AWS

🔴 AWS Direct Connect ghosted US-EAST-1 customers for 6 hours straight. A routine deployment decided to weaponize a subsystem, turning a minor hiccup into a full regional meltdown by afternoon. Engineers showed up fashionably late to the party.

⏰ Feb 21, 2026 FYI spotted via status_rss

// The official story

Service is operating normally: [RESOLVED] AWS Direct Connect Connectivity Issues

// Status page says

Between 11:41 AM PST and 5:45 PM PST, we experienced connectivity issues for some AWS Direct Connect Customers in the US-EAST-1 Region. While the issue was introduced at 11:41 AM PST, impact was limited until approximately 1:30 PM PST when impact grew as a result of a subsystem deployment. Our automated deployment takes approximately 12 hours so impact stayed limited to a subset of customers until we began observing broader impact at approximately 3:00 PM PST. Engineers were engaged and began i

🔗 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)