Real-time status check for Cloudflare. See if it's just you or everyone experiencing issues.
Cloudflare provides CDN, DDoS protection, DNS, and web application firewall services protecting millions of websites worldwide.
Category: Services | Website: www.cloudflare.com
ipconfig /flushdns or sudo systemd-resolve --flush-caches.Cloudflare provides CDN, DDoS protection, DNS, web application firewall, Workers (serverless edge compute), R2 (object storage), Pages (static site hosting), Tunnel (zero-trust connectivity), and many other internet infrastructure services. It sits in front of millions of websites, processing traffic at edge locations worldwide. When Cloudflare has issues, the impact is immediately visible across a huge fraction of the internet.
Cloudflare outages take several patterns: regional issues (specific edge locations or geographic regions affected), component-specific outages (DNS works but Workers fails, or CDN works but WAF degrades), configuration-related issues (a problematic config push causes errors at edge), and rarely global outages affecting the core platform. The 2022 and 2023 incidents demonstrated how widespread the impact can be when core systems fail.
For status verification, cloudflarestatus.com is the canonical source — shows per-region and per-component status. The @CloudflareStatus Twitter account posts updates. For developers, the Cloudflare blog typically publishes detailed post-mortems for major incidents within days.
Sites behind Cloudflare are affected by Cloudflare outages. During incidents, status pages and customer communication need to happen via channels independent of your own site (Twitter, secondary status page hosted elsewhere) so users can find updates even when your main site is unreachable.
Cloudflare DNS (1.1.1.1 public resolver, plus authoritative DNS for hosted domains) is widely used. Public resolver outages affect home/business users using 1.1.1.1; authoritative DNS outages affect domain resolution for sites hosted on Cloudflare DNS. Have backup resolver configured for resolution; have backup authoritative nameserver configured for hosted domains.
Cloudflare Workers run at edge. Worker outages can affect the application logic served by the worker — different from origin/CDN issues. Have fallback behaviour (e.g. serve cached or static content if Workers fail) coded into your edge logic.
Cloudflare's email security products (Area 1 / Cloudflare Email Security) protect inbound mail. Outages here can delay or drop mail. Have backup mail security paths or accept temporary unprotected mail flow during outages — better than losing mail entirely.
Cloudflare Tunnel provides outbound-only connections from internal services to Cloudflare edge — eliminates need for inbound firewall holes. When Cloudflare is down, internal services accessed this way are unreachable. Have backup VPN access for critical internal services.
Hiding origin IP from public DNS is good security but creates total dependency on Cloudflare. Have a documented mechanism to access origin directly during Cloudflare outages — even if normally firewalled to Cloudflare IPs, an emergency procedure to allow direct admin access matters.
If your site is behind Cloudflare and Cloudflare is down, your status page is also down. Users have no way to find updates. Maintain a status page on a different host (status.io, Statuspage.io, GitHub Pages outside Cloudflare) for incident communication.
For client devices, having only 1.1.1.1 configured means Cloudflare DNS outages break all DNS resolution. Configure secondary resolver (8.8.8.8, Quad9 9.9.9.9) so Cloudflare issues do not break browsing entirely.
When Workers code throws errors or hits rate limits during edge issues, the user-facing impact depends on whether your code degrades gracefully. Always include error handling that falls back to serving cached/static content when Workers fail.
During Cloudflare outages or WAF rule push issues, overly-aggressive WAF rules can block legitimate traffic. Keep WAF in monitoring mode for new rules until verified, alert on unusual block-rate spikes, have a documented fast-disable procedure for problematic rules.
Cloudflare's component-level status page distinguishes DNS, CDN, WAF, Workers, R2, etc. Knowing which is affected determines what mitigation applies. "Cloudflare is down" without knowing which component is too vague to act on.