AWS
// ACTIVE OUTAGES
Service is operating normally: [RESOLVED] Inaccurate Estimated Billing Data
⚪ 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.
Service is operating normally: [RESOLVED] Elevated connectivity issues with a single Avalability zone
🟠 Single availability zone in Frankfurt decided connectivity was optional between 2:56–6:07 PM PDT. EC2 instances ghosted their networks, new launches got participation trophies instead of IP addresses, and several AWS APIs went along for the ride. Technically 'resolved' now, but that's what they always say right before the sequel.
Service is operating normally: [RESOLVED] Increased Launch Template API Error Rates
⚪ 🎭 AWS's Launch Template API decided to take an unscheduled sabbatical between 2:56-6:54 AM PDT, turning template creation into a coin flip. Running instances shrugged and kept chugging, but anyone trying to spawn new resources got the silent treatment. Even services downstream realized their templates weren't coming home for dinner.
Service is operating normally: [RESOLVED] Increased Error Rates and Latencies
⚪ EC2 APIs in EU-North-1 decided to take a 43-minute siesta between 1:42-2:25 PM PDT, rejecting new instance launches with the classic 'Internal Server Error' move. Existing instances watched from the sidelines unharmed. The irony of a service designed for infinite scaling hitting the pause button is not lost on us.
Service is operating normally: [RESOLVED] Increased Connectivity Issues
🟡 AWS's euw3-az2 decided to play dead for 42 minutes—EC2 launches failed, instances ghosted their users, EBS volumes went full Houdini. Root cause: something got lost in translation, literally. All better now, probably.
Service is operating normally: [RESOLVED] Increased Error Rates
⚪ 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.
// INCIDENT HISTORY
// ABOUT AWS MONITORING
What Broke Today monitors AWS and 90+ other services in real time. Our AI-powered system checks status pages every 5 minutes, filters out noise from planned maintenance, and delivers snarky, human-readable outage summaries.
When AWS goes down, you'll know before your boss asks. Track outages, review incident history, and stay ahead of infrastructure issues.
Get instant alerts when things break.
// ADD AWS STATUS TO YOUR README
Real-time status badge for AWS. Updates automatically.
