- Level
- confirmed
- Worst impact
- Partial outage
- Components
- APM : Europe, Alerts : US, Alerts : Europe, APM : US, Browser : Europe, Infrastructure : US, Infrastructure : Europe, Auto-Telemetry with Pixie : US, Logs : US, AWS Lambda Integration : US, Logs : Europe, Browser : US, Mobile : Europe, Infrastructure Agent : US, Infrastructure Agent : Europe, Dashboards : US, NRQL : Europe, Log API : US, Log API : Europe, Serverless : Europe, Incident Intelligence : US, Metric API : US, Metric API : Europe, Infrastructure : US, Synthetics : Europe, Infrastructure : Europe, OTLP API : US, OTLP API : Europe, Infrastructure Integrations : US, Infrastructure Integrations : Europe, Logs : US, Logs : Europe, Lookout : US, Mobile : US, Open Instrumentation : US, Proactive Detection : US, Serverless : US, Synthetics : US
- Regions
- eu, us
What to do
Check whether you use New Relic APM : Europe, Alerts : US, Alerts : Europe, APM : US and 34 more 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 2h 49m it lasted.
Anything that failed between 2026-01-12 15:21 UTC and 2026-01-12 18:10 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 5
- investigating
We are currently investing an issue causing timeouts/query lag in NRDB
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We have engaged our additional teams to assist with further investigation and are evaluating additional mitigation efforts.
provider
- identified
Some customers in the US and EU region may experience errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data. We are seeing recovery from mitigating actions and will continue to provide updates until services have been restored to normal operation.
provider
- resolved
Our teams have resolved two concurrent service interruptions affecting data ingestion and query services. On January 12th, 2026, a subset of customers in the US and EU regions may have experienced latency or timeouts when querying data in New Relic. Teams implemented a fix, restoring affected query performance at 17:29 UTC. Separately, a subset of customers in the US and EU regions may have experienced errors when sending data to New Relic. This interruption could have resulted in potential data drops for data sent during this timeframe, depending on client-side retry settings, and may have generated false alert notifications regarding host reporting status. This interruption appears related to a disruption with a New Relic third-party edge service provider. To remediate, our teams have shifted traffic to an alternate cloud provider and have seen recovery of impacted services.
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-f667d449a0
Is New Relic still down?
No, this incident was resolved 2026-01-12 18:10 UTC. For New Relic's live state, see https://down.guide/new-relic.
How long did it last?
2h 49m, from 2026-01-12 15:21 UTC to 2026-01-12 18:10 UTC, by the times New Relic posted.
What was affected?
New Relic named APM : Europe, Alerts : US, Alerts : Europe, APM : US and 34 more 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.