Skip to main content
New Relic

Synthetics Ping Monitor Processing Delays in Multiple Regions

Degraded Lasted 1h 46m · started · New Relic's page

Level
confirmed
Worst impact
Degraded
Components
Synthetics : Europe, Synthetics : Europe
Regions
ap-south-1, ca-central-1, eu, eu-north-1, eu-south-1, eu-west-3, us, us-east-1
Down Index
39of 100

What to do

  • Check whether you use New Relic Synthetics : Europe, Synthetics : Europe in ap-south-1, ca-central-1, eu, eu-north-1. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 46m it lasted.

    Anything that failed between 2026-11-02 02:32 UTC and 2026-11-02 04:17 UTC may need a replay.
  • Subscribe to New Relic's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=new-relic works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from New Relic 4

  1. investigating

    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.

    provider

  2. investigating

    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.

    provider

  3. monitoring

    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.

    provider

  4. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-4cea9e06b3

Is New Relic still down?

No, this incident was resolved 2026-11-02 04:17 UTC. For New Relic's live state, see https://down.guide/new-relic.

How long did it last?

1h 46m, from 2026-11-02 02:32 UTC to 2026-11-02 04:17 UTC, by the times New Relic posted.

What was affected?

New Relic named Synthetics : Europe, Synthetics : Europe in ap-south-1, ca-central-1, eu, eu-north-1.

What caused it?

New Relic hasn't published a root cause. If it does, it shows here.

Where does this come from?

New Relic's official status page, https://status.newrelic.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.