- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on New Relic. 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 2026-02-18 10:06 UTC and 2026-02-18 10:06 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 09:20 UTC and 09:44 UTC on Wed Feb 18 2026, some customers in the USEU region may have experienced delayed data in queries, charts, and dashboards. We have investigated and resolved this service interruption and impacted services have returned to normal operations.
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-4f91e75fd2
Is New Relic still down?
No, this incident was resolved 2026-02-18 10:06 UTC. For New Relic's live state, see https://down.guide/new-relic.
How long did it last?
0m, from 2026-02-18 10:06 UTC to 2026-02-18 10:06 UTC, by the times New Relic posted.
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.