New Relic Outage History

New Relic experienced distributed tracing errors impacting the UI and APM components in Europe and the United States. The issue began on 4:23 PM UTC and was resolved by 5:23 PM UTC, lasting about 1 hour. Users in the affected regions may have seen errors when generating or viewing distributed traces.

The New Relic status page documented the incident as an investigation at first, then confirmed resolution once the services returned to normal. The incident involved two regional components: UI : Europe / APM : Europe and UI : US / APM : US, with two official updates issued during the outage. There were no public user reports recorded during this period. The geographic impact was regional to the US and Europe rather than global.

New Relic reported alert irregularities in the US region, causing delayed or missing real-time alert notifications for some customers. This impacted alert delivery across multiple components, including Alert Notifications for APM, Mobile, Infrastructure, Logs, NRQL, Serverless, Browser, Synthetics, and the UI Alerts interface. The incident began at Jan 21, 2026 10:23 PM UTC and was resolved by Jan 22, 2026 12:48 AM UTC, lasting about 2 hours and 25 minutes. The status page published three updates during the incident: initial investigation, identification and a fix with early recovery, and final resolution.

New Relic reported UI irregularities with degraded performance affecting data ingestion, real-time data viewing, and alert notifications. The disruption was centered in the US region and impacted 16 UI components (including Open Instrumentation, Proactive Detection, Serverless, Logs, Infrastructure, Infrastructure Integrations, Lookout, Mobile, Synthetics, Alerts, APM, Auto-Telemetry with Pixie, AWS Lambda Integration, Browser, Dashboards, and Incident Intelligence). US and EU customers could experience errors when sending data, delays in dashboard updates, and incomplete or late alert notifications. The outage began at 3:23 PM UTC and was resolved by 6:13 PM UTC, lasting about 2 hours and 50 minutes.

An incident impacted New Relic's Alert Notifications service in the US and Europe, causing false loss-of-signal alerts for a period. The incident began at Dec 18, 2025 11:33 PM UTC and was resolved by Dec 19, 2025 1:59 AM UTC. The provider issued 3 official updates during the incident, and the issue affected the Alert Notifications components in US and Europe. This event represented degraded alert delivery rather than a full platform outage, with users in both regions potentially receiving spurious alerts. After the final update, Alert Notifications returned to normal and services were restored.

New Relic reported connectivity issues affecting Data Ingest in the Europe region (eu-proud-roof). The issue began around 11:48 AM UTC and caused degraded ingestion across 11 Europe ingest components, including APM Agent, Browser Agent, Event API, Incident Intelligence API, Infrastructure Agent, Log API, Metric API, Mobile Agent, OTLP API, Trace API, and Synthetics. The problem progressed to a partial degradation at 3:53 PM UTC and was fully resolved by 3:58 PM UTC after roughly 4 hours and 10 minutes. User reports were limited during the incident. The Europe region experienced the impact; no global service disruption was indicated. The provider issued 3 status updates during the incident.

The New Relic status site experienced a brief outage where pages failed to load for about a minute. StatusGator detected an Early Warning Signal at Oct 30, 2025 6:05 PM UTC based on user reports, with four reports across Seattle, Toronto, Atlanta, and Buenos Aires describing pages not loading or 404 errors. The outage began at 6:05 PM UTC and was resolved by 6:06 PM UTC. New Relic did not publish a status page update during the event. The incident appeared limited to the New Relic status pages and did not indicate broader service impact.

New Relic Data Ingest in the US and Europe experienced partial degradation, with errors sending data, issues viewing real-time data, and delayed or missing data in Synthetics and Cloud environments. This degradation affected two regional components and impaired data ingestion and live dashboards for affected users.

The incident began at 8:45 AM UTC with the initial status change. Over the course of the event, three status updates were published. The US component recovered by 10:13 PM UTC and the European component by 10:19 PM UTC, resulting in an outage lasting about 13 hours and 34 minutes.

New Relic reported Data Irregularities in the US Region, causing delayed Browser Monitoring data for queries, charts, and dashboards and delaying or missing alert notifications for related data. This affected Data Ingest (Browser Agent), Alert Notifications, and UI in the US region. The incident began at 4:03 PM UTC and was resolved by 8:13 PM UTC, lasting about 4 hours and 10 minutes. The provider issued five status updates during the incident, including an initial suppression of alerts to prevent false positives and subsequent updates as recovery progressed.

The outage began on 5:38 PM UTC and was resolved by 6:53 PM UTC. New Relic reported data irregularities in the US region, causing delays in data appearing in the user interface and in alert notifications. The issue affected 11 Data Ingest components in the US region, including Event API, Browser Agent, Incident Intelligence API, Log API, Metric API, Mobile Agent, OTLP API, Trace API, Synthetics, Infrastructure Agent, and APM Agent. The incident lasted about 1 hour and 15 minutes and could impact monitoring and analysis workflows for users relying on up-to-date data.

The provider issued two official status updates during the incident, describing the problem and listing the affected components before restoring normal service. The status transitioned from up to warn and then back to up as services were brought back online.

An outage affected New Relic Synthetics checks in the US Production region, with Synthetic Reporting dropping to zero and impacting synthetic monitoring workflows. The issue began around Sep 9, 2025 12:52 PM UTC and prompted an investigation, with an official update at 12:53 PM UTC as engineers worked to identify the cause. The outage impacted UI and Synthetics components in the US, and persisted for approximately 5 hours and 51 minutes before the service was restored at 6:43 PM UTC. The provider issued two status updates during the incident, outlining ongoing investigation and eventual recovery.