- Level
- confirmed
- Worst impact
- Degraded
- Components
- MULTIPLESERVICES
- Regions
- us-west-2
- Down Index
- 49of 100
What to do
Check whether you use AWS MULTIPLESERVICES in us-west-2. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 18m it lasted.
Anything that failed between 2026-09-03 21:49 UTC and 2026-09-04 00:07 UTC may need a replay.Subscribe to AWS's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=aws works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from AWS 4
- investigating
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.
provider
- investigating
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.
provider
- investigating
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.
provider
- investigating
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-551e2296fe
Is AWS still down?
No, this incident was resolved 2026-09-04 00:07 UTC. For AWS's live state, see https://down.guide/aws.
How long did it last?
2h 18m, from 2026-09-03 21:49 UTC to 2026-09-04 00:07 UTC, by the times AWS posted.
What was affected?
AWS named MULTIPLESERVICES in us-west-2.
What caused it?
AWS hasn't published a root cause. If it does, it shows here.
Where does this come from?
AWS's official status page, https://health.aws.amazon.com/health/status, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.