Identify where the region message appears
| Observed symptom | Confirm first | Do not infer directly |
|---|---|---|
| The page explicitly names a region or country | Full message, the page where it appears, and current official availability | A city-level database result does not prove the service made a mistake |
| The message follows a sign-in redirect | Sign-in method, browser session, exit, and address family | Not every request is known to use one exit |
| It occurs on only one network | That network's DNS, proxy rules, IPv4, and IPv6 | One risk label is not enough to identify the cause |
| It persists on several networks | Official status, account-page guidance, and support | A network check cannot decide eligibility or account status |
Review Anthropic's current support guidance first
Preserve the exact message
Record whether the message appears on the public page, during registration, sign-in, or an authenticated session. Similar unavailable messages can belong to different parts of the flow.
Use Anthropic's current guidance
Refer to Anthropic's current supported-country or region guidance. Availability can change, so older lists and third-party screenshots are not a substitute for the current official page.
Check IPv4 and IPv6 separately
Review the region, ASN, network type, and time on both exit cards. A dual-stack network can send different requests over different paths.
Confirm Claude's routing exit
Use AI Routing Exit Check to see the public exit returned through the Claude endpoint, then compare it with the current network exit. It validates routing behavior, not account eligibility.
Change one network variable
Use one known-stable network for a comparison. Do not change the node, DNS, browser, and sign-in method together, because the result cannot be attributed.
Inspect exits only after a stable network difference
Inspect proxy routing only when the same account and browser step change consistently with the network. The public page, sign-in redirect, and resources can use different hosts, so one matching rule does not establish the path for the full flow; an IPv4-only proxy can also leave IPv6 on another path.
Keep the current IP result, Claude routing exit, and failure time together. A stable difference points to rule coverage or network configuration; it is not a claim that any IP type guarantees access. Eligibility remains defined by official policy and the page shown to the user.
Choose the next step by reproduction scope
- Record the Claude message, time, browser, and sign-in step
- Record the original network's IPv4, IPv6, ASN, region, and Claude routing exit
- Repeat the same flow on one known-stable network without changing browser settings
- If it persists, review official status and the account-page message; if it is limited to the original network, inspect its DNS, proxy, and address-family rules
- Give the reproducible record to an administrator or Anthropic support instead of rotating exits at random
The evidence boundary of a network check
The Claude and routing-exit checks show the path observed for this network and public endpoint. They can expose missing proxy coverage, different IPv4/IPv6 exits, or DNS and routing differences. They cannot read account location, payment, organization permissions, or Anthropic's internal decision.
Sources and evidence limits
Sources below support the stated technical or policy boundary. Diagnostic comparisons in this guide remain observations, not account verdicts.
- Supported CountriesAnthropic · Official guidance
- Claude StatusAnthropic · Official guidance
- Claude Help CenterAnthropic · Official guidance