Vendor Status Dashboard

Live check

Is Cloudflare down right now?

Checking Cloudflare’s status page…

Fetched live from www.cloudflarestatus.com by your own browser — we never proxy, cache, or fake it.

While you wait: the Cloudflare incident checklist

  1. Work out which plane is failing. Edge/CDN, DNS, or dashboard/API? Control-plane incidents (dashboard, API) can leave traffic flowing untouched; edge incidents mean your users see it. The component list on the status page tells you which fight you're in.
  2. Read the error codes. Cloudflare-branded 521/522/523 pages point at origin connectivity (often your side); widespread Cloudflare-styled 500s point at the edge itself. No cf-ray header at all suggests requests aren't reaching Cloudflare — think DNS.
  3. Correlate by geography. Cloudflare incidents frequently name specific data centers. Map your user reports to regions before declaring a global outage — a POP-level incident looks total from inside one city.
  4. Don't reflexively bypass. Grey-clouding DNS or pointing traffic straight at origin exposes origin IPs, drops WAF/DDoS/rate-limiting, and DNS TTLs make it slow to undo. Sometimes it's right — but it's a decision, not a reflex.
  5. Remember the internal blast radius. If internal tools sit behind Cloudflare Access/Zero Trust, your own team may be locked out of the tools needed to respond. The break-glass path needs to exist before you need it.

What breaks when Cloudflare has issues

Cloudflare sits in the request path, so an edge incident is a your-site-is-down incident for affected regions: 5xx at the edge, TLS failures, or — if your zones use Cloudflare nameservers and the incident touches DNS — domains that stop resolving entirely, email included. Workers, Pages, R2 and KV take application logic and assets down with them; Turnstile can silently break logins; Zero Trust outages lock your engineers out of internal tools mid-response. Even a dashboard-only incident freezes your ability to change DNS or rules while you wait.

FAQ

How do I tell if it's Cloudflare or my origin?

Check the error page and headers: Cloudflare-branded 521/522/523 errors mean the edge couldn't reach your origin — often your side. Uniform errors across many unrelated Cloudflare-fronted sites mean it's them. The status page plus a curl directly against your origin settles it.

Should I take my site off Cloudflare during their outage?

Usually no. Bypassing exposes your origin IPs, drops WAF and DDoS protection, and DNS TTLs mean the change lags in both directions. Consider it only for prolonged incidents with an origin sized for direct traffic.

Is my DNS down too?

Only if your domains use Cloudflare as authoritative DNS and the incident includes DNS. When authoritative DNS fails, everything on the domain fails globally — including email, via MX records.

Does a Cloudflare incident affect internal admin tools?

If they're behind Cloudflare Access, Zero Trust or a Cloudflare Tunnel, yes — which can lock responders out mid-incident. Document a break-glass access path in advance.

Get pinged in your toolbar the moment Cloudflare’s status changes

Vendor Status Dashboard is a Chrome extension for on-call engineers: Cloudflare and every other vendor you depend on, one badge, answer in five seconds. Free for 5 vendors, no account.

Join the waitlist — launching soon

Also on your stack?

Not affiliated with Cloudflare. Status data comes from their public status page.