Is Cloudflare Down Right Now?
Developer and sysadmin guide to Cloudflare status — check CDN, DNS, Workers, and WAF availability, with error codes and region-specific troubleshooting.
Check Cloudflare Status
Cloudflare publishes a live incident page with per-region and per-service status:
Cloudflare Service Components
Cloudflare is a multi-service platform — each product can be degraded independently. Identify which component is affected before troubleshooting:
Content delivery and reverse proxy across 300+ locations
Authoritative DNS and public resolver infrastructure
Serverless compute at the edge in 300+ cities
Web Application Firewall and DDoS mitigation
S3-compatible object storage without egress fees
Jamstack hosting and deployment platform
ZTNA, Tunnel, and Access gateway services
Video streaming and encoding platform
Common Cloudflare Error Codes & Fixes
521 Web Server Is DownOrigin server refusing Cloudflare connectionsFix: Whitelist Cloudflare IP ranges in your origin firewall
522 Connection Timed OutOrigin server not responding within timeout windowFix: Check origin server load; increase timeout in Cloudflare config
524 A Timeout OccurredOrigin took too long to complete responseFix: Optimize origin response time or increase timeout to 100s+
525 SSL Handshake FailedSSL/TLS negotiation failed between Cloudflare and originFix: Check SSL mode (Full vs Full Strict) and origin certificate validity
1020 Access DeniedWAF rule or Firewall rule blocking the requestFix: Review WAF and Firewall rules in Cloudflare dashboard
1101 Worker ErrorCloudflare Worker script threw an uncaught exceptionFix: Check Worker logs in Cloudflare dashboard; review script error handling
🌍 Cloudflare Outages Are Usually Regional
Unlike most services, Cloudflare outages often affect only specific data centers or regions. A full global outage is extremely rare — Cloudflare operates 300+ Points of Presence that can reroute traffic automatically.
When checking status, look for the specific PoP or region affecting your users (e.g., "Frankfurt," "US East Coast," "APAC"). Your monitoring alerts should include geographic context.
How to Monitor Cloudflare Regionally
- • Subscribe to cloudflarestatus.com email/SMS updates
- • Use Better Stack to monitor your origin (bypasses Cloudflare cache)
- • Set up alerts on both your Cloudflare-proxied domain AND origin IP
- • Use
curl -o /dev/null -s -w "%{http_code}"from multiple regions
Troubleshooting Cloudflare Issues
Check cloudflarestatus.com first
The official Cloudflare status page shows live status per product and region. Incidents are typically posted within 5-10 minutes of detection.
Use development mode to bypass cache
In Cloudflare dashboard → Caching → Configuration → enable Development Mode. This temporarily disables caching and serves requests directly from your origin, helping isolate whether the issue is Cloudflare or your origin.
Check your origin server independently
Test your origin directly using its IP address (bypassing Cloudflare DNS) with curl -H "Host: yourdomain.com" http://ORIGIN_IP/. If your origin responds, the problem is in Cloudflare configuration.
Monitor with independent uptime tools
Don't rely on Cloudflare to monitor Cloudflare. Use Better Stack or similar to monitor your site from external networks with no Cloudflare dependency.
Related Guides
Frequently Asked Questions
Is Cloudflare down right now?
To check if Cloudflare is down, visit the official Cloudflare status page at www.cloudflarestatus.com. Cloudflare operates globally across 300+ data centers — outages are often regional, not global. Check the status page for specific PoP (Point of Presence) locations. You can also check APIStatusCheck.com/api/cloudflare for third-party monitoring data.
What causes Cloudflare 521 and 522 errors?
Error 521 means Cloudflare cannot connect to your origin web server — your origin is refusing connections (firewall blocking Cloudflare IPs, origin server down, or wrong port). Error 522 is a connection timeout — Cloudflare reached your origin but it did not respond in time. Fix 521: whitelist Cloudflare IP ranges in your origin firewall. Fix 522: check origin server load and increase connection timeout settings.
Why is Cloudflare DNS not working?
Cloudflare DNS failures can be caused by: (1) Global DNS infrastructure incidents — check cloudflarestatus.com, (2) DNS propagation delay after making changes (can take up to 48 hours for external TTL expiry), (3) Incorrect DNS records in your Cloudflare dashboard, (4) CAA records blocking SSL certificate issuance, (5) DNSSEC misconfiguration. Use dig or nslookup to verify your DNS records are resolving correctly.
How do I bypass Cloudflare if it is down?
If Cloudflare is causing issues, you can temporarily bypass it by: (1) Setting DNS records to "DNS only" (gray cloud) instead of "Proxied" (orange cloud) — this bypasses Cloudflare CDN while keeping DNS, (2) Pointing your A record directly to your origin IP, (3) Using the Development Mode toggle in Cloudflare dashboard to bypass cache. Note: bypassing removes DDoS protection and CDN benefits.
How long do Cloudflare outages usually last?
Most Cloudflare incidents are resolved within 15-60 minutes. Regional outages affecting a single data center are often resolved in under 30 minutes as traffic reroutes to nearby PoPs. Global incidents are rare — Cloudflare's redundant architecture means a single PoP failure usually auto-recovers without user impact.