AWS: Elevated API issues and Launch Failures
Is it fixed? Yes.
Resolved after 5 h 30 min. First reported Nov 11, 15:40 UTC, resolved Nov 11, 21:11 UTC. The vendor posted it on its status page first.
What happened
AWS experienced elevated API error rates, EC2 launch failures, and connectivity issues primarily centered in the AP-NORTHEAST-1 Region (specifically Availability Zone apne1-az1). The incident also affected ECS and Fargate task launches, ELB provisioning, NAT Gateway workflows, and Managed Flink state transitions before being fully resolved.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
This incident was resolved upstream without a reported workaround.
Official fixTimeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(current)
- First report on status page
Service impact: Elevated API issues and Launch Failures
Source - Official statement
We are experiencing elevated API error rates and launch failures in the AP-NORTHEAST-1 Region.
Source - Official statement
⚠️ Amazon Web Services (AWS) is reporting an incident: Amazon Elastic Compute Cloud (Tokyo): Elevated API issues and Launch Failures Investigating: We are experiencing elevated API error rates and launch failures in the AP-NORTHEAST-1 Region.
Source - Official statement
We are experiencing elevated API error rates and launch failures in the AP-NORTHEAST-1 Region.
Source - Official statement
We are seeing early signs of recovery for the elevated API error rates and launch failures in the AP-NORTHEAST-1 Region.
Source - Official statement
We continue to see broad signs of recovery in the AP-NORTHEAST-1 Region.
Source
Show all 12 updatesHide the full timeline
- First report on status page
Service impact: Elevated API issues and Launch Failures
Source - Official statement
We are experiencing elevated API error rates and launch failures in the AP-NORTHEAST-1 Region.
Source - Confirmed on Bluesky post
⚠️ Amazon Web Services (AWS) is reporting an incident: Amazon Elastic Compute Cloud (Tokyo): Elevated API issues and Launch Failures
Source - Official statement
⚠️ Amazon Web Services (AWS) is reporting an incident: Amazon Elastic Compute Cloud (Tokyo): Elevated API issues and Launch Failures Investigating: We are experiencing elevated API error rates and launch failures in the AP-NORTHEAST-1 Region.
Source - Official statement
We are experiencing elevated API error rates and launch failures in the AP-NORTHEAST-1 Region.
Source - Official statement
We are seeing early signs of recovery for the elevated API error rates and launch failures in the AP-NORTHEAST-1 Region.
Source - Official statement
We continue to see broad signs of recovery in the AP-NORTHEAST-1 Region.
Source - Official statement
We continue to work towards full recovery.
Source - Official statement
We continue to work towards full recovery.
Source - Official statement
Between 6:46 AM and 9:46 AM PST, we experienced elevated API error rates and launch failures primarily centered in a single Availability Zone (apne1-az1).
Source - Status changed
Status changed: investigating → resolved (official status page reports resolution).
- Official statement
✅ Resolved: Amazon Web Services (AWS) - Amazon Elastic Compute Cloud (Tokyo): [RESOLVED] Elevated API issues and Launch Failures
Source
Evidence
9 reports · 7 Status, 2 BlueskyShow
- [1]Status First reportService impact: Elevated API issues and Launch Failures(opens official status page in a new tab)
We are experiencing elevated API error rates and launch failures in the AP-NORTHEAST-1 Region. Launch failures appear to be concentrated in a single Availability Zone (apne1-az1). We are working to identify the root cause and mitigate the issue.
by aws status
- [2]Bluesky⚠️ Amazon Web Services (AWS) is reporting an incident: Amazon Elastic Compute Cloud (Tokyo): Elevated API issues and Launch Failures(opens the official status page in a new tab)
⚠️ Amazon Web Services (AWS) is reporting an incident: Amazon Elastic Compute Cloud (Tokyo): Elevated API issues and Launch Failures Investigating: We are experiencing elevated API error rates and launch failures in the AP-NORTHEAST-1 Region. Launch failures appear to be concentr… t.lpl.dev/eV8jpxJ
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 1comments94% match
- [3]StatusService impact: Elevated API issues and Launch Failures(opens official status page in a new tab)
We are experiencing elevated API error rates and launch failures in the AP-NORTHEAST-1 Region. While launch failures still appear to be concentrated in a single Availability Zone (apne1-az1), we are now seeing low levels of launch failures in other availability zones as well. Cloudwatch alarms for EC2 and EBS resources in the affected Availability Zone are transitioning into Insufficient Data state and alarms configured to alert off of Insufficient Data may transition to Alert state. The…
by aws status97% match
- [4]StatusService impact: Elevated API issues and Launch Failures(opens official status page in a new tab)
We are seeing early signs of recovery for the elevated API error rates and launch failures in the AP-NORTHEAST-1 Region. EC2 and EBS CloudWatch health data is now reporting correctly. We will continue to monitor the progress of our recovery efforts and will provide you with another update by 10:00 AM PST or sooner as new information becomes available.
by aws status91% match
- [5]StatusService impact: Elevated API issues and Launch Failures(opens official status page in a new tab)
We continue to see broad signs of recovery in the AP-NORTHEAST-1 Region. Our mitigation efforts are still underway, and we will provide you with another update on our progress by 10:45 AM PST or sooner as new information becomes available.
by aws status94% match
- [6]StatusService impact: Elevated API issues and Launch Failures(opens official status page in a new tab)
We continue to work towards full recovery. We are observing some connectivity issues to newly created or modified instances in a single Availability Zone (apne1-az1). This affects actions such as new instance launches, new cluster creation, autoscaling groups, gateways, and vpc gateway endpoints. Connectivity to existing resources and Instance to Instance communication are not impacted. We have identified the root cause of this new issue and are working to mitigate the issue. We will provide…
by aws status95% match
- [7]StatusService impact: Elevated API issues and Launch Failures(opens official status page in a new tab)
We continue to work towards full recovery. Customers can launch new instances in the other two healthy Availability Zones (apne1-az2, apne1-az3). We also recommend that customers do not make changes that would impact connectivity to existing instances in the affected Availability Zone. This includes actions such as attaching and detaching network interfaces or gateways as well as VPC Peerings changes. We continue to work on resolving the intermittent connectivity issues to newly created or…
by aws status95% match
- [8]StatusService is operating normally: [RESOLVED] Elevated API issues and Launch Failures(opens official status page in a new tab)
Between 6:46 AM and 9:46 AM PST, we experienced elevated API error rates and launch failures primarily centered in a single Availability Zone (apne1-az1). We also experienced impact to other services such as ECS and Fargate Task Launch failures, ELB provisioning delays, Nat Gateway failures for Create and Disassociate workflows and Managed Flink application state transitions delays. Running EC2 instances and existing workflows were not affected. During this time, EC2 and EBS health data was…
by aws status94% match
- [9]Bluesky✅ Resolved: Amazon Web Services (AWS) - Amazon Elastic Compute Cloud (Tokyo): [RESOLVED] Elevated API issues and Launch Failures(opens the official status page in a new tab)
✅ Resolved: Amazon Web Services (AWS) - Amazon Elastic Compute Cloud (Tokyo): [RESOLVED] Elevated API issues and Launch Failures
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 0comments91% match
FAQ
What happened in the AWS outage?
AWS experienced elevated API error rates, EC2 launch failures, and connectivity issues primarily centered in the AP-NORTHEAST-1 Region (specifically Availability Zone apne1-az1). The incident also affected ECS and Fargate task launches, ELB provisioning, NAT Gateway workflows, and Managed Flink state transitions before being fully resolved.
What is affected by the AWS outage?
AWS.
When did the AWS outage start and end?
It started Nov 11, 15:40 UTC and was resolved Nov 11, 21:11 UTC, after 5 h 30 min.
How do I get alerts for AWS?
Subscribe to the AWS RSS feed for every new AWS incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether AWS is down. AWS feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 9 reports from 2 independent sources, including the vendor’s own status page.