AWS Service Disruption Affecting Multiple Systems
Is it fixed? Yes.
Resolved after <1 min. First reported Nov 13, 23:58 UTC, resolved Nov 13, 23:58 UTC. It never appeared on the vendor’s status page.
What happened
An AWS service disruption occurred, impacting various cloud infrastructure systems and prompting widespread reports.
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
aws.amazon.com/message/1019...
Source - Status changed
Status changed: investigating → resolved (no new reports for 48h).
Evidence
1 report · 1 BlueskyShow
- [1]Bluesky First reportaws.amazon.com/message/1019...(opens Bluesky post in a new tab)
aws.amazon.com/message/1019... status.cloud.google.com/incident/clo... + 1,000,000 other examples
by drunk.moe 6upvotes 0comments
FAQ
What happened in the AWS outage?
An AWS service disruption occurred, impacting various cloud infrastructure systems and prompting widespread reports.
What is affected by the AWS outage?
AWS.
When did the AWS outage start and end?
It started Nov 13, 23:58 UTC and was resolved Nov 13, 23:58 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.