New Relic reported this major-impact incident on its official status page on Jan 12, 2026, 15:21 UTC. It was resolved after 2h 49m.
Right now New Relic is operational. Live New Relic status →
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.
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.
We have engaged our additional teams to assist with further investigation and are evaluating additional mitigation efforts.
We are continuing to investigate this issue.
We are currently investing an issue causing timeouts/query lag in NRDB
Our 5-minute checks didn't record a change in New Relic's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
New Relic reported 2 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 26m. See New Relic's uptime and incident history