# Amazon Web Services: Incident updated: Elevated API issues and Launch Failures (ap-northeast-1) > Incident updated: Elevated API issues and Launch Failures (ap-northeast-1). Detected 2026-11-11 by Rewindex: what changed on Amazon Web Services’s status page, with the before/after diff. Canonical: https://rewindex.com/change/r12d97e53213c05 Last updated: 2026-11-11T21:13:12Z **Summary:** _summary pending_ - Kind: Incident update · Label: Normal progress (rule) - Changed: 2026-11-11 21:13 UTC · Detected: 2026-11-11 21:13 UTC - [Source: https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status) - [Company: Amazon Web Services](https://rewindex.com/company/aws.md) - Versions: before incident\_version:715/ap-northeast-1-aws\_ec2\_operational\_issue\_ec778\_efc270b4609@a776398289f5 → after incident\_version:715/ap-northeast-1-aws\_ec2\_operational\_issue\_ec778\_efc270b4609@defadde24a90 - Change 16 of 21 for this incident Incident page (full timeline): [Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/company/aws/incidents/ap-northeast-1-aws_ec2_operational_issue_ec778_efc270b4609.md) ## What changed **1. Changed: Status** ```diff - investigating + resolved ``` **2. Added: Resolved time** ```diff + 2026-11-11 21:11 UTC ``` **3. Added: Update** (resolved) · 2026-11-11 21:11 UTC ```diff + 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. ``` ## History of this incident | When (UTC) | Change | Label | | --- | --- | --- | | 2026-11-11 15:53 UTC | [Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/rccb24b6a9bb7d3.md) | Normal progress | | 2026-11-11 16:23 UTC | [Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/re4c403d98a6c37.md) | Normal progress | | 2026-11-11 16:33 UTC | [Incident silently edited: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/rbe7c67b1585440.md) | Wording only | | 2026-11-11 16:43 UTC | [Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/rb45a3ccc585ded.md) | Normal progress | | 2026-11-11 16:53 UTC | [Incident silently edited: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r13befa3a8f20e0.md) | Wording only | | 2026-11-11 17:23 UTC | [Incident silently edited: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r8079208ced7460.md) | Normal progress | | 2026-11-11 17:33 UTC | [Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r56b6d7321c88f6.md) | Normal progress | | 2026-11-11 17:43 UTC | [Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/rcb2562f9ecb943.md) | Normal progress | | 2026-11-11 18:03 UTC | [Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r3ab4f32435057a.md) | Normal progress | | 2026-11-11 18:13 UTC | [Incident silently edited: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r74360b3451c50d.md) | Wording only | | 2026-11-11 19:03 UTC | [Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r0c67c7bb757630.md) | Normal progress | | 2026-11-11 19:13 UTC | [Incident silently edited: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r24f8e175699117.md) | Wording only | | 2026-11-11 19:33 UTC | [Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r8091f8b5af4177.md) | Wording only | | 2026-11-11 20:03 UTC | [Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/ra848aad2479d00.md) | Normal progress | | 2026-11-11 20:13 UTC | [Incident silently edited: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r502da0763f39e1.md) | Wording only | | 2026-11-11 21:13 UTC | Incident updated: Elevated API issues and Launch Failures (ap-northeast-1) (this change) | Normal progress | | 2026-11-11 21:33 UTC | [Incident silently edited: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r10c950a016c608.md) | Wording only | | 2026-11-12 01:53 UTC | [Incident silently edited: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r3b2e59886f59df.md) | minor edit | | 2026-11-12 02:23 UTC | [Incident silently edited: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/rbb4b32ee4336f6.md) | Wording only | | 2026-11-12 03:33 UTC | [Incident silently edited: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/r3508aeecbb22cf.md) | Wording only | | 2026-11-12 06:03 UTC | [Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)](https://rewindex.com/change/rdd315c1d6733a7.md) | Wording only | Previous: [change](https://rewindex.com/change/r502da0763f39e1.md) · Next: [change](https://rewindex.com/change/r10c950a016c608.md) · All Amazon Web Services changes: [timeline](https://rewindex.com/company/aws/changes.md) _Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._ ## 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). - Canonical URL: https://rewindex.com/change/r12d97e53213c05 - Citation: Amazon Web Services, “Incident updated: Elevated API issues and Launch Failures (ap-northeast-1)” (2026-11-11 21:13 UTC). Archived by Rewindex: https://rewindex.com/change/r12d97e53213c05 (CC BY 4.0). - Markdown link: `[Amazon Web Services: Incident updated: Elevated API issues and Launch Failures (ap-northeast-1) (2026-11-11)](https://rewindex.com/change/r12d97e53213c05)` --- Canonical: https://rewindex.com/change/r12d97e53213c05 · Markdown: https://rewindex.com/change/r12d97e53213c05.md · JSON: https://rewindex.com/api/v1/changes/r12d97e53213c05 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-12T15:22:01.450Z