Live / Amazon Web Services / Incident
Amazon Web Services: [RESOLVED] Increased Connectivity issues in US-EAST-1 — N. Virginia
Amazon Web Services · aws.amazon.comResolved2026-11-15 14:53 UTC
Public — what happened
Summary
Amazon Web Services said it began investigating connectivity problems in its US-EAST-1 (N. Virginia) Region at 12:38 UTC on 2026-11-15, along with trouble signing in through IAM Identity Center and creating new AWS accounts. The company said people using Identity Center to log in to the AWS Console or services such as Kiro and Connect saw errors, and it offered no workaround at first. It reported early recovery by 13:15 to 13:22 UTC, then said authentication was fully fixed, while a smaller group of Network Load Balancer users in one availability zone kept having connection problems for longer. AWS marked the incident resolved at 14:53 UTC, said all services were operating normally, and advised customers to retry any failed requests; it did not state a cause in the text provided.
Timeline
- Started — 2026-11-15 12:38 UTC
- Investigating — 2026-11-15 12:38 UTC (5 updates)
- Update — 2026-11-15 14:53 UTC
- Resolved — 2026-11-15 14:53 UTC · 2h 15m after it started
What SquidGrid measured
SquidGrid measured 37 internet paths into Amazon Web Services’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Amazon Web Services against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Amazon Web Services: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Amazon Web Services report →
More from Amazon Web Services
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.