Isitreallydown?
// Incident Post-MortemDRN-F2D963A5

AWS outage on May 8, 2026

Major severityResolved45 minCloud
Started · UTC
May 08, 01:51 PM
4d ago
Resolved · UTC
May 08, 02:36 PM
4d ago
Duration
45 min
End-to-end
Peak confidence
80.00
17 snapshots
// What happened

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

// Timeline

  1. Status changed to Operational

    The stored readout moved to Operational with confidence 55.00.

  2. Incident detected

    Major confidence crossed the incident threshold for Service impact: Increased Error Rate and Latency.

  3. Marked resolved

    The incident was closed after 45 min of observed impact.

// Signals by source2 sources
  • 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]
// Aggregate evidence

Confidence scoring

80.00

The incident reached 80.00 peak confidence across 17 stored status snapshots.

User reports

0 / 15m

No elevated user-report volume was preserved in the incident window snapshots.

Status samples

0 affected

The incident row exists, but the bounded snapshot window does not include affected status samples.

Recovery signal

Resolved

Recovery was recorded at Fri, May 08, 2026, 02:36 PM UTC.

// User impact

AWS users likely saw failed connections, degraded availability, or session instability for this Cloud service. The incident reached Major severity and lasted 45 min. The stored report window does not show a preserved user-report spike.