Availability by region

Can You Use Claude in Hong Kong? Why It Gets Blocked and What to Do

"I'm in Hong Kong. Can I actually use Claude?" The answer isn't a simple yes or no. This guide gives the direct answer first, then explains why so many people find that "the site loads but I can't use it", covers Macau and Codex, and ends with the shortest path you can check for yourself.

Keywords: can you use claude in hong kong, claude hong kong, claude not available in hong kong, claude pro hong kong, claude macau, codex hong kong

Last updated: · Maintained by Voguesly Residential IP

In short
  • Neither Hong Kong nor Macau is on Anthropic's supported list. The website usually loads, but the region check at sign-up, login or subscription does not pass.
  • Switching to a Hong Kong node doesn't help, because your exit is still in Hong Kong. Switching to a US datacenter IP gets the region right, but the IP type may then trigger risk checks. You need to look at both exit region and IP type.
  • Payment problems are usually a mismatch between card country, IP and billing address. Spend 30 seconds on a check first, see which item is failing, then adjust.

Can you use Claude in Hong Kong? The direct answer

As of 2026, Anthropic's official list of supported regions does not include Hong Kong. So:

In other words, "does it load" and "does the region check pass" are two separate things. Most people in Hong Kong get stuck on the second.

It loads ≠ it works: two separate thingsTwo columns compared. Whether the site loads is about connectivity; whether the region check passes depends on exit region, IP type, DNS, account and payment. On a local Hong Kong connection the website usually loads, but the region check doesn't pass because Hong Kong is not on the supported list. Typically pages load instantly and download speed is normal, but you're asked to verify as soon as you log in and the subscription payment won't go through. That doesn't mean there's no way: the key is an exit in an officially supported region, with the whole chain (IP type, DNS, payment method, billing address) kept consistent. Most people in Hong Kong get stuck on the region check. It loads ≠ it works: two separate things Does it load? Region check passes? What is checked Connectivity Exit region, IP type, DNS, account, payment On a local Hong Kong connection Usually loads Doesn't pass: Hong Kong is not on the supported list What you see Pages load instantly, download speed normal Asked to verify at login; payment won't go through That doesn't mean there's no way The key: an exit in a supported region, and the whole chain kept consistent: IP type, DNS, payment method, billing address Most people in Hong Kong get stuck on the second one: the region check.
"Does it load" and "does the region check pass" are two separate things

Why does it load but not work?

Anthropic doesn't only look at whether you can connect. It looks at your whole environment:

What is checkedTypical state on a local Hong Kong connection
Exit IP regionHong Kong: not on the supported list
Exit IP typeLocal broadband is usually residential, so this one is fine
DNS exitShould match the IP region; a mismatch adds risk
Account sign-up regionIf it contradicts your current IP region, verification is more likely
Payment detailsRisk checks tighten when card country or billing address doesn't match the IP

That's why you see something odd: the connection is fast and pages load instantly, but as soon as you log in you're asked to verify, or the subscription payment just won't go through. The connection isn't slow; the region item simply doesn't match.

What about Macau? And Codex?

Macau

Macau is essentially the same as Hong Kong: it is also not on the official supported list, and the symptoms are similar. The website loads, but sign-up, subscription or longer use runs into the region check. The approach is the same, so there's no need to research it separately.

Codex / OpenAI

Codex is an OpenAI product, and OpenAI's supported list is different from Anthropic's, so the Claude answer can't simply be applied to it. In practice, when Hong Kong users have trouble with Codex, it's more often not "region not supported" but failing to connect during sign-in authorization, or frequent disconnects while it runs. That is a network path problem, and you troubleshoot it in a completely different way. See Codex keeps saying Reconnecting / won't connect: how to fix it (Chinese).

How to find the problem fast: a three-step self-check

Step 1: See your current exit region and type. Open the Voguesly AI IP test. No login is needed, and it shows your current exit region, IP type (Residential/ISP or Datacenter/Proxy), DNS status and the result of a Claude handshake.

Step 2: Check from the command line.

curl -s https://ipinfo.io/json

Check whether country is a supported region, and whether org is a local ISP or a hosting provider. If country shows HK, the region is what's blocking you.

Step 3: Make sure your DNS exit is in the same region as your IP. A common hidden problem is that the IP has already moved to a supported region while DNS still resolves in Hong Kong. That contradiction triggers the check just the same.

Three steps: see which item is failingStep 1, see your current exit region and type: open the Voguesly AI IP test, no login needed; it shows your exit region, IP type, DNS status and the result of a Claude handshake. Step 2, check from the command line: run curl -s https://ipinfo.io/json; if country shows HK, the region is what's blocking you. Step 3, make sure your DNS exit is in the same region as your IP: if the IP has moved to a supported region while DNS still resolves in Hong Kong, that contradiction triggers the check just the same. Three steps: see which item is failing 1 See your exit region and type Open the Voguesly AI IP test (no login). It shows exit region, IP type, DNS status and the result of a Claude handshake 2 Check from the command line curl -s https://ipinfo.io/json If country shows HK, the region is what's blocking you 3 DNS exit in the same region as your IP IP already in a supported region, but DNS still resolves in Hong Kong: that contradiction triggers the check too
A three-step self-check

Can you pay for Claude Pro with a Hong Kong credit card?

Many Hong Kong users get stuck at payment: subscribing to Claude Pro with a Hong Kong credit card usually has a low success rate. Stripe's risk checks compare card country, current IP location and billing address together. A Hong Kong card with a Hong Kong IP may be blocked because the region isn't supported; a Hong Kong card with a US IP and a US billing address can be flagged as high risk because the three don't match.

The more reliable approach is to have card country, IP and billing address all match, in a supported region. For the full process, see the complete guide to Claude Pro sign-up, subscription and payment (Chinese; includes a section on paying from Hong Kong).

What the four common errors mean

"It doesn't work" in Hong Kong is really several different situations, and each is handled differently. Find yours first:

What you seeMost likely causeWhat to do first
Your region isn't supported yet / outside the service areaExit IP region is not on the supported listConfirm your current exit region; don't just switch to a faster connection
Repeated verification that comes back right after you pass itHigh risk score on the IP type, or DNS and IP in different regionsCheck whether the IP is residential or datacenter, then check the DNS exit
Features limited after login, conversations cut offAccount sign-up region contradicts your current exit regionKeep your exit region consistent with where the account was registered
Payment keeps failing on the subscription pageCard country, IP and billing address don't matchLine all three up; see the payment section above

The second one is the easiest to mistake for "an unstable connection". The test is simple: if pages load instantly and download speed is normal, but you're asked to verify as soon as you log in, it isn't a speed problem. To find out exactly which item doesn't match, see why Hong Kong users also run into Claude / ChatGPT verification and limits (Chinese), which breaks down each check in more detail.

Is a Hong Kong node enough?

A lot of people ask whether there's a Hong Kong node they can use for Claude. The question itself rests on a wrong assumption: a Hong Kong node solves connectivity, not the region check.

If you're in mainland China, a Hong Kong node does help you connect. But once you're connected, the exit region Claude sees is Hong Kong, and Hong Kong isn't on the supported list, so you're back to the question at the top of this guide. For mainland users, a Hong Kong node means "can connect, but may still be stopped by the region check"; for people already in Hong Kong, a Hong Kong node changes nothing.

What really matters is which region your exit is in, and what type of exit it is. When both are right, you're far less likely to be stopped by verification or at checkout.

Four kinds of exit: what Claude seesLocal Hong Kong broadband: the region is not on the supported list; the website loads, but at sign-up or subscription you may see a region-not-supported message. Hong Kong node: connects, but the exit is still Hong Kong; for mainland users it solves connectivity but may still be stopped by the region check, and for people already in Hong Kong it changes nothing. US datacenter IP: the region is right, but the IP type can carry a high risk score; the typical symptom is repeated verification. US residential IP: both region and type are right; keep DNS, account and payment consistent too, and you're far less likely to be stopped by verification or at checkout. Four kinds of exit: what Claude sees Local Hong Kong broadband Region not on the supported list Website loads; at sign-up or subscription you may see a region-not-supported message Hong Kong node Connects, but the exit is still Hong Kong Mainland users: can connect, but may still be stopped by the region check. Already in Hong Kong: it changes nothing. US datacenter IP Region right, IP type may carry high risk Typical symptom: repeated verification US residential IP Both region and type are right Keep DNS, account and payment consistent too, and you're far less likely to be stopped by verification or at checkout
Four kinds of exit, and what Claude sees for each

Common misconceptions

"Hong Kong is outside the mainland, so it must work." Being able to connect and being in a supported region are two different things. Hong Kong's internet is open, but the region check is a separate layer.

"Just switch to another Hong Kong node." Moving to a different Hong Kong exit still leaves you in Hong Kong, so the result of the check won't change.

"Any US node will do." If what you switch to is a datacenter exit, the region may be right, but the IP type can carry a high risk score. You need to look at both region and type.

"If payment fails, something is wrong with the card." In most cases it's caused by card country, IP and billing address not matching, and has nothing to do with the card itself.

What to do next

Spend 30 seconds on a self-check first and see exactly where you're stuck: the wrong region, the wrong IP type, or DNS in a different region. Deciding how to adjust after that works much better than switching nodes blindly.

Open the AI IP testSee US residential IP plans

Related guides