Isitreallydown?
// Incident Post-MortemDRN-7B43C5E5

AWS outage on March 3, 2026

Major severityResolved45 minCloud
Started · UTC
Mar 03, 06:27 AM
70d ago
Resolved · UTC
Mar 03, 07:12 AM
70d ago
Duration
45 min
End-to-end
Peak confidence
80.00
0 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. Incident detected

    Major confidence crossed the incident threshold for Service impact: Increased Connectivity Issues and API Error Rates.

  2. Marked resolved

    The incident was closed after 45 min of observed impact.

// Signals by source0 sources

No per-source signal payloads were preserved in this incident's snapshot window.

// Aggregate evidence

Confidence scoring

80.00

The incident reached 80.00 peak confidence across available 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 Tue, Mar 03, 2026, 07:12 AM 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.