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

As listed on New Relic’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the New Relic status & history page.

Related: New Relic status & history. SquidGrid is not affiliated with New Relic.