- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu, us
What to do
Check whether you use New Relic in eu, us. 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 0m it lasted.
Anything that failed between 2025-09-26 22:42 UTC and 2025-09-26 22:42 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 1
- resolved
Between 21:48 UTC and 22:36 UTC on September 26, Friday, some customers in the US & EU region may have experienced delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We have investigated and resolved this service interruption and impacted services have returned to normal operations. To prevent our customers from receiving a high volume of false positive alert notifications, we temporarily suppressed notifications for affected data between 22:11 UTC and 22:30 UTC.
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-d64b081906
Is New Relic still down?
No, this incident was resolved 2025-09-26 22:42 UTC. For New Relic's live state, see https://down.guide/new-relic.
How long did it last?
0m, from 2025-09-26 22:42 UTC to 2025-09-26 22:42 UTC, by the times New Relic posted.
What was affected?
New Relic named in eu, us.
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.