What to Do When Claude Says Your Region Isn't Supported?
Claude decides where you are by the exit IP's location — node labels don't count. Only a node that's really in a supported country, preferably native, with all three leaks clean, counts as passing. Once chosen, stick with it long-term — don't hop between popular and obscure regions; that's safer than switching nodes constantly.
The proxy is on, the node is abroad, yet Claude still says "region not supported" — the problem is usually not where you are, but where your IP looks like it is. Claude's regional limits look at the exit IP's location — not the address on your passport, and not the country you entered when registering the account. As long as your exit IP falls outside the list, you'll be blocked no matter where you actually are.
How Claude decides your region
Anthropic maintains an official list of supported regions, including the US, UK, EU countries, Japan, South Korea, Singapore, Australia, Canada, and others; mainland China, Hong Kong, Russia, and others are not on it. The list changes — go by the Supported Regions page on the official website, not by old lists circulating online.
There is a fixed way to check the list: go to Anthropic's official website and find the Supported Regions page — what it lists is the set of countries and regions where Claude works right now. Check it before you pick a node, and don't rely on memory — the list changes with policy, and a region that is on it today may not be on it tomorrow. Old lists circulating online are mostly someone else's screenshots or reposts; once the update date passes they are out of date, and picking a node from an old list means testing yourself against rules that have already changed.
The decision rests only on three layers of measurement, not labels: first, the exit IP's location — check the country of your actual exit IP, not the node's name; second, connectivity and latency — use the website check to look at claude.ai connectivity and latency, since detours or abnormally high latency mean the exit doesn't match the label; third, the three leaks — if WebRTC, DNS, or IPv6 leaks your real region, it gives you away. A "US node" in proxy software is just a label; risk systems only trust measured results.
Three reasons you're still blocked with a proxy on
The node's location isn't on the list. Hong Kong nodes are the most common case: close and fast, but Hong Kong isn't on the supported list. When choosing a node, check the list first, then speed — don't reverse the order.
Broadcast IP. The IP is registered in the US but actually broadcast from another country, so location decisions waver — sometimes it works, sometimes it doesn't. A native IP means the registration country matches the place of use, and its decisions are stable; seeWhat Is a Native IP?.
Leaks expose your real region. If WebRTC, DNS, or IPv6 hasn't gone through the proxy, your real region is sent out — no matter how correct the proxy exit is. For how to check the three leaks, seeCheck These Three Things Before Using Claude and What Is a DNS Leak?.
| Cause | Symptom | Fix |
|---|---|---|
| Node not on the list | Direct "region not supported" message | Switch to a node in a supported region; check the exit IP's location first |
| Broadcast IP | Works sometimes, changes on refresh | Stick to one native node long-term |
| Three leaks | Exit is right but still blocked | Check the WebRTC, DNS, and IPv6 leaks |
| System region mismatch | Website opens, app doesn't | Check the system region and store region settings one by one |
Missing any one of them can get you blocked
Three prerequisites for opening Claude
Missing any one of them can get you blocked.
Exit in a listed region. The exit IP's location is in an Anthropic-supported region — Hong Kong nodes don't count. Check the exit IP's location first, confirm it's on the supported list, then open Claude.
Native preferred. A native IP, where registration and use are in the same place, has stable decisions. Avoid broadcast IPs — an experience that works sometimes and fails other times is itself a sign that the decision is wavering.
No leaks. WebRTC, DNS, and IPv6 don't expose your real region. Once all three line up, open Claude — you'll avoid many pitfalls. The order to check: first the exit IP's location, then whether it's a native IP, and finally whether any of the three leaks expose your real region.
Purity matters too: the lower the risk score, the better, with no proxy flags and no dark history. By this site's five tiers, below 20 is pure, below 35 fairly pure, below 50 average, below 70 suspicious, and 70 or above high-risk; purity = 100 − risk score. The risk score is a heuristic estimate based on public information, not an official ban decision from any platform — different platforms apply different policies, so treat the result as a reference only. For how to check purity, seeWhat Is IP Purity?, and to check the sharing count, seeWhat Is the IP Sharing Count?. If your risk score runs high, see What to Do About a High IP Risk Score? How to Lower It.
How to choose a supported region: popular vs. obscure
Nodes in popular regions have many users and high sharing — over a hundred people on one exit, and if someone triggers risk controls, the whole range gets punished with them. For how many sharing users is too many, seeHow Many Sharing Users Is Too Many? When Should You Switch IPs?. Obscure supported regions with fewer users sharing have cleaner profiles, but before choosing, confirm two things: first, that Claude actually works in that region, going by the officially published supported range; second, that your payment method, time zone, and language can line up with that region — otherwise the region is right but the payment doesn't match, and verification gets triggered anyway.
Check the alignment item by item: is the issuing country and billing address of your payment card in that region, is the system time zone set to that region, and are the browser and Claude account languages the ones commonly used there? If any one of them doesn't match, risk systems see a self-contradictory profile: the IP says you are in country A, the card says country B, and the time zone points to country C — the region can be right and verification still gets triggered. For how to align timezone and language with the region, seeIP, Timezone, and Language: How to Keep Your Account Environment Consistent.
Once chosen, stick with it long-term — don't hop between popular and obscure regions; switching regions frequently is itself high-risk behavior in the eyes of risk systems.Why is switching nodes frequently more dangerous? Every region change looks like a location jump to risk systems: an account hopping between several countries in a short time looks like it is shared by multiple people, or stolen and passed on. Even if every node you switch to is clean, the jumping itself makes the profile look more unstable. If you really have to switch, switch once and then stay put for a long time — don't test back and forth over a few days. For the difference between residential and datacenter IPs, seeThe Difference Between Residential and Datacenter IPs; for how ChatGPT's and Claude's risk priorities differ, seeWhat Do ChatGPT and Midjourney Require of an IP?.
The right choice also differs by situation: for the web version only, the focus is the exit location and the three leaks; for the app, you also need to check the phone's system region and the app store account's region; for binding a payment method, region, payment method, time zone, and language all have to line up — missing any one can trigger verification. For what to prepare for verification, seeWhat to Do When Claude Asks for KYC: Triggers and How to Avoid Them.
Can your network open Claude right now? Don't try it on a hunch — check the exit region, IP consistency, and the three leaks free on ISPing.me first. Open it only when all 9 pass:Check now →.
Common symptoms and what to do
Direct "region not supported" message: the exit IP's location isn't on the list — switch to a node in a supported region and check the exit IP's location first. Works sometimes, changes on refresh: a broadcast IP or a node hopping between countries — stick to one native node long-term. Website opens but the app doesn't: besides the IP, the phone's system region and app store account region may matter — check the system region and store region settings one by one. Opens right after switching nodes, then gets blocked after a few days: first check whether the sharing count grew or neighbors dragged the IP down, then check whether any of the three leaks changed — don't switch nodes right away.
When fixing it, don't cycle through nodes trying them one by one: every node switch looks like a region jump to risk systems, and frequent switching only makes the profile more unstable. The right order is to pinpoint the cause first: run the Claude check and see whether the region, IP consistency, or any of the three leaks is off, then decide whether to switch nodes or fix the leak. For how to test whether your proxy is leaking your real IP, seeHow to Test Whether Your Proxy Is Leaking Your Real IP?.
FAQ
The node clearly says USA — why does Claude still say it's not supported?
Node labels don't count; risk systems only trust the measured location of the exit IP. Check the actual exit IP's country first, then check whether it's a broadcast IP and whether any of the three leaks expose your real region.
Hong Kong nodes are close and fast — can I use them?
No. Hong Kong isn't on Anthropic's supported list — being close and fast doesn't help. When choosing a node, check the list first, then speed — don't reverse the order.
The website opens but the app doesn't — is that an IP problem?
Not necessarily. The app can also depend on the phone's system region and the app store account's region. Check the IP's location and leaks first, then verify the system region and store region settings one by one.
Will switching to an obscure region definitely open it?
No. Obscure regions have fewer users sharing and a relatively cleaner profile, but first confirm Claude actually works in that region, and confirm your payment method, time zone, and language can line up with it — otherwise verification gets triggered anyway.
Notes
Anthropic's supported-region list changes — go by the Supported Regions page on the official website; the list in this article reflects the common situation at the time of writing, not the official real-time list. Risk scores and purity are heuristic estimates based on public information — not bank-grade risk scores and not official region decisions from any platform — so treat the results as a reference only. Regional limits involve account and payment policies — follow Anthropic's official website.
Check in one click whether your network can open Claude
Exit region, IP consistency, WebRTC, DNS, and IPv6 leaks, time zone and language — 9 items, one by one, all passing before you open it. Test first, use second — don't wait until you're blocked to start troubleshooting:
Check nowRelated reading:What Do ChatGPT and Midjourney Require of an IP?What Is a DNS Leak?What Is a Native IP?What Is IP Purity?Check These Three Things Before Using ClaudeWhy Does Claude Ban Accounts?Residential IP vs. Datacenter IP: What's the Difference