- Level
- confirmed
- Worst impact
- Impact not stated
- Components
- Multiple services
- Regions
- us-east-1
Summary
The provider says connectivity issues in US-EAST-1 affecting IAM Identity Center sign-in and AWS SignUp are resolved. Authentication was fully mitigated at 5:20 AM PST, and a subset of Network Load Balancers in use1-az1 was fully mitigated at 6:21 AM PST.
Written by anthropic/claude-haiku-5.5 from AWS's own updates.
What to do
Check whether you use AWS Multiple services in us-east-1. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 15m it lasted.
Anything that failed between 2026-11-15 12:38 UTC and 2026-11-15 14:53 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 6
- investigating
We are investigating reports of Connectivity issues in the US-EAST-1 Region. IAM Identity center sign-in requests and AWS SignUp are also impacted at this time.
provider
- investigating
We continue to investigate Connectivity issues in the US-EAST-1 Region. IAM Identity center sign-in requests and AWS SignUp are impacted at this time. We can confirm errors when attempted to authenticate when using identity center or when using services that rely on IAM Identity center. For Kiro users, logins from social sign in methods are not impacted at this time. There are no workarounds for impacted customers.
provider
- investigating
We are seeing early signs of recovery for authentication via IAM Identity Center and SignUp.
provider
- investigating
We can confirm recovery for most AWS Services. We have fully mitigated the issue authentication errors from IAM Identity Center that was impacting Kiro, Connect, and other services which rely on IAM Identity Center for authentication. We continue to investigate an issue that is affecting a subset of Network Load Balancers in a single cell, in a single Availability Zone (use1-az1) in the US-EAST-1 Region. For customers who need immediate resolution, we recommend creating a new NLB with targets in multiple Availability Zones. We are actively working on multiple parallel paths to mitigate the issue. We will provide an update by 7:30 AM, or sooner if we have additional information to share.
provider
- investigating
We are seeing significant signs of recovery and are continuing to monitor for full recovery.
provider
- resolved
Between 3:05 AM and 6:10 AM PST we experienced signup errors, authentication issues, and connectivity issues in the US-EAST-1 Region. Customers using IAM Identity Center for authentication into the AWS Console, or for authentication into other AWS Services such as Kiro, Connect, etc would have been affected during this time. Engineers were automatically engaged at 3:10 AM PST and immediately began investigating the root cause, while in parallel working to mitigate both impacts. At 5:20, we fully mitigated the issue affecting authentication, and most AWS Services observed full recovery at this time. A subset of customers using NLB in a single cell in use1-az1 continued to experience connectivity issues until we fully mitigated the underlying issue at 6:21 AM PST. We recommend customers retry any failed requests. The issue has been resolved and all AWS Services are operating normally.
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-469a1d897e
Is AWS still down?
No, this incident was resolved 2026-11-15 14:53 UTC. For AWS's live state, see https://down.guide/providers/aws.
How long did it last?
2h 15m, from 2026-11-15 12:38 UTC to 2026-11-15 14:53 UTC, by the times AWS posted.
What was affected?
AWS named Multiple services in us-east-1.
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.