New Relic incident

Issue when querying live edge data in the US region

Minor Resolved View vendor source →

New Relic experienced a minor incident on April 13, 2026, lasting 2h 33m. The incident has been resolved; the full update timeline is below.

Started
Apr 13, 2026, 12:44 PM UTC
Resolved
Apr 13, 2026, 03:17 PM UTC
Duration
2h 33m
Detected by Pingoru
Apr 13, 2026, 12:44 PM UTC

Update timeline

  1. monitoring Apr 13, 2026, 03:17 PM UTC

    Apr 13, 15:17 UTC Resolved - Between 10:30 AM and 2:40 PM UTC on April 13th, some customers may have experienced an issue to query live edge data and some customers may have noticed stopped synthetic monitors in the US region. The issue is now resolved and impacted services have returned to normal operations. Apr 13, 14:41 UTC Update - We are still investigating an issue where some customers may be unable to query live edge data and some customers may notice stopped synthetic monitors in the US region. We continue to work on the issue and understand root cause. We will continue to provide updates as we have more information to share, or by 3:30 PM UTC. Apr 13, 13:58 UTC Update - We are continuing to investigate an issue where some customers may be unable to query live edge data and some customers may notice stopped synthetic monitors in the US region. Technical teams are actively engaged and are exploring mitigation steps to address the issue. Data ingest and alert notifications are not impacted by this interruption. Apr 13, 12:55 UTC Update - We are investigating an issue where some customers may be unable to query live edge data in the US region. Data ingest and alert notifications are not impacted by this interruption. Apr 13, 12:49 UTC Update - We are investigating an issue where some customers may be unable to query live edge data in the US region. Data ingest and alert notifications are not impacted by this interruption. Apr 13, 12:44 UTC Investigating - We are investigating an issue where some customers may be unable to query live edge data in the US region. Data ingest and alert notifications are not impacted by this interruption.