AWS outage on May 3, 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 75.00.
Incident detected
Major confidence crossed the incident threshold for AWS.
Status changed to Possible Issues
The stored readout moved to Possible Issues with confidence 34.00.
Status changed to Major Outage
The stored readout moved to Major Outage with confidence 44.00.
Marked resolved
The incident was closed after 2d 9h of observed impact.
- Reachability
Synthetic probes hit 100% success — 105ms avg
100% - News scan
News: Confirms — Amazon's Middle East data centers in Bahrain (ME-SOUTH-1) were damaged by Iran drone/missile attacks and are expected to be down for months during repairs, indicating a disruption near Manama.
Major - Cloud scope
Cloud impact scope: [Object Object] — Provider-level impact correlation flagged this scope.
[Object Object]
Confidence scoring
80.00The incident reached 80.00 peak confidence across 21 stored status snapshots.
User reports
0 / 15mNo elevated user-report volume was preserved in the incident window snapshots.
Status samples
15 affected15 snapshots in the window showed degraded, recovering, or major-outage state before recovery.
Recovery signal
ResolvedRecovery was recorded at Wed, May 06, 2026, 02:00 AM UTC.
AWS users likely saw failed connections, degraded availability, or session instability for this Cloud service. The incident reached Major severity and lasted 2d 9h. The stored report window does not show a preserved user-report spike.