Rewindex

RewindexOutage eventsJun 13, 2023

AWS outage, Jun 13, 2023

56 vendors posted 54 incidents between 19:00 and 22:00 UTC, against about 8 incidents from 7 vendors in the same hours on an ordinary week. 20 vendors named AWS in 19 incidents (19 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 19:13
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 hour13 vendors, 13 blamed AWSPipedream, Wiz, Temporal Cloud, Ashby +91 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana, JFrog +3
AWSown incident not archivedWithin an hour13 vendors, 13 blamed AWSPipedream, Wiz, TemporalCloud, Ashby +91 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana,JFrog +3
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/>13 vendors, 13 blamed AWS<br/>Pipedream, Wiz, Temporal Cloud, Ashby +9"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>7 vendors, 6 blamed AWS<br/>CockroachDB, Vanta, Asana, JFrog +3"]:::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

12 vendors

1 to 4 hours later

7 vendors

Same window, did not name anyone

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

Show all 35

Detected automatically from 32 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.