How to Fix Claude 502 Bad Gateway Error

A 502 Bad Gateway error on Claude.ai indicates that one server on the internet received an invalid response from another server. In the context of Claude, this typically means the edge servers or reverse proxies (like Cloudflare) cannot communicate properly with Anthropic’s backend application servers.

While this is frequently a server-side issue caused by deployment rollouts or high traffic, local browser states and network configurations can also cause your device to display a cached 502 error long after Anthropic has resolved the underlying problem. Follow these steps to diagnose and bypass the error.

Step 1: Verify Anthropic’s Server Status Before modifying your local system, confirm if the error is widespread. Anthropic maintains a public status page that tracks active incidents. 1. Navigate to `status.anthropic.com` in your web browser. 2. Look at the API and Web App status bars. If you see a major outage or degraded performance listed, the 502 error is server-side. 3. If the status page reports all systems operational, the issue may be local, regional, or cached on your network path.

Step 2: Perform a Hard Refresh Standard browser reloading often loads a cached version of the 502 gateway error page rather than sending a fresh request to Anthropic's servers. 1. On Windows/Linux: Press `Ctrl` + `F5`, or hold `Ctrl` and click the reload button in your browser. 2. On macOS (Chrome/Firefox): Press `Cmd` + `Shift` + `R`. 3. On macOS (Safari): Press `Option` + `Cmd` + `E` to empty the cache, then hold `Shift` and click the reload icon.

Step 3: Clear Claude-Specific Cookies and Cache Corrupted session cookies or stale localized application data can disrupt the handshake between your browser and the gateway. 1. In Google Chrome, click the padlock icon to the left of the URL bar while on `claude.ai`. 2. Select **Site settings** or **Cookies and site data**. 3. Click **Manage on-device site data** and delete the stored data for `claude.ai` and `anthropic.com`. 4. Restart your web browser and attempt to log back in to Claude.

Step 4: Disable VPNs and Custom Proxies Virtual Private Networks (VPNs) and custom proxy servers route your web traffic through alternative intermediary servers. If those intermediary servers have faulty DNS routing or are experiencing high packet loss, they can trigger a 502 Bad Gateway error. 1. Disconnect your current VPN connection. 2. If you are using a proxy server via your operating system settings, temporarily disable it. 3. Load `claude.ai` directly over your standard residential or cellular internet connection to see if the gateway link is restored.

Step 5: Flush Your DNS Cache Stale DNS records cached by your computer or router can route your traffic to an obsolete or offline IP address for Claude's servers. 1. **On Windows:** Open the Command Prompt as an administrator and type `ipconfig /flushdns`, then press `Enter`. 2. **On macOS:** Open Terminal and type `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`, then press `Enter` (you will need to enter your system password). 3. Re-test the connection.

When to escalate If you have completed these steps and still receive a 502 Bad Gateway error, and the official status page shows no outages, the issue is likely a localized regional CDN routing failure on Anthropic's side. Wait 15 to 30 minutes for CDN routes to self-heal. If the issue persists for over an hour, collect your browser console logs (by pressing `F12` and selecting the Console tab) and open a ticket through the help widget on the Anthropic Support page.