Isitreallydown?
// Incident Post-MortemDRN-F1212CEE

Cloudflare outage on May 6, 2026

Major severityResolved45 minCloud
Started · UTC
May 06, 09:30 AM
6d ago
Resolved · UTC
May 06, 10:15 AM
6d ago
Duration
45 min
End-to-end
Peak confidence
80.00
23 snapshots
// What happened

Www's official status page is reporting maintenance affecting SYD (Sydney) on 2026-05-11. All 337 CLOUDFLARE regions are reporting healthy. Isitreallydown?'s synthetic checks are not yet measured, DNS is resolving normally, user reports are quiet. Current signals suggest this is component-specific rather than a broad Cloudflare outage. Other news: Cloudflare Status also reported on Cloudflare in the last 24h — "Cloudflare is investigating network performance issues in Chicago.". This does not appear tied to the current signal.

Cached · Sun, May 10, 2026, 03:32 PM UTC · scope: service signals

// Timeline

  1. Status changed to Operational

    The stored readout moved to Operational with confidence 75.00.

  2. Incident detected

    Major confidence crossed the incident threshold for R2 enablement temporarily degraded on Dash (09:30–10:06 UTC).

  3. Marked resolved

    The incident was closed after 45 min of observed impact.

// Signals by source1 sources
  • Reachability

    Synthetic probes hit 100% success — 289ms avg

    100%
// Aggregate evidence

Confidence scoring

80.00

The incident reached 80.00 peak confidence across 23 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 Wed, May 06, 2026, 10:15 AM UTC.

// User impact

Cloudflare 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.