503RADARINCIDENT ARCHIVEMETHODOLOGY
RESOLVED

Cloudflare outage — June 22, 2026

Customers unable to create Access and Device Enrollment policies via the Dashboard and API

Cloudflare’s Zero Trust / WARP was disrupted for 30d 6h on June 22, 2026. 503Radar’s sensors raised the first signal at 13:38 UTC, 1h 09m before the official status page acknowledged impact.

Key facts

DetectedJune 22, 2026 · 13:38 UTC
Confirmed14:48 UTC · lead time 1h 09m
Resolved19:49 UTC
Duration30d 6h
ServiceZero Trust / WARP
Official recordhttps://stspg.io/b0gt6ktwdnmw

Timeline

  1. 13:38Z

    Detected · Signal

    1 crowd signal for Zero Trust / WARP on CLOUDFLARE crossed the signal threshold.
  2. 14:48Z

    Confirmed · Official

    An official CLOUDFLARE status-page notice corroborated the event — 1h 09m after detection.
  3. 19:49Z

    Resolved

    Signal volume fell back below the threshold; the event was closed.

What people reported

“ℹ️ Minor outage at Cloudflare. Customers cannot create new Access/Device Enrollment policies via Dashboard or API. No impact on authentication or policy enforce”@watchrrnews.bsky.social · 18:36 UTC

How this was detected

1 independent evidence class for zero-trust on CLOUDFLARE. 1 crowd report across bluesky (single platform — not corroborating), z=+0.4σ vs the cell baseline. Official notice confirms it, 1h 09m after the crowd.