How to Fix Claude Error Code 520 Web Server Unknown Error

What is Cloudflare Error 520?

When attempting to send a prompt or load the Claude.ai dashboard, you may occasionally see a branded Cloudflare error page with the headline: "Error 520: Web server is returning an unknown error."

This error is not a problem with your personal computer or internet connection. It is a configuration or performance error occurring between Cloudflare (Claude’s reverse proxy and security layer) and Anthropic’s origin servers. Specifically, it means Anthropic’s server returned an empty, invalid, or unexpected response to Cloudflare, causing Cloudflare to terminate the request because it could not safely interpret the data.

This most commonly happens during high-traffic spikes, partial system outages, or when your browser transmits cookie headers that are too large for the web server to process.

---

Step-by-Step Fixes for Error 520

1. Wait Out the Micro-Outage In 90% of cases, Error 520 is caused by a temporary, seconds-long crash or reboot of an Anthropic origin node. Before changing any local configurations, wait 60 seconds and attempt to resubmit your message or refresh the page. Often, Cloudflare’s load balancers will automatically route your next request to a healthy server node.

2. Strip Excess Browser Cookies for Claude If the origin server's buffer limits are set tightly, it may reject HTTP headers that contain too much cookie data, returning an empty response that triggers a 520 error. Clearing your site-specific cookies usually resolves this.

1. While on claude.ai, press F12 to open the Developer Tools.
2. Go to the Application tab (Chrome/Edge) or Storage tab (Firefox).
3. Expand the Cookies section in the left sidebar and click on https://claude.ai.
4. Click the Clear All icon (a circle with a diagonal line through it) or select all cookies and hit Delete.
5. Refresh the page and log back in.

3. Reduce Prompt Payload and Attachment Sizes If you receive the 520 error specifically when clicking "Submit" on a prompt, the payload you are sending might be triggering an internal server limit.

• If you uploaded large files (PDFs, CSVs, or images), try splitting them into smaller chunks.
• If you pasted an exceptionally long code block or text document, break the prompt into smaller, sequential instructions.
• Ensure you do not have multiple browser tabs attempting to submit long prompts to Claude simultaneously under the same account.

4. Turn Off Outdated browser Extensions Certain web-scraping, AI-assistance, or aggressive ad-blocking extensions can inject custom headers into your outgoing HTTPS requests. These custom headers can cause Anthropic’s firewall to reject the request with an empty response.

1. Open a new Incognito or Private Browsing window where extensions are disabled by default.
2. Navigate to claude.ai and log in.
3. If the error does not repeat, return to your normal browser window, temporarily disable your extensions one by one (starting with ad-blockers and translation tools), and test to isolate the culprit.

5. Force a Route Change via a VPN If a regional CDN edge server is delivering corrupted headers to Anthropic’s central database, routing your traffic through a different location will bypass the faulty edge server.

1. Open your preferred VPN client.
2. Select a server location in a different city or neighboring country where Claude is officially supported.
3. Establish the VPN connection, clear your browser cache, and reload claude.ai.

---

When to Escalate

If you have cleared your cookies, verified your prompt size is small, tested in Incognito mode, and still continuously encounter the Error 520 page for more than 15 minutes, the issue is a sustained backend database or web server error on Anthropic's side.

Since this is an origin-level failure, you cannot fix it locally. Monitor the official Anthropic status page for updates. If you must contact support, take a screenshot of the entire error page—paying special attention to the Ray ID string listed at the bottom of the Cloudflare block page. Email this Ray ID along with details of what you were doing when the error appeared to support@anthropic.com so their DevOps team can trace the specific server failure.