Rewindex

RewindexOutage eventsSep 28, 2022

AWS outage, Sep 28, 2022

16 vendors posted 15 incidents between 16:00 and 21:00 UTC, against about 12 incidents from 10 vendors in the same hours on an ordinary week. 6 vendors named AWS in 6 incidents (6 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.

    11. first vendor named AWS 16:57
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, 3 blamed AWSDaily, Unbounce, Gusto1 to 4 hours later3 vendors, 3 blamed AWSLever, Jira, Confluence
AWSown incident not archivedWithin an hour3 vendors, 3 blamed AWSDaily, Unbounce, Gusto1 to 4 hours later3 vendors, 3 blamed AWSLever, Jira, Confluence
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, 3 blamed AWS<br/>Daily, Unbounce, Gusto"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>3 vendors, 3 blamed AWS<br/>Lever, Jira, Confluence"]:::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

1 to 4 hours later

3 vendors

  • +1 h 56 min

    Blames AWS

    Minor incident

    LeverIncident with AWS

    …Incident with AWS AWS has confirmed that the issue they have experienced has been resolved. More information on the incident can be found here https://health.aws.amazon.com/health/status. We’ll contin…

  • +3 h 33 min

    Blames AWS

    Minor incident

    JiraIntermittent Notification Delay/Failure

    …are, Jira Work Management, Confluence, and Jira Service Management. The root cause was an AWS issue that caused our notification services to fail intermittently. This issue has been resolved.…

  • +3 h 39 min

    Blames AWS

    Minor incident

    ConfluenceIntermittent Notification Delay/Failure

    …are, Jira Work Management, Confluence, and Jira Service Management. The root cause was an AWS issue that caused our notification services to fail intermittently. This issue has been resolved.…

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 12 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.