Rewindex

RewindexOutage eventsSep 3, 2026

AWS us-west-2 outage, Sep 3, 2026

19 vendors posted 18 incidents between 21:00 and 23:00 UTC, against about 4 incidents from 4 vendors in the same hours on an ordinary week. 7 vendors named AWS in 7 incidents (7 of them blamed it), and 3 did so before AWS’s own status page. AWS posted “Increased API Error Rates (us-west-2)” at 21:49 UTC.

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 AWS posted (21:49).

  1. AWS posted 21:49first vendor named AWS 21:12
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-west-2posted 21:49 UTCPosted before AWS did3 vendors, 3 blamed AWSMaterialize, Temporal Cloud, SemgrepWithin an hour4 vendors, 4 blamed AWSDropbox, Teleport, Wiz, SurveyMonkey
AWS us-west-2posted 21:49 UTCPosted before AWS did3 vendors, 3 blamed AWSMaterialize, Temporal Cloud,SemgrepWithin an hour4 vendors, 4 blamed AWSDropbox, Teleport, Wiz,SurveyMonkey
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-west-2<br/>posted 21:49 UTC"]:::root
  before["Posted before AWS did<br/>3 vendors, 3 blamed AWS<br/>Materialize, Temporal Cloud, Semgrep"]:::blames
  root --> before
  h1["Within an hour<br/>4 vendors, 4 blamed AWS<br/>Dropbox, Teleport, Wiz, SurveyMonkey"]:::blames
  root --> h1

Vendors that named AWS

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

Posted before AWS did

3 vendors

Within an hour

4 vendors

Same window, did not name anyone

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

Show all 11

Detected automatically from 11 status pages opening incidents in the peak hour (normally at most 8). 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.