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).
- AWS posted 21:49first vendor named AWS 21:12
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.
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 --> h1Vendors 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
- Minor incident
−38 min
Blames AWS
MaterializeDegraded availability for Cloud customers in us-west-2 due to upstream AWS credential service disruption
…Degraded availability for Cloud customers in us-west-2 due to upstream AWS credential service disruption Between 21:12 UTC and 22:18 UTC on September 3, AWS experienced elevated error rates in its Sec…
- Minor incident
−38 min
Blames AWS
Temporal CloudElevated Errors in us-west-2 Region
…Elevated Errors in us-west-2 Region As of 9/4 05:03 UTC, all affected MRN namespaces have been failed back to us-west-2. No further issues have been observed and this incident is resolved. As of 9/4 0…
- Major incident
−14 min
Blames AWS
…mgrep products. Our engineering team will continue monitoring until the final update from AWS. AWS STS outage in us-west-2 is affecting our system. We are investigating mitigations. Early signs of rec…
Within an hour
4 vendors
- Minor incident
+24 min
Blames AWS
DropboxCustomer support via telephone may be unavailable for some users
…has been resolved. We're currently experiencing issues with phone services due to a wider AWS outage. We are investigating and will share another update shortly.…
- Minor incident
+34 min
Blames AWS
TeleportTeleport us-west-2 increased error rates
…Teleport us-west-2 increased error rates This incident has been resolved. AWS is experiencing increased API errors in its us-west-2 region which is impacting Teleport Cloud services in that region. Si…
- Incident, no impact listed
+42 min
Blames AWS
WizWe are investigating an issue affecting some Wiz services for tenants hosted in the AWS us-west-2 region, related to an ongoing AWS service disruption
…We are investigating an issue affecting some Wiz services for tenants hosted in the AWS us-west-2 region, related to an ongoing AWS service disruption This incident has been resolved. A fix has been i…
- Minor incident
+48 min
Blames AWS
SurveyMonkeyPossible service degradation due to AWS outage
…Possible service degradation due to AWS outage This incident has been resolved. A fix has been implemented and we are monitoring the results. This incident has been resolved.…
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
- −21 minMajor incident
- −14 minMinor incident
- −12 minMajor incident
- −8 minMinor incident
- −7 minMinor incident
- +9 minMinor incident
- +24 minMinor incident
- +29 minMinor incident
- +44 minMinor incident
- +48 minMinor incident
- +55 minMinor incident
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.