Materialize: Degraded availability for Cloud customers in us-west-2 due to upstream AWS credential service disruption
AWS us-west-2 outage, Sep 3, 2026 · 20 vendors, 20 incidents
Materialize’s incident blames AWS as the cause. (hop 1, posted −38 min vs AWS’s own post)
“…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…”
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 --> h1
me["Materialize (this incident)<br/>posted −38 min"]:::me
before --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: aws/us-west-2
Timeline of updates
- resolved
Between 21:12 UTC and 22:18 UTC on September 3, AWS experienced elevated error rates in its Security Token Service (STS) in the us-west-2 region, which AWS reported on its Health Dashboard. Materialize environments in that region use STS to obtain credentials for object storage access, and requests for those credentials failed or timed out during the event. Some environments in the region experienced degraded performance during this window. Query results remained correct throughout, and no data was lost. The upstream issue was resolved by AWS at 22:18 UTC and all affected environments recovered.
Impact, status and times are the vendor’s own, as last archived. View on status.materialize.com (opens in new tab).