Compare your exit against Anthropic's published country list, then review region, ASN, residential or data-center attributes, proxy, VPN, Tor risk, and IPv4/IPv6 consistency.
Checking
A Claude AI IP check combines service connectivity with the current IP region, ASN, network type, and proxy risk to help identify network-related access problems.
Connectivity shows whether this network can load Claude's public check resource. It helps diagnose the basic path, but it does not guarantee account login, subscription eligibility, or the complete conversation service.
A dual-stack network may reach Claude through different IPv4 and IPv6 exits. Review each result separately when their regions, ASNs, or network types differ.
Data-center, proxy, and risk-source signals can explain some access differences, but they cannot predict an account ban. If the network looks normal, continue with account eligibility, browser messages, and Claude's official service status.
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 messageWhen 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 troubleshootingWhen 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 troubleshootingWhen 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