AWS outage on May 7, 2026
AWS appears mostly operational, but Isitreallydown?'s test connections are failing in me-south-1 (Manama, Bahrain), which is 1 of 37 AWS regions. User reports are quiet and other regions are reporting normal health, suggesting this degradation is isolated to the Middle East region.
Cached · Mon, May 11, 2026, 01:37 PM UTC · scope: service signals
Status changed to Operational
The stored readout moved to Operational with confidence 55.00.
Incident detected
Major confidence crossed the incident threshold for AWS US-EAST-1 thermal event — power loss in single AZ.
Status changed to Possible Issues
The stored readout moved to Possible Issues with confidence 32.00.
Status changed to Operational
The stored readout moved to Operational with confidence 55.00.
Marked resolved
The incident was closed after 19h of observed impact.
- News scan
News: Too Early — No matching news yet for this signal.
— - Cloud scope
Cloud impact scope: [Object Object] — Provider-level impact correlation flagged this scope.
[Object Object]
Confidence scoring
85.00The incident reached 85.00 peak confidence across 200 stored status snapshots.
User reports
0 / 15mNo elevated user-report volume was preserved in the incident window snapshots.
Status samples
3 affected3 snapshots in the window showed degraded, recovering, or major-outage state before recovery.
Recovery signal
ResolvedRecovery was recorded at Fri, May 08, 2026, 05:00 PM UTC.
AWS users likely saw failed connections, degraded availability, or session instability for this Cloud service. The incident reached Major severity and lasted 19h. The stored report window does not show a preserved user-report spike.