← Back to the carnage
AWS
🟢 AWS's network config update system decided to move at geological time scales, leaving new instances playing hide-and-seek with their public IPs. The good news: they found them eventually. The bad news: it took nearly 4 hours. 🐌
// The official story
Service is operating normally: [RESOLVED] Elevated latencies for network change propagation
// Status page says
Between 7:08 AM and 10:48 AM PST, we experienced elevated latencies for network change propagation in the EU-WEST-1 Region. This was due to a delay in propagation of configuration updates on a sub-system which supports external and cross account connectivity. Customers experienced delays when attempting to connect to newly launched instances using their assigned public IPs, as well as delays in establishing new VPC Peering connections. Other AWS Services were also impacted by this issue and were
🔗 Official status page (for the PR-approved version)
https://status.aws.amazon.com/Aws's Greatest Hits
🟢 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)
🟢 AWS
Aug 16, 2026
🔴 AWS's Frankfurt facility discovered that packets, like tourists, sometimes prefer getting lost. Co-location partner and AWS are having a spirited disagreement about how 'near term' recovery actually works. Spoiler: it's not. (Auto-resolved: no updates in 24h)
🟢 AWS
Jul 31, 2026
⚪ 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)
🟢 AWS
Jul 24, 2026
⚪ 🔌 AWS US-WEST-2 ghosted everyone for 20 minutes between 3:55-4:15 AM PDT, tanking connectivity across multiple services and the Management Console. Engineers showed up fashionably late at 4:01 AM, found the problem, and fixed it before anyone could file a ticket. The region's internal plumbing stayed dry though, so there's that. (Auto-resolved: no updates in 24h)