Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.
Where Are Popular AI Tools Available? Supported Countries
Olivia Park
April 6, 2026· Updated October 4, 2026· 10 min read
Where are popular AI tools available? On 4 October 2026, OpenAI, Anthropic and Google all listed the United States, the United Kingdom, Japan and Taiwan, and none of them listed Russia. Mainland China and Hong Kong were missing from the OpenAI and Claude lists, while Google's Gemini web app listed Hong Kong and allowed mainland China only for Workspace accounts.［2］［4］［7］
We found no comparable country list for Perplexity, Midjourney, Suno or Runway, so the map below links each provider's own page and a dedicated guide per tool. One provider can set different rules for its web app, API, mobile app, account type, plan or feature rollout. A VPN changes only the network path and exit IP, not account country, payment, age, eligibility or platform rules.
Key Takeaways
- OpenAI, Claude and Gemini all list the US, UK, Japan and Taiwan; none lists Russia.
- Of the three, only Gemini lists Hong Kong, and it allows mainland China for Workspace accounts only.
- Availability can differ by web, API, mobile app, account, plan, and feature.
- A VPN can test only a permitted network-layer problem; account and payment rules stay separate.
Where are popular AI tools available? A source-indexed map
Google renamed NotebookLM to Gemini Notebook in July 2026; the map keeps both names so readers can match the current product with older support pages.［6］
| Tool | Official region source | What the source says (4 October 2026) | Tool guide |
|---|---|---|---|
| ChatGPT | OpenAI supported countries and ChatGPT list | Country list published; mainland China, Hong Kong and Russia absent | ChatGPT checks |
| Claude | Anthropic supported countries | One list for Claude.ai and the API; mainland China, Hong Kong and Russia absent | Claude checks |
| Gemini | Web, mobile and API lists | Web app in 230+ countries and territories, Hong Kong included; mainland China Workspace only; mobile app in 150+ countries; the API list omits Hong Kong, mainland China and Russia | Gemini checks |
| Gemini Notebook (formerly NotebookLM) | Gemini Notebook FAQ | Follows the Gemini app region list; age verified in the Google Account | Gemini Notebook checks |
| GitHub Copilot | GitHub trade controls | No country list; Copilot may not be sold or exported to embargoed destinations | AI coding tool checks |
| Grok | About Grok and xAI Grok docs | Web, iOS and Android apps described; no country list found | Grok checks |
| Perplexity | Perplexity Help Center | No country list found; plan features differ | Perplexity checks |
| Midjourney | Midjourney documentation | No country list found; web and Discord access | Midjourney checks |
| Suno | Suno Terms of Service | No country list; sanctioned users barred, and the app or paid plans are not promised in every location | Suno checks |
| Runway | Runway Help Center | No country list found | Runway checks |
Each row summarizes the provider's own page as read on 4 October 2026.［1］［2］［3］［5］［8］［9］［10］［11］［12］ The table tells you where to recheck; it does not mark a country as permanently supported or blocked, and a blank result is not proof of unavailability.
Which AI tools list Hong Kong, mainland China and Russia?
The three providers with full country lists differ most on these regions. This snapshot compares their published lists, not a personal test.［2］［4］［7］
| Region | OpenAI list | Anthropic (Claude) | Gemini web app | What to check next |
|---|---|---|---|---|
| United States, United Kingdom, Japan, Taiwan | Listed | Listed | Listed | Account, plan and feature rollout |
| Hong Kong | Not listed | Not listed | Listed | Mobile store, billing and the Gemini API list |
| Mainland China | Not listed | Not listed | Workspace accounts only | Local law and provider terms |
| Russia | Not listed | Not listed | Not listed | Provider terms and payment rules |
OpenAI warns that using its services outside the listed countries and territories may get an account blocked or suspended, so a missing region is an account risk, not just a connection fault.［7］ Sign-in errors and app-store details for each tool stay in the tool guides linked in the map above.
A network test is diagnostic only. It cannot establish eligibility, change billing country, or bypass a provider restriction. For network-layer troubleshooting, see ChatGPT access checks and the AI-use guide; do not turn this map into a VPN guarantee.
Keep the map maintainable
- Save the official URL, product surface, account context, and access date.
- Separate “provider says supported” from “my request reached the service”.
- Recheck fast-changing rows before publication or a consequential decision.
- Remove a claim when the primary source no longer supports it.
What should each availability row record?
A useful row is a small evidence record, not a green or red country label. Keep the product name, the exact surface being checked, the account or plan assumptions, the provider wording, the source URL, and the date of the check together. If any of those fields is missing, mark the row for recheck instead of filling the gap with a guess.
| Field | Record | Why it matters |
|---|---|---|
| Product surface | Web app, API, mobile app, workspace, model, or feature | The provider may publish separate rules for each surface. |
| Identity and plan | Personal or organization account, subscription, age or billing prerequisite | A supported country does not make every account or plan eligible. |
| Source wording | Quote or close paraphrase with the scope preserved | “Available” may mean only sign-up, not every feature. |
| Evidence date | The day the source and, where permitted, the test were checked | Availability and rollout facts can change without notice. |
| Result status | Source-confirmed, recheck, not stated, or network symptom | A blank source is not the same as a provider denial. |
| Next action | Official help page, account support, or a permitted network test | Readers need a safe next step, not only a label. |
Do not mix a provider's supported-country list with a personal test result. The list answers what the provider says about a defined product surface; a test answers what happened for one account, network, device, and time. Both are useful, but they are different kinds of evidence.
A repeatable refresh workflow
- Define the claim. Write “web sign-in for a personal account” or “API access for an organization plan,” not simply “the tool works in this country.”
- Open the first-party source. Prefer the provider's supported-region page, product help center, terms, or account documentation. Do not replace a missing official answer with a search snippet.
- Preserve the boundary. Record whether the page covers sign-up, login, payment, a model, an app store, an API, or a feature rollout. Keep exclusions and footnotes.
- Record the date and uncertainty. Use “not stated” when the provider does not answer the exact question. Do not turn an old cached page into a permanent status.
- Check the account separately. If the provider lists prerequisites, verify them through the account or support flow. Do not change billing country, age, identity, or organization settings to make a test look successful.
- Use a network test only when allowed. Keep the device, account, surface, and task fixed; test one permitted route and record errors. A route result cannot override eligibility or platform policy.
- Publish the smallest supported claim. If the source confirms web access but says nothing about mobile or API, publish only the web claim and link the other surfaces to recheck.
- Archive the change. When a source changes, record the old wording, new wording, date, and affected rows so a reader can see why the map moved.
AethoVPN may be relevant when an AI tool's network route is the obstacle, but the availability map still has to be checked against each provider's current supported-region and account policies. For the one permitted route test in step 6 of the refresh workflow, AethoVPN can keep that connection encrypted on shared Wi-Fi; a route result does not change a row's source status, and each provider's terms and local law still apply. You can start its 3-day free trial just for that check.
How should you read common outcomes?
The provider says supported, but the page still fails
Check the exact surface, account, plan, age, billing and workspace conditions first. Then check the local network, DNS, browser session and service status. A failure in one path is not evidence that the provider's list is wrong, and a successful retry is not evidence that every account is eligible.
The web app works, but the app or API does not
Keep separate rows. Mobile distribution, API onboarding, model availability and workspace policies can have different prerequisites. Link to the platform-specific source rather than copying the web result into every column.
The source lists a country but not a feature
Use “country stated; feature not stated” and send the reader to the feature documentation or support channel. Do not infer that a newly released model, upload mode, payment option or quota is included.
No first-party list exists
Use “not stated” and explain what a reader can verify safely. A third-party test may be a lead for research, but it is not a provider guarantee and should not become a permanent map label.
Use the AI availability map to make a safe decision
Start with the provider row, then check the account and plan requirements. If those are satisfied but the request still fails, collect the exact error and perform only a permitted network diagnosis. If the error remains an eligibility or payment decision, stop changing routes and contact the provider. If the source is silent, choose a supported surface or postpone the task rather than treating uncertainty as permission.
This sequence also makes the map easier to maintain: every row has a defined question, a source boundary, an evidence date, and a stopping rule. It prevents the page from becoming a list of permanent promises while still giving readers a practical way to investigate a real failure.
Summary
- Treat this as a source index with a date, not a static promise.
- Compare web, API, mobile, account, plan and feature rules separately.
- Use a VPN only to diagnose a permitted network-layer problem.
FAQ
Does this map guarantee access?
No. It points to current primary sources; account, plan, rollout, law and network conditions still apply.
Why are there no permanent green or red country labels?
Provider policies change and product surfaces differ. A dated source is safer than a stale universal label.
Should I use a VPN to test every row?
No. First check the provider, account and product surface. Use a VPN only where lawful and only for a network-layer diagnosis.
Does payment unlock an unsupported region?
Not necessarily. Payment is only one of the provider's conditions: supported regions, identity, and account eligibility are still decided under the provider's own list and rules, so a successful payment does not by itself open an unsupported region.
How often should I refresh this map?
Refresh it whenever a provider changes its supported-country, account, plan, or feature documentation. Record the page and date instead of treating an old row as a permanent answer.
Disclaimer: This article is for general informational purposes only. Follow provider requirements and local law.
Sources:
- OpenAI — ChatGPT supported countries — https://help.openai.com/en/articles/7947663-chatgpt-supported-countries
- Google — Gemini web app availability — https://support.google.com/gemini/answer/13575153
- Google — Gemini mobile app availability — https://support.google.com/gemini/answer/14579026
- Anthropic — Supported countries and regions — https://www.anthropic.com/supported-countries
- X Help — About Grok — https://help.x.com/en/using-x/about-grok
- Google — NotebookLM is now Gemini Notebook — https://blog.google/innovation-and-ai/products/gemini-notebook/notebooklm-gemini-notebook/
- OpenAI — Supported countries and territories — https://developers.openai.com/api/docs/supported-countries
- Google AI for Developers — Available regions for Google AI Studio and Gemini API — https://ai.google.dev/gemini-api/docs/available-regions
- Google — Gemini Notebook frequently asked questions — https://support.google.com/notebooklm/answer/16269187
- GitHub — GitHub and trade controls — https://docs.github.com/en/site-policy/other-site-policies/github-and-trade-controls
- Suno — Terms of Service — https://suno.com/terms
- xAI — Welcome to Grok — https://docs.x.ai/grok/overview
Sources checked 4 October 2026.
Related Articles:
