AWS

🔴 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.

⏰ 1h ago It's bad spotted via status_rss

// The official story

Service impact: Increased invoke error rates

// Status page says

Between 7:27 AM and 8:47 AM PDT, and between 10:47 AM and 4:15 PM PDT, we experienced intermittent invoke error rates and latencies for HTTP APIs in the US-WEST-2 Region. During this time, customers would have observed increased latency or errors when invoking HTTP APIs, with elevated errors occurring between 3:12 PM and 3:45 PM PDT. This represented the period of highest customer impact with the majority of affected customers experiencing errors or increased latencies during this window. Majori

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