← Back to the carnage
AWS
🔴 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)
// The official story
Service is operating normally: [RESOLVED] Elevated Launch Failures
// Status page says
Between 2:35 PM and 4:21 PM PST, we experienced elevated EC2 instance launch failures affecting all AZs (usw2-az1, usw2-az2, usw2-az3, usw2-az4) in the US-WEST-2 Region. EC2 Instance Launches, AWS services that instantiated new instances, as well as services such as DataSync or AWS Backup which require new instances to support data transfers to or from the US-WEST-2 Region were affected. Our engineers were automatically engaged and immediately began investigating the root cause. We identified th
🔗 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 11, 2026
🟢 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.
🟢 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)