Claude Login Not Working? Check Status and Sign-In Method

Claude login not working? Start with two 30-second checks before anything else: confirm Anthropic's status page is green, then confirm you are using the same sign-in method your account was created with. Those two checks explain most failed sign-ins, and both are free to rule out.

Sign-in paths and incident checks verified 31 July 2026 against Anthropic's Claude status page.

Almost every "claude login not working" report falls into a small number of buckets, and they are not equally likely. Panicking and clearing everything — cookies, extensions, the app, your password — usually makes the problem harder to diagnose, not easier. This guide works through the causes in the order they actually occur, from cheapest check to most involved. What follows draws on our own use of it, including the rough edges you only notice in practice.

The 30-second triage: is it you or is it Anthropic?

Check two things first: whether the status page shows an active incident, and whether you are using the same sign-in method — email link, Google, or SSO — that created the account. Most failures stop here.

Before you touch a single setting, answer two questions.

Question one: is the service up? Open status.claude.com in any browser. It does not require you to be signed in, which is exactly why it is the right first stop. If there is an active incident affecting Claude.ai or authentication, then claude login not working is not your problem to fix — it is a wait. Our walkthrough on how to tell whether Claude is down covers how to read the status page properly, including why a green banner does not always mean every region is healthy.

Question two: which sign-in method does your account actually use? This is the single most common self-inflicted cause of claude login not working. Claude accounts can be created with an email sign-in link, with Google, or through a company SSO setup. If your account was originally created with Google and you now try the email path, you may be handed a login flow that does not match the credentials your account holds. Nothing looks broken — you just do not get in.

Think back honestly: when you first signed up, did you click a Google button? Did IT hand you a link? If the answer is Google or SSO, use that path every time, on every device.

We sign in to Claude constantly across the web app, the desktop app, and Claude Code while building this site, and the single habit that has spared us the most claude login not working headaches is boringly deciding on one method up front and never deviating from it. The times we did get tripped up, it was almost always the terminal-side OAuth handshake stalling on a fresh machine, not a real credential problem — re-running the sign-in in the same browser cleared it. Picking a lane and staying in it removes a whole category of self-inflicted failure.

Symptom table: match what you see to the likely cause

Match the symptom to the cause. A missing email points at spam filters, an invalid link at a mail scanner, an endless reload at cookies, a dead Google button at popup blockers, and access denied at your admin.

If your screen shows an actual error string rather than silence, that is useful — a specific message narrows things fast. The "error logging you in" message has its own dedicated fix path, and if you are seeing a 500-class failure during the OAuth handshake, our notes on the OAuth error status 500 will get you closer than generic advice.

Magic link problems: the most common cause of claude login not working

Five failure modes cover nearly all of them: the mail landed in spam, a corporate scanner pre-clicked and burned the single-use token, a newer request invalidated the old link, the link expired, or you opened it in a different browser.

The email sign-in link — the "magic link" — is convenient right up until it is not. Here is what goes wrong, roughly in order of frequency.

1. It landed in spam or promotions. Automated sign-in mail is exactly the shape of mail that filters distrust. Search your entire mailbox, not just the inbox, before assuming it was never sent.
2. A corporate mail scanner burned the token. This one is genuinely common on work email and almost nobody guesses it. Security gateways at many companies pre-click every link in inbound mail to check it for malware. Because a magic link is single-use, the scanner consumes it, and by the time you click, the link is spent. You get "invalid or expired" on a link that arrived 20 seconds ago.
3. You requested several links. Each new request typically invalidates the previous one. If you tapped "resend" three times, only the newest link is live — clicking the first email you see in the list will fail.
4. The link expired. Sign-in links are deliberately short-lived. Anthropic does not publish a fixed number you can rely on, so treat any link older than a few minutes as suspect and request a new one rather than counting the seconds.
5. You opened it in a different browser. Request the link in Chrome, click it from a mail app that opens Safari, and the session the link expects is not there. Open the link in the same browser you requested it from.

If a mail scanner is eating your links, the fix is not more retries. Switch to Google sign-in if your account supports it, use a personal address, or ask IT to allowlist Anthropic's sending domain. Retrying 10 times just burns 10 tokens.

Browser-side causes: cookies, extensions, and stale sessions

A silent loop back to the sign-in screen usually means cookies. Try a private window with extensions off; if that works, clear cookies for the Claude domain, allow third-party cookies, and disable your VPN for one attempt.

If the service is up and your method is right, suspect your browser next. The classic signature of browser-caused claude login not working is a loop: you sign in, the page flashes, and you are back at the login screen with no error at all.

Run this short checklist, in this order:

• Open an incognito/private window and try again. Private windows start with no cookies and usually no extensions, so this one step tells you whether the problem is your browser profile. If incognito works, you have your answer.
• Disable privacy extensions and ad blockers for the domain. Aggressive content blockers sometimes break the redirect chain that authentication depends on.
• Allow third-party cookies for the sign-in flow, at least temporarily. Strict cookie blocking is a frequent cause of sign-in loops.
• Clear cookies for the Claude domain specifically — not your whole browser history. A stale session from before a password change can outrank the new one.
• Turn off VPNs or proxies for one attempt. An exit node in an unexpected region can trip checks.

That last point matters more than people expect. If your traffic exits somewhere Claude is not offered, sign-in can fail in ways that look like a bug rather than a geography problem.

The model you are on has nothing to do with sign-in, by the way — Claude Opus 5 is currently the flagship, but authentication happens long before any model is chosen, so switching models never fixes a login.

Account-side causes: the ones you cannot fix from the browser

Some causes live in the account, not the browser: signing up under a different address, a half-verified signup, an SSO or Team seat your admin revoked, a pending identity check, or a suspended account.

Some cases of claude login not working are not technical at all — they are facts about the account itself, such as which address it lives on or who controls the seat. Work through these if the first three sections came up clean.

A different email than you think. People sign up on a personal address, then years later try the work one. There is no error that says "this address has no account" in a way most users notice — you just never get in. Try every address you plausibly used.

An unverified account. If signup was interrupted, the account may exist in a half-created state.

An SSO, Team, or Enterprise seat. On a managed workspace, your admin controls access. If your seat was removed or your SSO group changed, claude login not working is an administrative fact, not a bug — and only your admin can undo it. This is worth checking before you file a support ticket, because support will route you back to your admin anyway.

Identity or verification checks. If you are being asked to prove who you are mid-flow, that is a deliberate step rather than a failure — complete it and the sign-in continues.

A suspended or banned account. Rare, but it happens, and it presents as a hard stop rather than a loop.

Why does the app fail when the web works?

The app is holding a cached session token. Sign out inside the app, quit it completely rather than closing the window, then sign in again; a reinstall clears the stored token if that still fails.

If the web works but the app does not, the app is holding a cached session it will not let go of. The pattern is that you sign in, the app briefly shows the interface, then bounces you back out.

For mobile, sign out fully, force-quit, and sign in again; if that fails, reinstalling clears the stored token. Our Claude mobile app guide covers the platform quirks. On desktop, the same logic applies — sign out, quit completely rather than closing the window, relaunch. If the desktop app refuses but a browser succeeds, use the browser while you sort out the app; you lose nothing but convenience.

Worth separating: if you can sign in but a specific conversation will not open, that is a different problem entirely and is covered in why Claude can't open this chat. And if things load but behave strangely across the board, our general Claude not working guide is the broader net.

When to contact support, and what to include

Open a ticket only after ruling out status, method, magic link, browser, and account. Include the exact address, sign-in method, verbatim error text, a timestamped attempt, your browser and OS, and everything you already tried.

If you have ruled out status, method, magic link, browser, and account, stop guessing and open a ticket at support.claude.com. A vague ticket gets a slow, generic reply. A precise one gets fixed.

Include all 6 of these:

• The exact email address you are trying to sign in with — spelled out, not "my work email".
• The sign-in method you are using (email link, Google, or SSO).
• The exact error text, copied verbatim, or "no error, it just reloads" if that is the truth.
• A timestamp with your time zone for your most recent attempt.
• Browser and OS, plus whether incognito with extensions off also failed.
• What you already tried, so nobody asks you to try it again.

Do not promise yourself a response window — nobody publishes a reliable one, and expecting a number just makes the wait worse.

The short version

Work down the list in order — status, method, magic link, browser, account, app — instead of changing everything at once. Resetting five variables simultaneously is what turns a three-minute fix into an afternoon.

Work down, not sideways. Status page, then sign-in method, then magic link, then browser, then account, then app — that order costs you a few minutes and resolves the large majority of cases. The instinct to reset everything at once is the thing that turns a 3-minute fix into an afternoon, because once you have changed 5 variables you can no longer tell which one mattered.

And be honest at step two. More claude login not working reports come down to the wrong sign-in button than to anything Anthropic did.