AWS US-EAST-1 Outage Disrupts Cloud Operations
Is it fixed? Yes.
Resolved after <1 min. First reported Nov 16, 04:05 UTC, resolved Nov 16, 04:05 UTC. It never appeared on the vendor’s status page.
What happened
An hours-long outage in the AWS US-EAST-1 region disrupted cloud operations before services were restored.
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 Restores Services in US-EAST-1 After Hours-Long Outage Disrupts Cloud Operations
Source - Status changed
Status changed: investigating → resolved (no new reports for 48h).
Evidence
1 report · 1 BlueskyShow
- [1]Bluesky First reportAWS Restores Services in US-EAST-1 After Hours-Long Outage Disrupts Cloud Operations(opens Bluesky post in a new tab)
AWS Restores Services in US-EAST-1 After Hours-Long Outage Disrupts Cloud Operations
by infosec.skyfleet.blue 3upvotes 1comments
FAQ
What happened in the AWS outage?
An hours-long outage in the AWS US-EAST-1 region disrupted cloud operations before services were restored.
What is affected by the AWS outage?
AWS.
When did the AWS outage start and end?
It started Nov 16, 04:05 UTC and was resolved Nov 16, 04:05 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.