How to interpret it
Compare IPv4 and IPv6 exits with Anthropic’s published country list. A public resource loading does not prove sign-in or full chat access, and IP risk signals cannot predict an account ban.
Claude IP Check: Region List & Exit Identity
Compare your exit against Anthropic's published country list, then review region, ASN, residential or data-center signals, and proxy risk.
Locate region
- Parse IP
- Locate region
- Match ASN
- Check proxy / VPN / Tor
- Check risk lists
- Summarize AI access
Claude access diagnosis
Live checkChecking
Checking
- Public endpoint reachability
- Checking
- Measured from this browser
- Access conditions reference
- Checking
- Reference based on public information
- Exit network type
- Checking
- Current exit profile
- Risk note
- Checking
- Based on exit network signals
Current exit IPCheckingCollecting network profile…
AI Availability
Live check on this networkChecking
Checking
Checking
Checking
Checking
How to read this check
How to Read a Claude AI IP Check
This page places Claude public-resource connectivity alongside exit region, ASN, and network type to help investigate network-side issues.
Frequently asked questions
How do I tell whether this exit suits Claude?
This page does not give a single suitability score. It lists the signals you can verify separately: exit region, ASN, residential or data-center type, proxy and Tor flags, and whether IPv4 and IPv6 agree. Those signals explain access differences; they do not determine whether an account is restricted.
Which countries does Claude support?
Anthropic publishes the supported countries and regions on its official support page. This page shows your current exit region next to that public list so you can compare them. The list changes, so treat Anthropic's page as authoritative.
Claude will not open or keeps loading - what do I check first?
Separate three stages first: the public page, the sign-in redirect, and the signed-in session. Only when the same page changes with the network are exit region and proxy path the likely cause.
Do mismatched IPv4 and IPv6 exits affect Claude?
They can. A dual-stack network may reach Claude through different exits, and if the two paths differ in region or ASN you can see the problem appear and disappear when the network changes. This page shows both address families separately.
Official sources and evidence limits
These are the primary official sources referenced on this page. Results describe the current network environment, not account, subscription, or platform risk outcomes.
- Claude StatusAnthropic
- Claude SupportAnthropic
- Claude supported countriesAnthropic
Claude Guides
Claude access troubleshooting
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: Cookies and Redirects
When Claude repeatedly asks for verification or signs out after sign-in, check cookies, redirects, extensions, and device time before inspecting exits.
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 guide