New Relic incident
Data and UI Irregularities - US and EU regions
New Relic experienced a minor incident on January 12, 2026, lasting 2h 49m. The incident has been resolved; the full update timeline is below.
Update timeline
- monitoring Jan 12, 2026, 06:10 PM UTC
Jan 12, 18:10 UTC 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. Jan 12, 17:36 UTC 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. Jan 12, 15:53 UTC Update - We have engaged our additional teams to assist with further investigation and are evaluating additional mitigation efforts. Jan 12, 15:22 UTC Update - We are continuing to investigate this issue. Jan 12, 15:21 UTC Investigating - We are currently investing an issue causing timeouts/query lag in NRDB