New Relic reported this minor-impact incident on its official status page on Nov 2, 2026, 02:32 UTC. It was resolved after 1h 46m.
Right now New Relic is operational. Live New Relic status →
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.
Overlapping incidents aren't necessarily related.
New Relic reported 3 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 46m. See New Relic's uptime and incident history