Rewindex

RewindexOutage eventsAug 29, 2024

AWS outage, Aug 29, 2024

14 vendors posted 14 incidents between 09:00 and 11:00 UTC, against about 2 incidents from 2 vendors in the same hours on an ordinary week. 5 vendors named AWS in 5 incidents (2 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.

    5. first vendor named AWS 09:00
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 hour3 vendors, 1 blamed AWSSegment, Ably, Front1 to 4 hours later2 vendors, 1 blamed AWSConfluent, Semgrep
AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSSegment, Ably, Front1 to 4 hours later2 vendors, 1 blamed AWSConfluent, Semgrep
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/>3 vendors, 1 blamed AWS<br/>Segment, Ably, Front"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Confluent, Semgrep"]:::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

3 vendors

  • +0 min

    Blames AWS

    Incident, no impact listed

    SegmentAmazon Kinesis Stream delays

    …Amazon Kinesis Stream delays Delivery delays to Amazon Kinesis of over an hour due to AWS outage.…

  • +41 min

    Names AWS

    Minor incident

    AblyPush notification and queue delivery issues

    …nue to monitor this issue. We're experiencing issues delivering push notifications in the ap-southeast-1 region. We are investigating and will post an update soon.…

  • +43 min

    Names AWS

    Minor incident

    FrontDegraded performance in us-west-2 [us-west-2]

    …Degraded performance in us-west-2 [us-west-2] This incident has been resolved. This incident has been resolved. We are experiencing issues launching new deployments in our us-west-2 region, which may…

1 to 4 hours later

2 vendors

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 2 in these hours).

Show all 9

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