Claude Troubleshooting Guides
Keep the exact page message, then separate official availability boundaries, browser state, and network differences without attempting to bypass service controls.
Common Claude issues
Each guide starts from a reproducible symptom and explains the boundary of network evidence.
Claude Not Working: Network and Region Checks
Claude not working? Isolate the failure across Anthropic status, browser state, public exits, and IPv4/IPv6 paths before blaming the exit IP.
Read guideClaude region-unavailable messageClaude Region Unavailable: Network Exit Checks
When Claude reports your region is unavailable, identify whether it happens on a public, sign-in, or signed-in page, and review Anthropic's guidance.
Read guideClaude verification-loop troubleshootingClaude Verification Loop: Captcha & IP Risk
Troubleshoot Claude verification loops with official status, exact errors, cookies, scripts, extensions, and controlled network comparisons.
Read guideClaude identity verificationClaude Identity Verification Check
Separate Claude challenges, sign-in checks, and Persona identity verification. Follow official instructions and compare browser sessions.
Read guideClaude dual-stack exit troubleshootingClaude IPv4/IPv6 Exit Mismatch: Causes
When the Claude check shows different IPv4 and IPv6 regions, ASNs, or network types, record each dual-stack path separately before locating the difference.
Read guideClaude account and exit checksClaude Account or Exit Block? How to Tell
Separate a Claude account restriction, a blocked exit, and a service incident before treating a failure as an account ban.
Read guide