Live / Amazon Web Services / Incident
Amazon Web Services: [RESOLVED] Increased Error Rates — N. Virginia
Amazon Web Services · aws.amazon.comResolved2026-09-22 00:24 UTC
Public — what happened
Summary
Amazon Web Services said that between 3:49 PM and 5:06 PM PDT, customers in its US-EAST-1 (N. Virginia) Region saw more errors than usual when trying to start new EC2 virtual servers, and that other AWS services which start servers for customers, such as Amazon ECS, AWS Fargate and Amazon EMR, were also affected. The company said servers that were already running were not impacted. AWS attributed the problem to a recent software update to part of EC2 that handles launch requests, and said it reversed that update, saw recovery begin at 4:44 PM, and has since reported the issue resolved.
Timeline
- Started — 2026-09-21 23:26 UTC
- Resolved — 2026-09-22 00:24 UTC · 58 min after it started
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 40, 2026, our weekly internet health report.