New Relic incident

NrComputeUsage is 0 for ScannedEvents

Resolved after 5 hours 9 minutes, on March 24, 2026.

monitoring Mar 24, 2026, 10:31 AM UTC

Mar 24, 10:31 UTC Resolved - 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. Mar 24, 06:02 UTC Update - 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 Mar 24, 05:22 UTC Investigating - Some customers in the US and EU regions may experience discrepancies in NRComputeusage and NRConsumption usage values

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. monitoring Mar 24, 2026, 10:31 AM UTC

    Mar 24, 10:31 UTC Resolved - 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. Mar 24, 06:02 UTC Update - 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 Mar 24, 05:22 UTC Investigating - Some customers in the US and EU regions may experience discrepancies in NRComputeusage and NRConsumption usage values

Your product runs on more than New Relic

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →