AWS

⚪ AWS S3 in EU-CENTRAL-2 spent nearly an hour literally unable to PUT or GET its act together. Turns out the bytes weren't having it. Someone unplugged the reassembly line, plugged it back in, problem solved. Apparently AWS stores data like IKEA furniture—occasionally needs angry intervention.

⏰ Mar 07, 2026 FYI spotted via status_rss

// The official story

Service is operating normally: [RESOLVED] Increased Error Rates

// Status page says

Between 11:27 AM and 12:20 PM PST we experienced substantial error rates for S3 PUT/GET requests in EU-CENTRAL-2 Region. Engineers were engaged immediately based on automated alarming. We identified the root cause as an issue with a subsystem responsible for assembling objects bytes in storage. At 12:04 PM PST, we implemented mitigations and began observing early signs of recovery for S3. Error rates continued to improve, and other AWS Services continued to recover until 12:50 PM PST when we obs

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