TL;DR

Four Claude errors get lumped together and they may have different causes. Something went wrong is a generic failure that can come from either end: retry a few times, then check status.claude.com. An unknown network error suggests a problem with your connection, so rule out a VPN and extensions. Error 529 is described by Anthropic as temporary API overload, so wait and retry with increasing gaps. For a 503 or capacity message, check the status page, and if it is green, wait and retry. Anthropic does not publish a list of these exact messages.

Short answer

Four different errors get lumped together here and they may have different causes. “Something went wrong” is a generic failure that can come from either end, so retry a few times and then check the status page. The authentication service error is a fifth message that looks like this one and is not. “An unknown network error” suggests a problem with the connection between you and Claude, and a VPN or browser extension is worth ruling out first. Error 529 means the API is overloaded, so wait rather than retrying hard. Before doing anything else, check status.claude.com, because if it is an outage nothing you do locally will help.

Claude fails to respond and you get an error. Which error you got matters, because the causes may not be related to each other and the fixes may differ.

The messages are also unhelpfully vague, and several of them read alike from the browser.

Thirty seconds at status.claude.com first. If something is down there, stop reading and wait, because none of this is about your setup.

Which network error is it?

Anthropic’s help centre does not publish an official list of these exact messages, so the wording below is an approximation of how the errors read. If yours differs slightly, match on the meaning.

“Something went wrong. Try sending your message again.”

A generic failure that can come from either end of the connection. Retry the message. If it persists past a few attempts, check the status page, then try a new chat.

“An unknown network error has occurred”

The wording suggests a problem with the connection between you and Claude, though Anthropic does not document it. Rule out your VPN first, then extensions, then your network. Fixes 2 to 4.

Error 529, or a message about being overloaded

Anthropic’s API documentation defines 529 as the API being temporarily overloaded. Waiting is the fix. Anthropic’s documented approach is to retry with increasing gaps, not repeatedly.

Error 503, or a service unavailable or capacity message

Anthropic does not document a 503 message for claude.ai, so treat that label as a general description. Its troubleshooting guide does document a message about unexpected capacity constraints, which it says is not an outage and does not appear on the status page. Check status.claude.com. If it is green, wait and retry.

ErrorWhat it suggestsWhat to do
Something went wrong. Try sending your message again.A generic failure, from either endRetry; if it persists, check the status page, then try a new chat
An unknown network error has occurredA problem with the connection between you and ClaudeTurn off the VPN, then rule out extensions, then check your network
Error 529, or overloadedAPI temporarily overloadedWait, then retry with increasing gaps
Error 503, or a service unavailable or capacity messageService unavailable, or a capacity limitCheck status.claude.com; if green, wait and retry. Capacity messages do not appear there

Fix 1: check the status page first

status.claude.com shows whether Claude is actually up. It is the fastest way to find out whether you are troubleshooting your own setup for no reason.

Worth knowing that the web app, the API and Claude Code can be affected separately, so a green light on one does not clear the others. Check the status of claude.ai, the API and Claude Code separately, and read the incident title for what is affected.

Fix 2: turn off your VPN

If you are on a VPN and getting network errors, turn it off and retry. Anthropic’s error troubleshooting guide lists turning off a VPN as a first step for a generic login error, the nearest documented case.

Claude’s responses arrive over a connection that stays open while it writes, which an unstable tunnel may interrupt. Anthropic does not document this for network errors. If you need the VPN on, try a different server, ideally one geographically closer to you.

Fix 3: rule out extensions

Open claude.ai in a private window and send one message. A private window lets you test without your extensions, unless you have allowed them to run there.

If it works in private and fails normally, an extension may be the cause, and the same guide lists disabling active extensions as a first step for that generic login error. Re-enable them one at a time to find which.

Fix 4: clear the site data for claude.ai

The same guide suggests clearing your cache and cookies for a login error, so it is the last local step to try before you conclude the problem is not on your side. Limit it to claude.ai, because wiping every site’s data costs you sign-ins elsewhere for no gain.

In Chrome and similar browsers, the route is:

  1. Open claude.ai
  2. Click the icon to the left of the address bar, the padlock or the sliders
  3. Choose Cookies and site data, then Manage on-device site data
  4. Delete everything listed
  5. Hard refresh with Ctrl + Shift + R, or Cmd + Shift + R on Mac

You will be signed out of claude.ai. Your conversations live on Anthropic’s servers, not in your browser, so sign in again and resend the message that failed. If the same error comes back, the browser was not the cause. Upload failures are a related case, covered in the file upload guide.

Error 529 and being overloaded

529 means the API is temporarily overloaded. Anthropic’s API error documentation says it can occur when the API experiences high traffic across all users, so it is not about your account, your plan or your request.

Waiting is the sensible response. The official SDKs retry transient failures with exponential backoff, and the same approach works by hand: wait, and space out retries with increasing gaps rather than firing them one after another.

It is described as temporary overload, so if the work can wait, try again later.

When a long conversation is the trigger

If errors started appearing in one particular chat and everything else works, it is worth treating that chat as the variable rather than your connection.

Anthropic does not document why one chat would fail while others work. A very long chat with attachments may be heavier, so one thing to try is starting a new chat and carrying the context over: ask Claude to summarise where things got to, then paste that as your first message. If the new chat works, you have your workaround.

Work and school networks

If Claude fails at work and works at home, your work network is a suspect.

Test by tethering to your phone for one message. If that works, ask whoever runs your network to allow claude.ai and anthropic.com. A proxy that buffers or inspects traffic could interrupt a streamed response while ordinary pages load. Anthropic does not document this, so treat it as a possibility rather than a diagnosis.

Why the messages are so vague

Anthropic does not document why these messages are generic. One plausible reading is that a dropped connection, a timeout and an overloaded server all look like the same event from the browser: the response stopped.

That would explain why a generic message can cover faults at either end of the connection, which is why working out which one you have matters. Attachment problems are covered separately in the file upload guide. Sign-in failures are a different fault, and the Lead Source blog covers the authentication service error on its own page.

Written by the team at Lead Source, who spend their days on lead source attribution rather than error codes, but keep a status page bookmarked like everyone else.