Synthetics Ping Monitor Processing Delays in Multiple Regions
New Relic reported processing delays for Synthetic ping monitors in several regions. The affected regions were ap-south-1, ca-central-1, us-east-1, eu-north-1, eu-south-1, and eu-west-3. This affected Synthetics in Europe, Alert Notifications in Europe, and Data Ingest in Europe. New Relic reports that the incident is resolved. The incident lasted 106 minutes. Other synthetic monitor types were not affected.
State
Resolved
Started
2 h ago
2026-11-02 02:32 UTC
Lasted
1 h 46 min
until 2026-11-02 04:17 UTC
Worst impact
Partial outage
Timeline
4 updatesInvestigating
1 h 31 min 86%
Monitoring
15 min 14%
Updates
Times in UTCAs posted by New Relic
Queue processing for Synthetic ping monitors has normalized across all affected locations, and throughput metrics have returned to baseline. Systems remain stable and the service is operating normally.
Synthetic ping monitor processing has normalized and throughput has returned to baseline levels across all affected regions (ap-south-1, ca-central-1, us-east-1, eu-north-1, eu-south-1, and eu-west-3). Our teams are actively monitoring the environment to verify sustained stability. We will provide another update once performance remains consistent.
Our engineering teams continue to actively investigate the processing delays affecting Synthetic ping monitors in ap-south-1, ca-central-1, us-east-1, eu-north-1, eu-south-1, and eu-west-3.
We are currently investigating processing delays affecting Synthetic ping monitors across several regions (ap-south-1, ca-central-1, us-east-1, eu-north-1, eu-south-1, and eu-west-3). As a result, users may experience dropped or delayed ping monitor execution and an overall decrease in Synthetic throughput in these specific locations. Other synthetic monitor types (scripted, browser) remain unaffected at this time. We will provide an update as soon as more details become available.
Affected components
3New Relic in the last 90 days
Full historyIncidents in 90 days
6
Days with an incident
4
Median duration
56 min
This incident
1.9× the median
Other New Relic incidents
All incidentsNew Relic·Next-Gen Entity Platform Issues
Between 08:35 and 09:42 UTC on October 28th, we experienced an issue in the JP region affecting the Next Gen Entity Platform (NGEP) where some customers may have been unable to view or manage entities. The issue is now resolved and the service is operating normally.
New Relic·Data Irregularities for US region
Between 19:24 UTC and 22:04 UTC, a subset of customers in the US region may have experienced delayed data in queries, charts, and dashboards as well as delayed, missing or suppressed alert notifications for related data. We have investigated and resolved this service interruption and impacted services have returned to normal operations.
New Relic·New Relic UI errors
Between 01:10 UTC and 03:33 UTC on September 25th, some customers in the US, EU, and JP regions may have experienced intermittent UI errors while navigating the New Relic UI. Data ingest and alert notifications were not impacted. We have resolved this issue and impacted services have returned to normal operations.
New Relic·Salesforce Service Disruption
All in-app services have returned to normal operations. Please reach out to New Relic support for assistance with any issues.
New Relic·Data Irregularities for EU Region
Between 23:06 UTC and 23:16 UTC, some customers in the EU region may have experienced errors when sending metric timeslice data to New Relic, issues in viewing metric timeslice data in real time, and delayed or missing alert notifications related to real time data. Impacted data may not be recoverable.
Follow New Relic
Your coding agent knows when New Relic is down, and tells you when a failure is theirs, not yours. You can also get New Relic incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "newrelic" and tell me if New Relic has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=newrelic/feed subscribe https://outages.cc/feed.xml?providers=newrelicFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane