← Back to the carnage
AWS

βšͺ πŸ”Œ 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)

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

// The official story

Service is operating normally: [RESOLVED] Connectivity Issues

// Status page says

Between 3:55 AM and 4:15 AM PDT, we experienced connectivity issues that impacted connectivity to the US-WEST-2 Region. This impacted multiple AWS services in the Region. Some customers may have also experienced issues accessing the AWS Management Console, with connection timeouts and unresponsive pages. Connectivity within the Region was not affected. Our engineers were automatically engaged at 4:01 AM PDT, and immediately began investigating this issue. We identified the root cause as an issue

πŸ”— 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 18, 2026
βšͺ Your AWS costs looked like they took a steroids cycle, but relaxβ€”the actual invoice won't bankrupt you. Estimated billing data hallucinated numbers between July 16-17 while alarms watched like useless security cameras. The good news: only your heart rate was affected, not your credit card.