Amazon Web Services incident
Amazon Elastic Compute Cloud — N. Virginia: [RESOLVED] Increased Error Rates
Amazon Web Services experienced a major incident on September 21, 2026 affecting Amazon Elastic Compute Cloud — N. Virginia, lasting 1d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Sep 21, 2026, 11:26 PM UTC
We are investigating increased API error rates in the US-EAST-1 Region.
- monitoring Sep 21, 2026, 11:44 PM UTC
We can confirm increased error rates affecting new instance launches, including elevated API error rates for RunInstances, CreateFleet, and related EC2 launch workflows in the US-EAST-1 Region. Customers attempting to launch new EC2 instances may experience launch failures or elevated API response latency. Our engineers are actively engaged and working towards recovering the issue. We are seeing initial signs of recovery. Existing instances remain unaffected. We recommend retrying failed RunInstances and CreateFleet API calls. We will provide an update by 5:30 PM PDT or sooner.
- monitoring Sep 22, 2026, 12:24 AM UTC
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 signs of recovery at 4:44 PM. Existing instances remain unaffected. The issue has been resolved and the service is operating normally.