# Amazon Web Services: Increased Error Rates (us-east-1)

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-09-21 23:26 UTC · Resolved: 2026-09-22 00:24 UTC · Duration: 58 min
- Updates: 3 · Affected components: Amazon WorkSpaces Applications, AWS AppSync, Amazon CloudFront, AWS DataSync, Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, Amazon OpenSearch Service, Amazon Elastic Load Balancing, Amazon Elastic MapReduce, AWS Fargate, AWS Global Accelerator, Amazon VPC IP Address Manager, AWS NAT Gateway, AWS VPCE PrivateLink, Amazon SageMaker, Traffic Mirroring, AWS Transit Gateway, AWS Site-to-Site VPN, Amazon WorkSpaces
- [Vendor status page: https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status)
- [Company: Amazon Web Services](https://rewindex.com/company/aws.md)

## Timeline of updates

- **update** 2026-09-21 23:26 UTC: We are investigating increased API error rates in the US-EAST-1 Region.
- **update** 2026-09-21 23:44 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.
- **update** 2026-09-22 00:24 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.


---
Canonical: https://rewindex.com/company/aws/incidents/us-east-1-aws_ec2_operational_issue_79073_047629764f9 · Markdown: https://rewindex.com/company/aws/incidents/us-east-1-aws_ec2_operational_issue_79073_047629764f9.md · JSON: https://rewindex.com/api/v1/companies/aws/incidents/us-east-1-aws_ec2_operational_issue_79073_047629764f9 · Generated 2026-10-20T00:08:27.173Z