Step-by-Step Fix
1) Confirm the exact symptom
Write down the exact message, when it started, and whether it affects one browser/device or everything.
2) Run the two isolation tests
- Incognito/private window
- Second network (phone hotspot, no VPN)
3) Reset browser/session state
- sign out/in
- hard refresh
- clear site data for the Claude site
- disable extensions temporarily
4) Rule out VPN/proxy and network filtering
Disable VPN/proxy and retry once on a stable network.
5) Verify account/workspace context
Confirm you’re using the correct account/workspace for the feature or billing state.
6) Escalate with a clean report
Include: error text, timestamp, region, browser/app + OS, and what you already tested.
Common Root Causes
- stale session/cookies
- extensions blocking requests
- VPN/proxy or network filtering
- wrong account/workspace
- platform-side incident or rollout
Prevention Tips
- keep one clean browser profile for Claude
- avoid rapid retries after errors
- use hotspot + incognito as the first diagnostic step
Why This Happens
Claude's web app communicates via HTTPS and WebSocket connections to Anthropic's API endpoints. A "network error" or "request failed" message means the request never reached Anthropic's servers, or a response was never received. The three most common causes are: (1) a VPN or proxy that routes traffic through a blocked region or a slow tunnel, (2) corporate or school firewall rules that block WebSocket connections (required for streaming responses), and (3) DNS resolution failures where the local resolver cannot reach anthropic.com or claude.ai. Each cause has a distinct fix.
Common Mistakes to Avoid
- Assuming it's Anthropic's fault without checking your own connection. The majority of "network error" reports are caused by local network conditions — VPN, firewall, or DNS — not by Anthropic's servers. Check status.anthropic.com first to confirm there is no active incident before troubleshooting your local setup.
- Keeping VPN enabled while troubleshooting. VPNs are the single most common cause of Claude network errors. Even a VPN that normally works can cause failures when the VPN server is overloaded or routing through a region with restricted access. Always test with VPN disabled before anything else.
- Not trying a mobile hotspot. Switching to a phone hotspot takes 30 seconds and immediately tells you whether the issue is network-specific (corporate firewall, ISP filtering) or device-specific (browser, extensions). If Claude works on hotspot but not your main network, the problem is the network, not Claude.
- Flushing DNS without also changing the DNS server. If your ISP's DNS is blocking or mis-resolving claude.ai, flushing the cache will not help because the bad result will be re-cached. Switch to Google DNS (8.8.8.8) or Cloudflare (1.1.1.1) in your network adapter settings to bypass ISP-level DNS filtering.
- Retrying immediately in a loop. Rapid retries on a failing connection do not fix the underlying issue and can look like an abuse pattern to firewalls, causing temporary IP blocks. Wait at least 60 seconds between retry attempts.
FAQ
Q: What is the difference between "network error" and "request failed" on Claude? Both messages indicate a transport-layer failure, but "network error" typically means the browser could not establish the connection at all (DNS failure, firewall block, or no internet), while "request failed" often means the connection was established but dropped mid-request (WebSocket timeout, server-side rejection, or proxy interruption). The fix steps are similar but WebSocket issues are more likely when you see "request failed" specifically.
Q: Why does Claude work fine in Chrome but give network errors in Firefox? Browser-level WebSocket handling and TLS certificate trust stores differ slightly between Chrome and Firefox. If your corporate network uses SSL inspection (MITM proxy), Chrome may accept the injected certificate while Firefox rejects it with a network error. In Firefox, go to about:preferences#privacy → Certificates → View Certificates and check whether your company's root CA is trusted. Add it if needed, or use Chrome as a workaround.
Q: Does Anthropic block access from certain countries? Anthropic does restrict access in certain regions due to legal or regulatory requirements. If you are in a restricted region, using a VPN to a permitted region should allow access, but VPN usage policies vary by location — verify that VPN use is legal in your jurisdiction before proceeding.
Q: My network ping to claude.ai works but the app still fails. What does that mean? A successful ping only confirms DNS resolution and ICMP routing — it does not verify that HTTPS or WebSocket connections work. Claude requires WebSocket connections on port 443 for streaming. Some firewalls allow ICMP (ping) while blocking WebSocket upgrade requests on the same port. Test with curl or a WebSocket testing tool to verify the actual connection type.
Q: How do I know if the issue is on Anthropic's side versus my side? Check status.anthropic.com for any active incidents. If the status page shows "All Systems Operational" and your issue reproduces across multiple devices and networks (home, hotspot, office), then it may be account-specific — contact support. If it only happens on one network, it is a local network issue. If it just started happening for many users simultaneously, check social media (X/Twitter) for reports.
Q: Claude works but responses stream very slowly or stop mid-stream. Is that a network error? Slow streaming is a partial network issue — the connection is established but the throughput is insufficient to receive the streaming response in real time. This happens frequently on mobile networks, satellite connections, and congested corporate Wi-Fi. Switching to a wired connection or a faster network will resolve most slow-streaming issues. If it happens on fast networks too, it may be server-side load and will self-resolve.
Related Issues
- Claude message failed to send
- Claude stuck on verifying
- Browse more fixes in this category
- Browse all Claude guides
Additional FAQ
Q: How do I know if the problem is on my end or the platform's side? Check the platform's official status page first — most services maintain a public status page that shows current incidents and outages. If no incident is posted and the problem only affects your account (not reported widely on Reddit or Twitter), it is likely a local issue. Testing in incognito mode and on a different network also helps isolate whether the problem is browser-specific, network-specific, or account-specific.
Q: Why do hard refresh and regular refresh fix different problems? A regular refresh (F5) reloads the page using cached resources — it does not clear JavaScript bundles, service worker state, or session cookies. A hard refresh (Ctrl+Shift+R or Cmd+Shift+R) bypasses the cache and fetches all resources fresh from the server. Regular refresh fixes transient network hiccups; hard refresh fixes stale cached code. Neither clears cookies or session tokens — for that, you need to clear site data explicitly from browser settings.
Q: When should I contact support versus waiting it out? Contact support immediately if: you were charged but did not receive access, your account was suspended without explanation, or the problem affects billing or data. Wait and retry after 30–60 minutes if: a status page shows an ongoing incident, the error message says 'try again later', or the problem started very recently. For account-specific errors with no platform-wide incident, opening a support ticket is always the right move — document what you tried and include timestamps.
Related Articles
- Claude usage limit reached
- Claude rate limit fix
- Claude blank page white screen
- Claude can't log in fix
Additional FAQ
Q: How do I know if the problem is on my end or the platform's side? Check the platform's official status page first — most services maintain a public status page that shows current incidents and outages. If no incident is posted and the problem only affects your account (not reported widely on Reddit or Twitter), it is likely a local issue. Testing in incognito mode and on a different network also helps isolate whether the problem is browser-specific, network-specific, or account-specific.
Related Articles
- Claude usage limit reached
- Claude rate limit fix
- Claude blank page white screen
- Claude can't log in fix
Additional FAQ
Q: How do I know if the problem is on my end or the platform's side? Check the platform's official status page first — most services maintain a public status page that shows current incidents and outages. If no incident is posted and the problem only affects your account (not reported widely on Reddit or Twitter), it is likely a local issue. Testing in incognito mode and on a different network also helps isolate whether the problem is browser-specific, network-specific, or account-specific.