← Back to the carnage
AWS

⚪ Two availability zones in São Paulo decided to play silent treatment with each other, tanking API reliability until AWS remembered basic networking. The reconciliation took 33 minutes. Everyone's fine now, probably. (Auto-resolved: no updates in 24h)

⏰ Feb 07, 2026 Fixed (for now) spotted via status_rss

// The official story

Service impact: [Resolved] Network Connectivity

// Status page says

Between 6:36 AM to 7:09 AM PST, we experienced intermittent network connectivity issues between two Availability Zones (sae1-az1 and sae1-az3) in the SA-EAST-1 Region. This issue resulted in API error rates and latencies for AWS Services in the SA-EAST-1 Region. The issue has been resolved and all services are operating normally.

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