← Back to the carnage
AWS

🟢 AWS's Tokyo region decided to ghost API requests for 3 hours straight. EC2 instances stayed chill—only new launches and Fargate got the cold shoulder. The usual suspects (ELB, NAT Gateways, Flink) all developed commitment issues simultaneously.

⏰ Nov 11, 2026 FYI spotted via status_rss

// The official story

Service is operating normally: [RESOLVED] Elevated API issues and Launch Failures

// Status page says

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 miss

🔗 Official status page (for the PR-approved version)

https://status.aws.amazon.com/

Aws's Greatest Hits

🟢 AWS 6d ago
⚪ AWS's identity service decided to play gatekeeper during peak hours, locking out auth-dependent services across the region. Three-hour lockout from 3-6 AM PST hit IAM Identity Center, Connect, and anything else that actually needs login credentials to function. The post-mortem will definitely claim 'cascading network events' instead of 'we broke authentication.'. (Auto-resolved: no updates in 24h)
🟢 AWS Nov 07, 2026
🔴 EC2 instance launches completely ghosted across all four AZs in us-west-2 from 2:35-4:21 PM PST. Anything touching that region—DataSync, Backup, your desperate SpotFleet requests—went belly-up. AWS engineers eventually remembered how instances work again. (Auto-resolved: no updates in 24h)
🟢 AWS Oct 30, 2026
🔴 Lambda's API gateway decided to play dead twice on Tuesday, leaving HTTP requests decomposing in queues. Between 7:27 AM and 4:15 PM PDT, the service kept flubbing invocations like a nervous freshman in a spelling bee. Peak chaos hit 3:12-3:45 PM when errors spiked harder than your coffee consumption. (Auto-resolved: no updates in 24h)
🟢 AWS Aug 18, 2026
⚪ AWS Direct Connect got surprise baptism at Equinix Frankfurt when water decided cooling systems weren't its only calling. Network gear drowned faster than a MacBook in a bathtub, took out packet delivery service for several hours. Plot twist: the real disaster was the infrastructure, not the cloud. (Auto-resolved: no updates in 24h)