Claude Unsupported Region Explained: Causes and Compliant Options
When Claude says your region is unsupported, it means Anthropic has decided, based on where you are accessing from, that your country or region is outside the area where it offers service. This is a provider policy, not a network fault. Waiting a while or switching browsers will not make it go away. When you see the "Claude unsupported region" message, first check the official supported-countries list to see whether your location is on it. If it is on the list and you are still blocked, work through the checklist below to separate a geolocation misjudgment from a network problem or a service outage.
This article does not offer any way to bypass the region restriction. Region limits are written into the terms of service, and circumventing them may violate those terms and possibly local regulations. What follows explains how to read the message, how to confirm the cause, and which options are legitimately available where you are.
What does this message actually mean?
Anthropic maintains a list of supported countries and regions for Claude on the web, in the app, and through the API. When you visit or make a call, the server infers your location from the request origin and other signals, and requests from locations not on the list are rejected.
It typically shows up in one of three ways:
- Web or app: when you open claude.ai or sign in, the page says, in essence, that Claude is not available in your region.
- Sign-up: the country of your phone number or billing address is not supported, so you cannot complete verification or payment.
- API calls: the request returns a rejection such as HTTP 403, rather than a timeout or a 5xx.
The API response code is the easiest signal to read. A 403 means the request reached the server and was explicitly refused. Timeouts, connection resets, and 5xx errors look more like network or service problems. The two kinds of problem are handled completely differently.
Where do I check the official supported regions?
Go by Anthropic's official pages:
- Supported countries and regions: https://www.anthropic.com/supported-countries
- Terms of service and usage policies: https://www.anthropic.com/legal
- Official status page: https://status.anthropic.com
A few notes:
- The list changes. Reposts and old screenshots may be out of date, so rely on the official page as it reads today.
- Availability on the web, in the app, and via the API is not necessarily identical. Check the notes for the specific product.
- At the time of writing, mainland China is not on the official list. For readers in mainland China, seeing this message is expected behavior, not a malfunction.
To follow changes to Claude's official changelog and news pages, you can use cdnping's official site changes page. It records line-by-line additions and removals across 11 official pages, Claude's included, and offers an RSS feed.
I'm in a supported region. Why am I still blocked?
The common causes are in the table below.
| Situation | Symptom | How to confirm | Compliant fix |
|---|---|---|---|
| Company network exits abroad | Blocked at the office, fine at home | Compare the country of the exit IP on each network | Use a network in your actual location, or ask corporate IT about the egress setup |
| IP geolocation database is wrong | Newly allocated ranges and mobile networks are occasionally placed in another country | Check whether several geolocation databases disagree | Switch to another normal local network, or report it to Anthropic support |
| Dual-stack network with different IPv4/IPv6 exits | Works intermittently, results differ after a refresh | Check the IPv4 and IPv6 exits separately | Make the network configuration consistent so the two exits do not land in different countries |
| Account or payment details don't match the region | The page opens but sign-up or payment fails | Check the country of the phone number and billing address | Use your own real information, as the official requirements say |
| An outage mistaken for a region problem | Many users report errors at once, with 5xx or timeouts | Check the official status page and third-party probes | Wait for recovery; no settings need to change |
The first three share one trait: your real location is in a supported region, but the request's exit location or the geolocation result does not match it. The goal is to make the exit honestly reflect where you are, not to pretend to be somewhere else.
Dual-stack problems are subtle. For details, see IPv6 proxy not working: why IPv4 and IPv6 exits differ on dual-stack networks, and how to troubleshoot.
Five-step check: region restriction or something else?
Go in order. Each step has a clear criterion.
Step 1: Confirm your location is on the official list
Open https://www.anthropic.com/supported-countries and find the country or region where you actually are. If it is not listed, stop here and go straight to the "Compliant alternatives" section below.
Step 2: Confirm the service itself is healthy
Open cdnping's Is Claude down? and Anthropic API status. The former combines the official status page, API probes every 5 minutes, and user reports. The latter probes the official API entry point from Cloudflare's edge every 5 minutes and keeps 30 days of history.
For reference: in cdnping's edge probes on October 17, 2026 (the DEN node, a window of about 85 minutes and 242 probes), api.anthropic.com had a 24-hour success rate of 100%, a median latency of 73 ms, and a p95 of 84 ms. That figure only shows that the server entry point was reachable during that window. cdnping began collecting on 2026-10-17, so the history is very short and cannot support a long-term conclusion. It also says nothing about whether your region is allowed to access the service.
Another reference point: records from Anthropic's official status page, synced by cdnping, show 6 major incidents and 1 minor incident for Claude from September 17 to October 17, 2026. Errors during an outage are sometimes misread as region problems, so do not skip this step. For how to read incident severity on a status page, see How to read the OpenAI and Claude status pages. For a roundup of incidents in this period, see Has Claude been going down a lot lately?
Step 3: See where your exit IP is placed
Open cdnping's IP and environment check and look at three things:
- Location vote: the country each of the 11 geolocation databases assigns to your IP, and the combined confidence. If the databases disagree, your exit IP may be misclassified.
- Multi-exit detection: the page reads the Cloudflare trace information used by services such as Claude, so you can see the exit location actually used when reaching those sites.
- IPv4/IPv6: whether the two exits land in the same country.
If you are in a supported region but the location shown here is somewhere else, the problem is in your network exit. Return to the table in the previous section for the matching fix.
Step 4: Tell the error types apart
If you use the API or Claude Code, run curl to see the response status code (replace $ANTHROPIC_API_KEY with your own environment variable):
curl -s -o /dev/null -w "%{http_code} connect:%{time_connect}s total:%{time_total}s\n" \
https://api.anthropic.com/v1/messages \
-H "x-api-key: $ANTHROPIC_API_KEY" \
-H "anthropic-version: 2023-06-01" \
-H "content-type: application/json" \
-d '{}'
This request deliberately has no body. Normally it returns 400 (bad request), which shows that the network and authentication path are working. Interpret the result roughly like this:
| Response | Meaning |
|---|---|
| 400 | The path is healthy and the request body is invalid, which is expected |
| 401 | The API key is invalid or not set |
| 403 | The request was rejected, possibly because of region or account permissions; check the official list and your account status |
| 429 | Rate limited |
| 5xx | A server-side problem; go back to step 2 and check status |
| 000 or timeout | The network did not connect, which is a network-layer problem |
The last case has nothing to do with region restrictions. Work through it layer by layer with Claude Code connection timeouts and errors: a four-layer network checklist.
Step 5: If you still can't tell, ask the provider
If the first four steps rule everything out, and you are sure you are in a supported region and using your own real information, contact support through Anthropic's official help center. Include the time the message appeared, the product (web, app, or API), and the error text. Do not try registering new accounts over and over to "get lucky", as that may violate the terms.
For the full set of network self-check steps, see The developer network self-check checklist (2026 edition).
If my location isn't supported, what compliant options are there?
To be clear: if your location is outside Anthropic's supported area, disguising your location with technical means in order to use the service is circumventing the provider's region policy. This site does not provide such methods and does not recommend them. The directions below are for reference. Before choosing any of them, read the relevant service's terms and confirm that it complies with local regulations.
Use model services available where you are
Users in China can use model platforms that serve China directly, for example DeepSeek, Kimi (Moonshot AI), Qwen (via Alibaba Cloud Model Studio), Zhipu, and Doubao (via Volcengine Ark). You can check their availability on cdnping: Is DeepSeek down?, Is Kimi down?, Is Qwen down?. cdnping's online speed test measures, right in your browser, the first-connection and round-trip times from your network to these APIs.
Many coding tools support a custom endpoint URL, so switching to another model usually means changing a single setting. See Configuring custom API endpoints for Claude Code, Codex, and OpenCode.
Understand the limits of cloud-hosted and gateway access
Claude models are also offered through some cloud providers' platforms (in cdnping's model monitoring you can see the availability of the same model across different inference providers). But cloud platforms have their own regional availability, account requirements, and terms of service. Being offered there does not mean it can be used compliantly everywhere, so check each item. The use cases and cautions for the three access routes are compared in Official API, cloud-hosted, or aggregation gateway: how to choose among three access routes.
Aggregation gateways are another kind of option. Take AGI Plan as an example (AGI Plan is a commercial partner of cdnping): it is a multi-provider LLM aggregation gateway that bills in RMB, and it states plainly that it is not an officially authorized channel. Some models are marked "overseas only", and the exact availability is as listed at https://agiplan.dev/models. Before using any third-party channel, review its data policy and billing basis; Is a Claude API relay reliable? Main risks and how to check is a useful reference. For payment, invoices, and compliance considerations, see How developers in China pay for AI APIs.
FAQ
Will clearing the cache or switching browsers fix it? If the cause is region policy, no. The browser cache does not determine where you are judged to be.
It worked before and now suddenly says my region is unsupported. What happened? The official list may have changed, your network exit may have changed, or your IP may have been reclassified by a geolocation database. Check using steps 1 and 3 above.
Is an API 403 always a region problem? No. Account permissions, organization settings, and other things can also cause a 403. Rule out the key and account status first, then compare against the official list.
Will my account be affected after this message appears? Account rules are governed by Anthropic's terms of service. Using your real information and using the service in a supported region under the terms is the safest course.
