← Back to the carnage
AWS
⚪ 🔧 AWS's edge locations forgot how to resolve domains, returning NXDOMAIN errors like a disgruntled librarian refusing to check the card catalog. The fix? Nuking the affected DNS servers from orbit. Propagation delays dragged on until evening, because why resolve things quickly when you can resolve them *dramatically*?. (Auto-resolved: no updates in 24h)
// The official story
Service is operating normally: [RESOLVED] Change Propagation Delays
// Status page says
Between 12:20 PM and 1:55 PM PST, we experienced elevated DNS resolution errors for CloudFront distributions served from a subset of edge locations globally. During this time, customers may have received NXDOMAIN responses. Engineers were automatically engaged, immediately began investigating in multiple parallel paths and mitigated errors by taking the affected fleet of DNS servers out of service. Additionally, between 12:20 PM and 8:08 PM PST, we experienced longer than usual propagation time
🔗 Official status page (for the PR-approved version)
https://status.aws.amazon.com/Aws's Greatest Hits
🟢 AWS
3d 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
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)