AWS: Increased Connectivity issues in US-EAST-1
Is it fixed? Yes.
Resolved after 2 h 15 min. First reported Nov 15, 12:38 UTC, resolved Nov 15, 14:53 UTC. The vendor posted it on its status page first.
What happened
AWS experienced connectivity, authentication, and signup issues in the US-EAST-1 region due to a regional incident affecting IAM Identity Center and a subset of Network Load Balancers in a single Availability Zone (use1-az1). The incident has since been fully resolved.
What caused it?
Under active investigation. No report has identified a root cause yet.
Workaround available
For customers who needed immediate resolution during the incident, AWS recommended creating a new NLB with targets.
Official fixTimeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(current)
- First report on status page
Service impact: Increased Connectivity issues in US-EAST-1
Source - Official statement
We are investigating reports of Connectivity issues in the US-EAST-1 Region.
Source - Official statement
⚠️ Amazon Web Services (AWS) is reporting an incident: Multiple services (N.
Source - Official statement
We continue to investigate Connectivity issues in the US-EAST-1 Region.
Source - Official statement
We are seeing early signs of recovery for authentication via IAM Identity Center and SignUp.
Source - Official statement
We can confirm recovery for most AWS Services.
Source
Show all 12 updatesHide the full timeline
- First report on status page
Service impact: Increased Connectivity issues in US-EAST-1
Source - Official statement
We are investigating reports of Connectivity issues in the US-EAST-1 Region.
Source - Confirmed on Bluesky post
⚠️ Amazon Web Services (AWS) is reporting an incident: Multiple services (N.
Source - Official statement
⚠️ Amazon Web Services (AWS) is reporting an incident: Multiple services (N.
Source - Official statement
We continue to investigate Connectivity issues in the US-EAST-1 Region.
Source - Official statement
We are seeing early signs of recovery for authentication via IAM Identity Center and SignUp.
Source - Official statement
We can confirm recovery for most AWS Services.
Source - Official statement
We are seeing significant signs of recovery and are continuing to monitor for full recovery.
Source - Official statement
Between 3:05 AM and 6:10 AM PST we experienced signup errors, authentication issues, and connectivity issues in the US-EAST-1 Region.
Source - Status changed
Status changed: investigating → resolved (official status page reports resolution).
- Official statement
✅ Resolved: Amazon Web Services (AWS) - Multiple services (N.
Source - Workaround discovered
Workaround reported: For customers who needed immediate resolution during the incident, AWS recommended creating a new NLB with targets.
Source
Evidence
8 reports · 6 Status, 2 BlueskyShow
- [1]Status First reportService impact: Increased Connectivity issues in US-EAST-1(opens official status page in a new tab)
We are investigating reports of Connectivity issues in the US-EAST-1 Region. IAM Identity center sign-in requests and AWS SignUps are also impacted at this time.
by aws status
- [2]Bluesky⚠️ Amazon Web Services (AWS) is reporting an incident: Multiple services (N.(opens the official status page in a new tab)
⚠️ Amazon Web Services (AWS) is reporting an incident: Multiple services (N. Virginia): Increased Connectivity issues in US-EAST-1 Investigating: We are investigating Connectivity issues in the US-EAST-1 Region. IAM Identity center sign-in requests and AWS SignUps are also impact… t.lpl.dev/9K8Llns
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 1comments94% match
- [3]StatusService impact: Increased Connectivity issues in US-EAST-1(opens official status page in a new tab)
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.
by aws status95% match
- [4]StatusService impact: Increased Connectivity issues in US-EAST-1(opens official status page in a new tab)
We are seeing early signs of recovery for authentication via IAM Identity Center and SignUp.
by aws status93% match
- [5]StatusService impact: Increased Connectivity issues in US-EAST-1(opens official status page in a new tab)
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…
by aws status95% match
- [6]StatusService impact: Increased Connectivity issues in US-EAST-1(opens official status page in a new tab)
We are seeing significant signs of recovery and are continuing to monitor for full recovery.
by aws status94% match
- [7]StatusService is operating normally: [RESOLVED] Increased Connectivity issues in US-EAST-1(opens official status page in a new tab)
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…
by aws status94% match
- [8]Bluesky✅ Resolved: Amazon Web Services (AWS) - Multiple services (N.(opens the official status page in a new tab)
✅ Resolved: Amazon Web Services (AWS) - Multiple services (N. Virginia): [RESOLVED] Increased Connectivity issues in US-EAST-1
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 0comments92% match
FAQ
What happened in the AWS outage?
AWS experienced connectivity, authentication, and signup issues in the US-EAST-1 region due to a regional incident affecting IAM Identity Center and a subset of Network Load Balancers in a single Availability Zone (use1-az1). The incident has since been fully resolved.
What is affected by the AWS outage?
AWS.
When did the AWS outage start and end?
It started Nov 15, 12:38 UTC and was resolved Nov 15, 14:53 UTC, after 2 h 15 min.
How do I get alerts for AWS?
Subscribe to the AWS RSS feed for every new AWS incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether AWS is down. AWS feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 8 reports from 2 independent sources, including the vendor’s own status page.