← Back to New Relic History
minor✓ Resolved

APM Data and Alert Irregularities in the US Region

New Relic•
Status
resolved
Duration
1h 27m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
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.
identified
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.
identified
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.
identified
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.

📊 TECHNICAL DETAILS

Internal ID
8e873f14-5e38-4ed5-9e93-bde5f6cb2f12
External ID
fvvtbqph4hml
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
1h 27m
Total Duration
4
Status Updates
Affected Components
APM : USAPM Agent : US
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed