New Relic incident

APM Data and Alert Irregularities in the US Region

Minor Resolved View vendor source →

New Relic experienced a minor incident on May 25, 2025 affecting APM : US and APM Agent : US, lasting 1h 26m. The incident has been resolved; the full update timeline is below.

Started
May 25, 2025, 01:34 AM UTC
Resolved
May 25, 2025, 03:00 AM UTC
Duration
1h 26m
Detected by Pingoru
May 25, 2025, 01:34 AM UTC

Affected components

APM : USAPM Agent : US

Update timeline

  1. identified May 25, 2025, 01:34 AM UTC

    Some customers in the US region may be experiencing delayed APM data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. To prevent our customers from receiving a high volume of false positive alert notifications, we have temporarily suppressed notifications for affected data.

  2. identified May 25, 2025, 02:08 AM UTC

    Beginning at 01:00 May 25 UTC some customers in the US region may be experiencing delayed APM data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. To prevent our customers from receiving a high volume of false positive alert notifications, we have temporarily suppressed notifications for affected data.

  3. identified May 25, 2025, 02:19 AM UTC

    Beginning at 01:00 May 25 UTC some customers in the US region may be experiencing delayed APM data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We have reduced the latency at this point and are investigating further. To prevent our customers from receiving a high volume of false positive alert notifications, we have temporarily suppressed notifications for affected data.

  4. resolved May 25, 2025, 03:00 AM UTC

    Beginning at 01:00 and 02:58 May 25 UTC, some customers in the US region may have experienced delayed APM data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We suppressed alerts from 01:32 to 02:58 May 25 UTC. We have resolved this interruption and impacted services have returned to normal operations.