Rewindex

CompaniesAmazon Web ServicesIncidents

Amazon Web Services: Increased API Error Rates (us-west-2)

MinorStatus: resolvedStarted Resolved (2.3 h)4 updateshealth.aws.amazon.com (opens in new tab)
Part of an outage event

AWS us-west-2 outage, Sep 3, 2026 · 20 vendors, 20 incidents

Amazon Web Services’s incident is the root of the event (the provider’s own post). (root, posted +0 min vs AWS’s own post)

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
Amazon Web Services is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
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
  class root me

Full 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: Amazon ConnectAWS IAM Identity CenterAWS Sign-InAWS Security Token Service

Timeline of updates

  1. update

    Starting at 2:12 PM PDT, we began experiencing increased API error rates for STS and Sign In when using SAML in the US-WEST-2 Region. Our engineering team was automatically engaged at 2:19 PM to begin investigating the root cause. There is no work around available at this time. We will provide another update by 3:30 PM PDT.

  2. update

    We are seeing early signs of recovery and continue to monitor for full recovery. We will provide another update at 4:15 PM, or sooner if we have additional information to share.

  3. update

    We continue to see recovery holding steady for the STS AssumeRoleWithSAML and AssumeRoleWithWebIdentity APIs in the US-WEST-2 Region. Error rates are now back to pre-event levels, and we continue actively monitoring to confirm full recovery. We will provide another update by 5:15 PM or earlier.

  4. resolved

    Between 2:12 PM and 3:18 PM PDT, we experienced increased API error rates affecting the STS AssumeRoleWithSAML and AssumeRoleWithWebIdentity APIs in the US-WEST-2 Region. The root cause was determined to be due to an issue with an STS subsystem responsible for communicating with external identity providers. Other AWS Services that rely on these identity federation protocols were also affected. At 3:18 PM, we observed signs of recovery and continued to monitor to ensure stability and full recovery. The issue is resolved and the service is operating normally at this time.

Impact, status and times are the vendor’s own, as last archived. View on health.aws.amazon.com (opens in new tab).

Amazon Web Services profileRecent Amazon Web Services incidentsMarkdownJSON