New Relic: Synthetics and Alert Irregularities for US Region
AWS us-east-1 outage, Dec 22, 2021 · 40 vendors, 40 incidents
New Relic’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +39 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-1<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>8 vendors, 6 blamed AWS<br/>Firebolt, Bitbucket, HubSpot, CircleCI +4"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor<br/>Confluent"]:::names
root --> h4
me["New Relic (this incident)<br/>posted +39 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
Between 12:09 and 13:50 UTC, some customers experienced Synthetics monitor failures and irregularities in Alerts across all products. Data will not be recovered. We’ve resolved the issue with UI and alerts for all Products in the US region Services. have returned to their normal operation.
From New Relic’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.newrelic.com (opens in new tab).