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 Loading: Network and Region Checks
When Claude will not open, the sign-in page stalls, or a chat keeps loading, isolate the failure across Anthropic status, browser state, public exits, and IPv4/IPv6 paths.
Read guideClaude region-unavailable messageClaude Region Unavailable: Support and Network Exit Checks
When Claude reports that your region is unavailable, first identify whether it occurs on a public, sign-in, or signed-in page and review Anthropic's current support guidance. Check IPv4, IPv6, and routing exits only when the difference follows the network.
Read guideClaude verification-loop troubleshootingClaude Verification Loop: Cookies and Redirects
When Claude repeatedly asks for verification, returns to the same page, or signs out after sign-in, first check cookies, redirects, extensions, and device time. Inspect exits and proxy paths only when the result changes with the network.
Read guideClaude dual-stack exit troubleshootingClaude IPv4 and IPv6 Exit Mismatch: Causes and Fixes
When the Claude check shows different IPv4 and IPv6 regions, ASNs, or network types, record each dual-stack path, proxy coverage, and WebRTC observation separately before using one-variable tests to locate the configuration difference.
Read guide