Couldn't connect to Claude? Fix it or confirm an outage

"We couldn't connect to Claude. Please check your network connection and try again." If that line, or "Temporarily unable to authenticate. Please retry.", just stopped you, the first job is to find out whose problem it is. Open status.claude.com. If claude.ai shows an incident, wait it out. If everything is green, the cause is usually on your side: a VPN, a browser extension, an outdated app or a stale sign-in.

This guide gives you that order of checks, built from Anthropic's own help center (checked October 22, 2026) and from public bug reports where Anthropic documents nothing. claude-for is an independent guide, not affiliated with Anthropic.

TL;DR: Check status.claude.com. If there is an incident, stay signed in and retry later. If there is none, turn off your VPN, disable browser extensions, clear cookies for claude.ai, update the desktop app, then sign out and back in.

The exact messages, and where they show up

These are the wordings people report, verbatim:

• "We couldn't connect to Claude. Please check your network connection and try again." The full sentence, seen in the apps and quoted on Threads in May 2026.
• "Couldn't connect to Claude" as the heading in Claude Desktop, with a second line underneath. Reported second lines include "check your network connection" (GitHub #53869), "Unknown error" (#73291) and "Your network redirected this request to www.anthropic.com. Contact your IT administrator." (#78376).
• "Temporarily unable to authenticate. Please retry." Note the period and capital P. It was the most common error during the September 29, 2026 outage, per Punto Informatico, and showed as a banner in Cowork (#98271).

Why you see it

The connection message means the app could not reach Anthropic's servers, or got an answer it did not expect. The second line is your best clue. "Unknown error" and "Your network redirected this request" in the reports above both came from corporate networks: a proxy that intercepts traffic, or a firewall that blocks the connection the app tries first.

The authentication message points the other way. In the reports we found, it appeared during a server-side incident, not because of anything the user did. According to Punto Informatico, the status page that day listed failed requests, errors loading conversations and prompts to log in again across claude.ai, Claude Code and Cowork. Resetting your password does nothing for that.

If you just want to know whether Claude is down for everyone, the status page is the answer, and the rest of this guide is for when it says all systems are operational.

The Claude moves worth stealing, by email

Workflows tested on real jobs, sent only when they are worth it. Free.

Subscribe

How to fix it

Work down this list in order and stop when the error goes away. Each step is cheap, and none of them deletes your chats.

The browser steps come from Anthropic's Troubleshoot Claude error messages article, written for the login error "There was an error logging you in". The status page advice is from Log in to your Claude account. The update path is from Anthropic's desktop extension allowlist article, and the Linux note from Install Claude Desktop.

A quick test to split network from app

Open claude.ai in a browser on the same machine. If the browser works and the desktop app still says "Couldn't connect to Claude", your network is fine and the app or its proxy handling is at fault. If neither works, switch to a phone hotspot for one minute. Working on the hotspot means your office or home network is blocking Claude.

If you are on a work network

Several GitHub reports describe Claude Desktop failing behind corporate proxies while the browser worked fine. One reporter found no client-side workaround at all. If that is you, send your IT team the exact second line of the error. Anthropic's Claude Code network configuration page is the closest official document for them, though it covers Claude Code rather than the chat app.

If you are on Linux

One user in GitHub #78376 fixed a persistent "Couldn't connect to Claude" by moving the ~/.config/Claude folder aside and relaunching. That is a community workaround, not Anthropic advice, and it resets local app settings. Rename the folder rather than deleting it, so you can copy anything back.

How to stop it happening again

• Subscribe to the status page. status.claude.com has a Subscribe to Updates button with email, SMS, Slack and RSS options, so you hear about incidents before you go hunting.
• Let the desktop app update. Use Check for updates when the app offers it. Two of the reports above began right after an update, so note your version number before you file a bug.
• Add claude.ai to your ad blocker's allowed sites if disabling extensions fixed it, instead of leaving everything switched off.
• Keep the browser as a fallback. When the app fails, claude.ai in a browser often still works, and your chats are the same in both.

The honest limits

Anthropic has no help article for either of these exact messages. The steps above come from its documentation for the nearest login error, and the causes come from bug reports, not from Anthropic. We have not reproduced the errors ourselves.

The status page can also lag. In #98271, the authentication banner appeared while status.claude.com still read "All Systems Operational". A green page does not prove the problem is yours. If nothing works after an hour, contact support: click your name in the lower left, then Get help, per How to get support. There is no phone line.

Questions people ask

Why does Claude say "Temporarily unable to authenticate"?

In every public report we found, it appeared during a server-side incident, such as the outage of September 29, 2026. Your password is fine. Check status.claude.com, stay signed in and retry in a few minutes rather than resetting anything.

Does a VPN stop Claude from connecting?

It can. Anthropic's own troubleshooting list for login errors starts with "Ensure you're not using a VPN when accessing Claude." Disconnect it completely and reload. Claude is also only offered in supported regions, so keep that in mind when you travel.

Is "Couldn't connect to Claude" the same as hitting my usage limit?

No. A usage limit shows its own message with a reset time, such as "5-hour limit reached". Our guide to Claude's usage limits explains those. The connection error means the app never reached Claude at all.

Why does Claude work in my browser but not in the desktop app?

The app connects differently from the browser, and the GitHub reports show it failing behind proxies the browser handles fine. Update the app, sign out and in, and if you are on a work network, ask IT. Using Claude Code in the desktop app has its own sign-in errors.

If you want a short note when Anthropic changes something that breaks your setup, the newsletter sends one only when it matters.