Amazon Web Services incident
Multiple services — Oregon: [RESOLVED] Increased API Error Rates
Amazon Web Services experienced a major incident on September 3, 2026 affecting Multiple services — Oregon, lasting 1d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Sep 03, 2026, 09:49 PM UTC
Starting at 2:12 PM PDT, we began experiencing increased API error rates for STS and Sign In when using SAML. 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.
- monitoring Sep 03, 2026, 10:26 PM UTC
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.
- monitoring Sep 03, 2026, 11:20 PM UTC
We continue to see recovery holding steady for the STS AssumeRoleWithSAML and AssumeRoleWithWebIdentityAPIs in the US-WEST-2 Region. Error rates are now back to pre-event levels, and continue actively monitoring to confirm full recovery. We will provide another update by 5:15 PM or earlier.
- monitoring Sep 04, 2026, 12:07 AM UTC
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.