How to Fix Claude Cloudflare Error Pages (520, 524)

When attempting to log into or use Claude, you may suddenly be blocked by a Cloudflare-branded landing page. These pages typically show error codes such as Error 520 (Web server is returning an unknown error), Error 524 (A timeout occurred), or security verification challenges that loop endlessly. Because Anthropic uses Cloudflare as its reverse proxy and security gateway, these errors occur when Cloudflare cannot establish a stable network handoff to Claude’s internal servers. Use this troubleshooting guide to resolve Cloudflare-specific connection blocks.

Step 1: Note and Decipher the Cloudflare Error Code Cloudflare error screens contain crucial diagnostic information at the bottom of the page. Identifying the code tells you whether to fix a local setting or wait out a server-side issue.

1. Look at the title of the error page.
2. Error 520 / 522: These indicate that Anthropic’s origin servers returned an empty, unknown, or unexpected response to Cloudflare. This is almost always an internal Anthropic infrastructure issue.
3. Error 524: This means Cloudflare completed a successful connection to Anthropic's servers, but those servers took too long to respond to the request (usually exceeding Cloudflare’s default 100-second timeout). This happens during extreme server capacity limits.
4. Error 1020 / Security Block: This means Cloudflare’s Web Application Firewall (WAF) flagged your IP address, browser footprint, or request patterns as malicious.

Step 2: Clear Edge Cache and Hard Refresh If Anthropic has patched an internal server error, your browser may still be stuck attempting to load the cached Cloudflare error page from an edge node.

1. Force your browser to bypass its local cache. On Windows/Linux, press Ctrl + F5 or Ctrl + Shift + R. On macOS, hold Shift and click the browser's reload icon.
2. If the error persists, open your browser’s Developer Tools by pressing F12 or Ctrl + Shift + I.
3. Navigate to the Application (or Storage) tab, select Clear Site Data, and refresh the tab.

Step 3: Solve or Bypass Endless Security Loops If you are stuck in a loop where Cloudflare repeatedly asks you to check a box to "Verify you are human" but never redirects you to Claude, your browser privacy configurations or extensions are likely interfering with the challenge script.

1. Disable any aggressive ad-blockers, script-blockers, or privacy extensions (such as uBlock Origin, Privacy Badger, or NoScript) temporarily.
2. Ensure your browser's third-party cookie settings are enabled. Cloudflare requires temporary cookies to track successful security clearances.
3. Try logging in using a clean browser profile or alternative browser (e.g., switching from Chrome to Firefox or Safari) to see if local browser extensions are triggering the security system.

Step 4: Reset Local Routing and Change DNS If your local network routing to Cloudflare's nearest edge node is degraded, you can force a routing recalculation.

1. Restart your router and modem. Unplug them from power for 30 seconds, then reconnect them to clear the routing cache of your physical hardware.
2. Switch your device's DNS servers. Sometimes local ISP DNS servers point to stale or slow Cloudflare IP blocks. Update your network adapter to use Google Public DNS (8.8.8.8 / 8.8.4.4) or Cloudflare Public DNS (1.1.1.1 / 1.0.0.1).

Step 5: Toggle VPN or Change Network Location If Cloudflare's firewall has temporarily blacklisted your specific IP address block (common on shared apartment networks, office networks, or public Wi-Fi), you must acquire a new IP address to access Claude.

1. If you are using a VPN, disconnect it. Cloudflare often flags commercial VPN exit nodes due to high traffic volumes from those IPs.
2. If you are not using a VPN, turn one on. Choose a nearby node to change your external IP address while keeping latency low.
3. Alternatively, switch your device to your smartphone's mobile data connection to verify if the block is restricted to your broadband connection.

When to escalate If you cannot bypass a Cloudflare error page after completing these steps, locate the **Ray ID** string at the very bottom of the error screen (e.g., `Ray ID: 8abc1234def56789`). This unique identifier tracks your exact connection path. Copy this ID and paste it into a support ticket sent to Anthropic Support. They can use the Ray ID to look up Cloudflare's server logs and determine exactly why your connection was rejected or timed out.