Is Cloudflare Down?

If you're experiencing issues with Cloudflare, try these troubleshooting steps. Since Cloudflare acts as a reverse proxy and CDN for millions of websites, the problem may be on their edge network or on your local configuration.

Basic Steps

• 1. Verify the target website itself – Cloudflare sits in front of websites. If a site is slow or erroring (e.g., 522, 524, 530), check if the site works on a different network (mobile data vs. Wi-Fi) to isolate whether the issue is your connection or the origin server behind Cloudflare.
• 2. Clear your DNS cache and browser cache – Outdated DNS entries can point to stale Cloudflare IPs. Flush your local DNS (e.g., ipconfig /flushdns on Windows or sudo dscacheutil -flushcache on macOS) and hard-refresh your browser (Ctrl+Shift+R).
• 3. Disable proxy/VPN and test direct – Cloudflare uses anycast IPs; a VPN or proxy can route you to a congested edge location. Try disabling them temporarily and re-test.
• 4. Check your local firewall or security software – Some antivirus or router-level security may block Cloudflare's challenge (CAPTCHA or "Just a moment" page). Whititelist cloudflare.com or temporarily disable these tools.
• 5. Test on a different browser or incognito mode – Extensions (ad-blockers, privacy tools) can interfere with Cloudflare's JavaScript challenge. Test in a clean browser profile.

Intermediate Steps

• 1. Inspect the specific HTTP error code – Cloudflare error pages are infamous for codes like 502, 504, 1016, or 1020. Note the exact code: 522 means the origin server is unreachable from Cloudflare, while 524 indicates a timeout on the origin. This tells you whether the fault is on Cloudflare's side or the website's hosting.
• 2. Use Cloudflare's diagnostic tools (via browser) – If you have access to a website that uses Cloudflare, try the cloudflare-dns.com resolver or temporary bypass by appending ?cf_cb=1 to the URL (if the site allows it) to skip the cache. This helps determine if a cached asset is corrupted.
• 3. Check your network's MTU or MTU-related packet loss – Cloudflare's network can be sensitive to improper MTU settings causing random disconnects. Run a ping test with a large packet size (ping -f -l 1400 on Windows) to see if fragmentation occurs.
• 4. Verify TLS/SSL configuration mismatch – If you're suddenly seeing "SSL Handshake Failed" across multiple sites using Cloudflare, your local system time might be out of sync (causing certificate validation failure). Update your OS clock and timezone, then re-test.

If you've tried all the above and Cloudflare is still not loading correctly for you, please click the Report Outage button on this Is It Down Bro? status page. This lets us monitor live reports from other users and helps identify if the issue is widespread on Cloudflare's network rather than a single local setup.