AWS outage on May 9, 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 Possible Issues
The stored readout moved to Possible Issues with confidence 44.00.
Incident detected
Minor confidence crossed the incident threshold for Service is operating normally: [RESOLVED] Increased Error Rate and Latency.
Marked resolved
The incident was closed after 45 min of observed impact.
Peak confidence reached
Confidence peaked at 48.00 while the service was marked Possible Issues.
- Hacker News
1 HN signal mentioned AWS — Stories or comments on Hacker News classified as relevant to this service.
1 hits - News scan
News: Confirms — Multiple outlets report AWS outages affecting North Virginia data center and US-East-1 region, with Coinbase, FanDuel, and other services disrupted; recovery is expected to take hours as cooling and power issues are addressed.
Major - Cloud scope
Cloud impact scope: [Object Object] — Provider-level impact correlation flagged this scope.
[Object Object]
Confidence scoring
45.00The incident reached 45.00 peak confidence across 17 stored status snapshots.
User reports
0 / 15mNo elevated user-report volume was preserved in the incident window snapshots.
Status samples
17 affected17 snapshots in the window showed degraded, recovering, or major-outage state before recovery.
Recovery signal
ResolvedRecovery was recorded at Sat, May 09, 2026, 03:49 AM UTC.
AWS users likely saw failed connections, degraded availability, or session instability for this Cloud service. The incident reached Minor severity and lasted 45 min. The stored report window does not show a preserved user-report spike.