AWS took 93 minutes to post its us-east-1 sign-in outage
Sign-in and connectivity errors hit 11 AWS services in US-EAST-1 for about three hours, and AWS still hasn't shared a root cause.

In short
- 01AWS says signup, sign-in and connectivity errors hit its US-EAST-1 Region from 3:05 to 6:10 AM PST.
- 02AWS's public status page first showed the incident at 4:38 AM PST, 93 minutes after the errors began.
- 03AWS listed 11 affected services, including IAM Identity Center, CloudWatch, NAT Gateway, Elastic Load Balancing and Kiro.
The story
AWS just confirmed an incident that broke sign-ins and connectivity in its US-EAST-1 Region for about three hours. Its public status page didn't mention the problem until 93 minutes after the errors began.
The incident drew little attention. Corey Quinn's column in The Register points out that it hit before dawn on a Sunday, Pacific time. It also landed in the shadow of Microsoft's much longer 365 outage.
IAM Identity Center failures blocked console sign-ins
Customers using IAM Identity Center to reach the AWS Console, or services such as Kiro and Amazon Connect, hit authentication errors. AWS told them there were "no workarounds for impacted customers" while it investigated. It fully mitigated the authentication problem at 5:20 AM PST.
The incident touched 11 services in all, including CloudWatch, NAT Gateway, Step Functions, OpenSearch and VPC Lattice. AWS also reported errors for new account signups.
One group waited longer. A subset of Network Load Balancers in a single cell of one Availability Zone, use1-az1, kept having connectivity problems until 6:21 AM PST. AWS told customers who needed an immediate fix to create a new load balancer with targets in multiple zones.
Customers noticed before the status page did
AWS says engineers were automatically engaged at 3:10 AM PST, five minutes after the first errors. Its first public notice came at 4:38 AM. Before that, users in an r/aws thread were comparing 503 errors and a dashboard that showed nothing wrong.
Of the 30 comments read for this story, about two-thirds reported being affected. That's a snapshot, not a survey.
Same here. Nothing in the health dashboard yet though.
A Reddit user on r/aws
AWS hasn't published a root cause. Its final update doesn't name one, and its Post-Event Summaries page lists nothing for this incident. AWS says all services are back to normal and recommends retrying failed requests.
A partial fix for the sign-in risk already exists. Organizations that use an external identity provider can replicate Identity Center to more Regions, which keeps a backup access portal online.
Why it matters
Sign-in is the layer teams need most during an incident, and a status page that lags by 93 minutes leaves them guessing. If every engineer reaches AWS through Identity Center in one Region, this was a free fire drill. A second Region or a tested break-glass account is cheap insurance against the next one.
Tools in this story
Share


