New Relic: Synthetic Alerts Irregularities for US/EU Regions
AWS outage, Mar 9, 2022 · 12 vendors, 12 incidents
New Relic’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted −14 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>2 vendors, 2 blamed AWS<br/>Courier, Unbounce"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Xero"]:::blames
root --> h4
me["New Relic (this incident)<br/>posted −14 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 20:42 and 21:52 UTC on March 9, some customers experienced delays and gaps in synthetics data. Data will not be recovered. We’ve resolved the issue with alerts for Synthetics in the US and EU regions. 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.
Impact, status and times are the vendor’s own, as last archived. View on status.newrelic.com (opens in new tab).