← Back to the carnage
AWS
⚪ 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)
// The official story
Service is operating normally: [RESOLVED] Increased Packet loss
// Status page says
Starting August 14 7:33 PM PDT, we experienced increased packet loss impacting AWS Direct Connect connectivity for customers with connections at the Equinix FR5 location in Frankfurt, DEU. Engineers were automatically engaged at 7:45 PM on August 14 and immediately began investigating mitigations. By 8:30 PM, we identified that network equipment at the FR5 location was impaired due to water ingress into the co-location facility. As a result, cooling system was impaired which resulted in devices
🔗 Official status page (for the PR-approved version)
https://status.aws.amazon.com/Aws's Greatest Hits
⚪ AWS
10h 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 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)