New Relic incident

NrComputeUsage is 0 for ScannedEvents

Notice Resolved View vendor source →

New Relic experienced a notice incident on March 24, 2026, lasting 5h 9m. The incident has been resolved; the full update timeline is below.

Started
Mar 24, 2026, 05:22 AM UTC
Resolved
Mar 24, 2026, 10:31 AM UTC
Duration
5h 9m
Detected by Pingoru
Mar 24, 2026, 05:22 AM UTC

Update timeline

  1. investigating Mar 24, 2026, 05:22 AM UTC

    Some customers in the US and EU regions may experience discrepancies in NRComputeusage and NRConsumption usage values

  2. investigating Mar 24, 2026, 06:02 AM UTC

    We are continuing to investigate an issue where some customers in the US and EU regions may experience discrepancies in NRComputeusage and NRConsumption usage values

  3. resolved Mar 24, 2026, 10:31 AM UTC

    Between 2026-03-24 05:22:07 UTC and 2026-03-24 08:21:09 UTC on March Tuesday, some customers in the US/EU region may have experienced discrepancies in the NrComputeUsage and NRCompute usage values We have investigated and resolved a service interruption and impacted services have returned to normal operations.