Rewindex

RewindexOutage eventsMar 9, 2022

AWS outage, Mar 9, 2022

12 vendors posted 12 incidents between 21:00 on Mar 9 and 00:00 on Mar 10 UTC, against about 5 incidents from 4 vendors in the same hours on an ordinary week. 3 vendors named AWS in 3 incidents (3 of them blamed it). Vendors reported an AWS outage; AWS’s own incident for this date is not in the archive.

Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.

Times are UTC; lags are from when the first vendor named AWS.

    7. first vendor named AWS 21:20
Named AWSNamed another vendorDid not name anyoneEach column is 30 minutes

How it spread

Vendors that named AWS, grouped by when they posted, and vendors that blamed one of the vendors AWS took down. Solid lines: the vendor named the other. Dashed: same window, not named.

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour2 vendors, 2 blamed AWSCourier, Unbounce1 to 4 hours later1 vendor, 1 blamed AWSXero
AWSown incident not archivedWithin an hour2 vendors, 2 blamed AWSCourier, Unbounce1 to 4 hours later1 vendor, 1 blamed AWSXero
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
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

Vendors that named AWS

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

Within an hour

2 vendors

1 to 4 hours later

1 vendor

  • +1 h 52 min

    Blames AWS

    Incident, no impact listed

    XeroUsers experiencing errors in Xero

    …s experienced errors for a short period of time in the Xero platform due to an issue with Amazon Web Services (AWS). AWS have now resolved this issue and updated their Health Dashboard https://health.…

Same window, did not name anyone

9 incidents started during the event without naming AWS or another vendor. Some are part of it, some are a normal day’s background (about 5 in these hours).

Show all 9

Detected automatically from 10 status pages opening incidents in the peak hour (normally at most 5). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.