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.
Started
21:49 UTC
Duration
Lasted 2h 21m
Source
IsDown
Next time
AWS (Amazon Web Services) is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Amazon Connect, Amazon Connect (Oregon), AWS Sign-In, AWS Sign-In (Oregon), Multiple services, Multiple services (Oregon), AWS IAM Identity Center, AWS IAM Identity Center (Oregon)
What happened?
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.
