← Back to the carnage
AWS

⚪ AWS's route-assignment system forgot how to assign routes, turning AP-SOUTH-1 into a packet massacre zone. Someone's config change turned into someone else's 2 AM incident call. Fixed now, but the damage to your SLA is already in the group chat. (Auto-resolved: no updates in 24h)

⏰ Jul 31, 2026 Fixed (for now) spotted via status_rss

// The official story

Service is operating normally: [RESOLVED] Elevated Packet Loss

// Status page says

Between 9:42 AM and 11:44 AM PDT, we experienced elevated network packet loss impacting AWS Direct Connect connectivity in the AP-SOUTH-1 Region. Our engineering team was automatically engaged at 9:46 AM to begin investigating. By 10:51 AM, we understood the root cause to be a configuration change made to a system responsible for assigning routes to devices. As we gained confidence in our mitigation steps, we parallelized our efforts to further reduce the packet loss. The issue is resolved and t

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

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

Aws's Greatest Hits

⚪ AWS 9h ago
🟢 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 5d ago
🔴 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)