Rewindex

RewindexOutage eventsJul 28, 2022

AWS us-east-2 outage, Jul 28, 2022

25 vendors posted 25 incidents between 16:00 and 19:00 UTC, against about 9 incidents from 7 vendors in the same hours on an ordinary week. 6 vendors named AWS in 6 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 17:11
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.

AWS us-east-2own incident not archivedWithin an hour5 vendors, 2 blamed AWSElastic Cloud, Coralogix, Confluent, Aptible +11 to 4 hours later1 vendor, 1 blamed AWSStream (GetStream)
AWS us-east-2own incident not archivedWithin an hour5 vendors, 2 blamed AWSElastic Cloud, Coralogix,Confluent, Aptible +11 to 4 hours later1 vendor, 1 blamed AWSStream (GetStream)
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 us-east-2<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Elastic Cloud, Coralogix, Confluent, Aptible +1"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Stream (GetStream)"]:::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

5 vendors

1 to 4 hours later

1 vendor

  • +1 h 17 min

    Blames AWS

    Minor incident

    Stream (GetStream)AWS connectivity issues

    …AWS connectivity issues This incident has been resolved. The issue has been resolved and the service in Ohio region is operating normally. This incident has been resolved. We experience a partial outa…

Same window, did not name anyone

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

Show all 19

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