Isitreallydown?
// Incident Post-MortemDRN-2A47F07E

Cloudflare outage on May 7, 2026

Minor severityResolved45 minCloud
Started · UTC
May 07, 09:00 PM
5d ago
Resolved · UTC
May 07, 09:45 PM
5d ago
Duration
45 min
End-to-end
Peak confidence
25.00
17 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 55.00.

  2. Incident detected

    Minor confidence crossed the incident threshold for Network Connectivity issues in Tokyo.

  3. Marked resolved

    The incident was closed after 45 min of observed impact.

  4. Peak confidence reached

    Confidence peaked at 55.00 while the service was marked Operational.

// Signals by source0 sources

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

// Aggregate evidence

Confidence scoring

25.00

The incident reached 25.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 Thu, May 07, 2026, 09:45 PM UTC.

// User impact

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