New Relic outage: Data Irregularities

Affected components

• Alert Notifications : Europe - APM : Europe
• Alert Notifications : Europe - Browser : Europe
• Alert Notifications : Europe - Infrastructure : Europe
• Alert Notifications : Europe - Logs : Europe
• Alert Notifications : Europe - Mobile : Europe
• Alert Notifications : Europe - NRQL : Europe
• Alert Notifications : Europe - Serverless : Europe
• Alert Notifications : Europe - Synthetics : Europe
• Alert Notifications : US - APM : US
• Alert Notifications : US - Browser : US
• Alert Notifications : US - Infrastructure : US
• Alert Notifications : US - Logs : US
• Alert Notifications : US - Mobile : US
• Alert Notifications : US - NRQL : US
• Alert Notifications : US - Serverless : US
• Alert Notifications : US - Synthetics : US
• Data Ingest : Europe - APM Agent : Europe
• Data Ingest : Europe - Browser Agent : Europe
• Data Ingest : Europe - Event API : Europe
• Data Ingest : Europe - Incident Intelligence API : Europe
• Data Ingest : Europe - Infrastructure Agent : Europe
• Data Ingest : Europe - Log API : Europe
• Data Ingest : Europe - Metric API : Europe
• Data Ingest : Europe - Mobile Agent : Europe
• Data Ingest : Europe - OTLP API : Europe

1. resolvedMar 3, 2026, 02:59 UTC

   We resolved this service interruption and impacted services have returned to normal operation. Between 00:11 UTC and 02:45 UTC on March 3rd, 2026, some customers may have experienced delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for impacted data.

2. monitoringMar 3, 2026, 02:28 UTC

   We continue to see signs of recovery as we monitor impacted services. Some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We will continue to provide updates until services return to normal operations.

3. investigatingMar 3, 2026, 01:02 UTC

   We are still investigating the an issue where some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We have been seeing signs of recovery, and will continue to provide updates until services are restored to normal operations.

4. investigatingMar 3, 2026, 00:36 UTC

   We are continuing to investigate an issue where some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data.

5. investigatingMar 3, 2026, 00:21 UTC

   Some customers in the US and EU regions may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data.

6. investigatingMar 3, 2026, 00:19 UTC

   Some customers in the US and EU regions may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data.

What APIStatus.watch saw

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.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Snowflake: AWS - Middle East (UAE): INC0152681Critical · Mar 1, 2026, 13:33 UTC
• Grafana Cloud: Complete outage in prod-me-central-1Critical · Mar 2, 2026, 06:43 UTC
• Smartsheet: Brandfolder Monthly Reports DelayedMajor · Feb 27, 2026, 21:55 UTC
• MongoDB Atlas: Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)Major · Mar 1, 2026, 19:30 UTC
• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Mar 2, 2026, 07:19 UTC
• Render: Ohio Services with Disks, Data Persistence failingMajor · Mar 3, 2026, 00:41 UTC
• Amplitude: Resource Center search is degradedMajor · Mar 3, 2026, 02:53 UTC

How often does New Relic have incidents?

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