Live / New Relic / Incident
New Relic: Synthetics Ping Monitor Processing Delays in Multiple Regions
New Relic · newrelic.comMajor incidentResolved2026-11-02 04:17 UTC
Public — what happened
Summary
New Relic said it was looking into delays affecting its Synthetics ping monitors in six regions, starting at 02:32 UTC on 2026-11-02. The company said users could see ping checks that were delayed or didn't run, and lower overall Synthetics throughput in those locations, while scripted and browser monitors were not affected. An update at 03:27 UTC said engineers were still investigating, and no cause was given in the text provided. The incident is marked resolved as of 04:17 UTC.
Affected
Synthetics : Europe, Synthetics : Europe
Timeline
- Started — 2026-11-02 02:32 UTC
- Investigating — 2026-11-02 02:32 UTC (2 updates)
- Resolved — 2026-11-02 04:17 UTC · 1h 46m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach New Relic against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for New Relic: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the New Relic report →
More from New Relic
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.