AWS Service Disruption and Billing Issues
Is it fixed? Yes.
Resolved after <1 min. First reported Nov 12, 08:04 UTC, resolved Nov 12, 08:04 UTC. It never appeared on the vendor’s status page.
What happened
A social media post mentions a crash and billing issues related to AWS, but provides no technical details.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
This incident was resolved upstream without a reported workaround.
Timeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(current)
- First report on Bluesky post
Nor the chamber of horrors AWS call *massive crash of thunder* billing...
Source - Status changed
Status changed: investigating → resolved (no new reports for 48h).
Evidence
1 report · 1 BlueskyShow
- [1]Bluesky First reportNor the chamber of horrors AWS call *massive crash of thunder* billing...(opens Bluesky post in a new tab)
Nor the chamber of horrors AWS call *massive crash of thunder* billing...
by radiobeartime.com 1upvotes 0comments
FAQ
What happened in the AWS outage?
A social media post mentions a crash and billing issues related to AWS, but provides no technical details.
What is affected by the AWS outage?
AWS.
When did the AWS outage start and end?
It started Nov 12, 08:04 UTC and was resolved Nov 12, 08:04 UTC, after <1 min.
How do I get alerts for AWS?
Subscribe to the AWS RSS feed for every new AWS incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether AWS is down. AWS feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.