Live  /  Providers  /  Cloudflare

Cloudflare

cloudflare.comReporting incidents

Independent assessment — SquidGrid is not affiliated with Cloudflare. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

CDN & edge · SquidGrid tracks Cloudflare’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Cloudflare is reporting

Current & recent incidents

identified

Network Performance Degradation — Asia-Pacific

Minor impact · 2026-09-25 08:50 UTC

identified

Cloudflare One Clients are incorrectly challenged on some sites

Minor impact · 2026-09-23 11:02 UTC

Resolved

Network Performance Issues in Eastern North America

None impact · 2026-09-28 20:36 UTC

Resolved

Replicate Flux Hotswap Models Stuck

Minor impact · 2026-09-28 20:28 UTC

Resolved

R2 Service Issues in Western North America (WNAM)

None impact · 2026-09-26 18:06 UTC

Resolved

Cloudflare Cloud Access Security Broker (CASB) Issues

Minor impact · 2026-09-26 10:58 UTC

Resolved

Issues with Durable Objects

Minor impact · 2026-09-25 14:49 UTC

Resolved

Secondary DNS Update Delays

Minor impact · 2026-09-25 10:10 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Cloudflare has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

SquidGrid’s own measurement fleet is watching 39,587 internet paths that cross Cloudflare’s network, observed from 99 countries. At last check (02:45 UTC), every measured path within its usual range. Signed-in customers see which paths, the carrier on each side, and the added latency.

SquidGrid is not affiliated with Cloudflare.