Live / Incidents / Amazon Web Services
Amazon Web Services: [RESOLVED] Increased Error Rates — N. Virginia
Amazon Web Services · aws.amazon.comResolved2026-09-22 00:24 UTC
Public — what happened
Summary
Between 3:49 PM and 5:06 PM PDT, we experienced increased error rates affecting new instance launches in the US-EAST-1 Region. During this time, customers may have experienced elevated error rates when attempting to launch new EC2 instances through RunInstances, CreateFleet, and related EC2 launch workflows. AWS services that launch EC2 instances on behalf of customers, including Amazon ECS, AWS Fargate, Amazon EMR, amongst others were also impacted during this period. We identified the root cause as a recent deployment to a subsystem within the EC2 service responsible for processing instance launch requests. We initiated a rollback of the problematic deployment and began observing initial s
Timeline
- Started — 2026-09-21 23:26 UTC
- Last update — 2026-09-22 00:24 UTC
- Resolved — 2026-09-22 00:24 UTC
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 →