rewindex

ChangesAmazon Web ServicesElevated API issues and Launch Failures (ap-northeast-1)

Amazon Web Services: Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)

Incident updateNormal progress (rule, 100%)Changed health.aws.amazon.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Amazon Web Services removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: resolved
AddedResolved time#2
Before: not present
After: 2026-11-11 21:11 UTC
AddedUpdateresolved#3
Before: not present
After: 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 missing or delayed for the affected Availability Zone resulting in CloudWatch alarms to transition to INSUFFICENT_DATA state and the DescribeInstanceStatus API to return Insufficient Data. We had identified the root cause and began our mitigation efforts by 7:47 AM, and by 9:46 AM we were seeing broad recovery for APIs and were able to see new EC2 launches succeed. While monitoring for full recovery, we began to observe that new launches in the single affected Availability Zone were experiencing connectivity issues, instance to instance connectivity was unaffected as was instances launched before the impact began. We were able to identify that this shared a root cause to the initial issue. We took multiple parallel paths to mitigate the connectivity issue, and saw first signs of recovery for the connectivity issue at 11:51 AM and full recovery by 12:31 PM. The issue has been resolved and the service is operating normally.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

TodayThursday, November 12Thu, Nov 12

3 rewrites, 1 incident change

YesterdayWednesday, November 11Wed, Nov 11

7 rewrites, 10 incident changes

Cite this

Incident updated: Elevated API issues and Launch Failures (ap-northeast-1) on Amazon Web Services’s status page, changed 2026-11-11 21:13 UTC (change 16 of 21).

Title
Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)
Vendor
Amazon Web Services
Date
URL
https://rewindex.com/change/r12d97e53213c05

All Amazon Web Services changesAmazon Web Services profileMarkdownJSON