Live / Amazon Web Services / Incident
Amazon Web Services: [RESOLVED] Elevated API issues and Launch Failures — Tokyo
Amazon Web Services · aws.amazon.comResolved2026-11-11 21:11 UTC
Public — what happened
Summary
Amazon Web Services said it saw higher error rates and failed launches of new computing instances in its Tokyo region, starting at 15:40 UTC on 2026-11-11, mostly in one availability zone (apne1-az1). It said other services that rely on those functions, including Auto Scaling, ECS and RDS, were also affected, while already running instances were not. AWS said it identified a root cause and worked on a fix; its final update said errors were reduced first, then later connectivity problems for new or changed instances were fully resolved. The incident was marked resolved at 21:11 UTC, and AWS recommended that customers retry any requests or workflows that failed.
Timeline
- Started — 2026-11-11 15:40 UTC
- Investigating — 2026-11-11 15:40 UTC (6 updates)
- Update — 2026-11-11 21:11 UTC
- Resolved — 2026-11-11 21:11 UTC · 5h 31m after it started
What SquidGrid measured
SquidGrid measured 74 internet paths into Amazon Web Services’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Amazon Web Services against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Amazon Web Services: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Amazon Web Services report →
More from Amazon Web Services
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.