If Claude says it is unavailable in your region, start by checking Anthropic’s current official list of supported locations. Then work through the account, browser, and network checks below. A VPN connection can change how a website sees your network location, but it does not make an unsupported location eligible, guarantee access, or resolve an account or service restriction. Availability and requirements can change, so use current official information rather than an old screenshot or a third-party list.
Start here: Confirm that your actual location is supported, identify whether the issue affects Claude’s web app, mobile app, or API, and test without changing several settings at once. If the service is not offered where you are, use it only when and where you meet Anthropic’s current requirements.
Check regional availability and the product you are using
“Claude is unavailable” can refer to several different problems: the service may not be offered in your location, sign-up may be unavailable, a particular account may need attention, or a page may fail to load because of a browser or network issue. These situations can look similar at first, but they call for different next steps. Before changing your setup, note the exact message and where it appears: on the public website, during sign-in, inside the app, or in an API response.
Start with Anthropic’s official supported-country and region information. Check it when the error occurs, not only when you first created your account: service availability and product requirements can change. Confirm the location information for the specific Claude product you want to use. Access to the web app, mobile app, and API may involve different account or setup requirements, so do not assume that availability in one context automatically confirms access in another.
Use your real location and account details. A VPN or proxy may cause a service to see an IP address associated with a different place, but that signal is not proof of eligibility. It can also create a mismatch between your apparent network location and other account or session information. Do not use a VPN to misrepresent your location or bypass a regional restriction. If you are in a supported location and a connection tool is already active, testing on your normal network can help establish whether it is contributing to the problem.
- ✅ Check Anthropic’s current official availability information, not an old search result.
- ✅ Identify whether you are using the web app, a mobile app, or the API.
- ✅ Record the exact error and the step where it appears.
- ❌ Do not treat a changed IP address as proof that you qualify for access.
If the official information says your location is not supported, browser resets and DNS changes are unlikely to resolve the underlying restriction. Avoid repeatedly creating accounts or changing location signals. If the location is supported but the problem persists, continue with the account and connection checks below, then contact official support if needed.
Use the error message to narrow down the cause
Read the wording carefully before troubleshooting. A regional availability notice points toward eligibility or location, while a sign-in prompt, verification request, or account notice points toward the account flow. A blank page, repeated loading indicator, or browser network error may instead involve the browser, an extension, DNS, or the local connection. An API error is not necessarily an indication that the web app is unavailable: the request may have an authentication, permission, billing, or configuration problem.
Capture the message in your notes, including the product, approximate time, browser or app version, and whether the issue happens on another device. Do not include passwords, private conversations, API keys, or full subscription links in screenshots or support messages. If a request identifier is shown, keep it available for official support, but do not post it publicly unless Anthropic’s instructions say that is appropriate.
| Symptom | First area to check | Useful next step |
|---|---|---|
| Explicit region or availability notice | Official supported locations and your actual location | Confirm current eligibility; do not try to disguise your location |
| Sign-in or verification loop | Account details, cookies, browser extensions, and session state | Try a clean browser session and complete the official verification flow |
| Page does not load or keeps timing out | Browser, DNS, network filtering, or connection stability | Compare with another browser or trusted network, changing one factor at a time |
| API request returns an error | API credentials, organization settings, request format, and service notices | Check the response details and current API documentation |
This table is a way to organize checks, not a diagnosis. The same symptom can have more than one cause, and a successful page load does not by itself confirm that every feature or account action is available.
Check the account, browser, and app session
If the location is supported, make sure you are using the intended account and the official sign-in route. An account created with a different email address, an incomplete verification step, or a session left open in another profile can cause confusing prompts. Follow the on-screen recovery or verification process rather than repeatedly submitting forms. If the account displays a restriction or asks you to contact support, use the official channel; changing browser settings cannot resolve an account-level decision.
For a web app issue, begin with a private or incognito window. This creates a relatively clean session and helps distinguish a stale cookie from a broader connection issue. If the page works there, review site data and cookies for Claude in your normal browser, then sign in again through the official page. Avoid deleting all browser data unless you understand that doing so may sign you out of other sites or remove saved preferences.
Temporarily disable extensions that modify scripts, cookies, privacy controls, or network requests, then reload the page. Content blockers and security extensions can sometimes interfere with sign-in or page functions, though disabling them is not a guaranteed fix. Re-enable extensions one at a time after testing so you can identify a specific conflict. Keep your browser current and avoid unofficial extensions that ask for Claude credentials or access to conversations.
On a phone or tablet, update the app through its official distribution channel and check that the device date and time are set correctly. If the app and web page behave differently, note that distinction: it helps separate an app-specific session problem from a broader account or availability issue. Reinstalling should be a later step, not the first one, because it may clear local state without addressing a service-side restriction.
For users who need a separate network configuration for ordinary browsing, a reputable VPN for China can be considered as a connectivity tool where its use is lawful and consistent with the service’s terms. It should not be used to misstate your location or evade Claude’s regional requirements. When troubleshooting a location or sign-in error, first test with the connection configuration disabled if you can do so safely, and compare the result with the official availability information.
Browser check: A clean session is a diagnostic step, not a workaround for unsupported locations. If the same explicit availability notice remains, stop changing browser settings and verify eligibility through official information.
Test network and VPN settings without guessing
When a page times out or fails to load, compare the same action across a small number of trustworthy connections, such as your usual network and a permitted alternative network. Keep the browser, account, and page the same so that the comparison is meaningful. If you use a VPN, proxy, secure DNS service, or managed network, note whether it is enabled. Do not switch several of these at once: otherwise, a change in the result will not tell you which setting mattered.
Check whether the device is using a captive portal, such as a hotel or public Wi-Fi sign-in page, and complete that sign-in before testing Claude. On a managed work or school network, filtering rules may block some services; ask the network administrator rather than attempting to bypass those controls. If other websites work but Claude does not, that observation is useful, but it does not establish whether the cause is regional availability, a service incident, account state, or a specific network rule.
A VPN client can route traffic differently depending on its mode and rules. Split tunneling may send one browser or application through a different route from another, while DNS settings can influence how a domain is resolved. These are reasons to inspect the client configuration, not to assume that changing servers or protocols will restore access. If you are troubleshooting with a VPN turned on, confirm which apps and domains are routed through it, then compare with the VPN turned off where appropriate and lawful.
Do not rely on a single IP-location lookup as a definitive test of your eligibility. Geolocation databases can be outdated or disagree, and a network address is only one of the signals a service may consider. If the location shown by an IP lookup appears wrong, contact your network provider or VPN provider for help correcting the network information; do not use that discrepancy to claim a location where you are not physically present.
- ✅ Keep the same account and browser while comparing permitted networks.
- ✅ Record whether a VPN, proxy, secure DNS service, or network filter is active.
- ✅ Ask an administrator about restrictions on a managed network.
- ❌ Do not cycle through locations or protocols to evade an availability restriction.
Separate web app troubleshooting from API troubleshooting
The Claude web app and the API are different ways to use the service. A web sign-in problem does not automatically mean that an API request is misconfigured, and an API failure does not prove that the web app is blocked in your region. Start by identifying which product you are using and follow its current official documentation. Confirm that the account, access method, and product requirements apply to that specific use.
For the web app
Check that you are on the official site, that the page has finished loading, and that the browser is using the expected account. If you see a region notice, return to the supported-location check. If the page loads but a conversation fails, note whether the error appears before or after submission, and check for a service notice before changing local settings. Do not paste private conversations into third-party diagnostic websites.
For the API
Use the current Anthropic API documentation to verify the endpoint, authentication method, request format, and account or organization configuration. Treat API keys as secrets: do not include them in browser screenshots, public issue reports, shell history shared with others, or support messages. If a key may have been exposed, follow the official instructions for managing or replacing it. Check the response status and error body with sensitive values removed, and distinguish authentication or permission errors from network timeouts.
API access can involve separate setup and account requirements. Verify those requirements in the official documentation rather than assuming that a working web session proves the API is enabled. Likewise, do not assume that a VPN will fix an API error: a request may fail because of credentials, organization settings, request parameters, or a temporary service problem. Make one controlled test, record the result, and compare it with the relevant official guidance.
Keep the diagnosis specific: Test the web app as a web session and the API as an API integration. Matching each error to the product that produced it avoids treating unrelated account, network, and configuration issues as one regional problem.
Improve connection stability and know when to contact support
Once access is confirmed for your actual location, focus on repeatable stability checks. Keep the browser or app updated, use a reliable connection, avoid running multiple network-routing tools at the same time, and check that the selected VPN or proxy mode does not conflict with another client. If you use a client with routing rules, verify that the browser or application follows the route you intended. A connected indicator only confirms that the client reports a connection; it does not prove that Claude traffic follows that route or that the service will accept it.
Change one setting per test and write down the outcome. For example, compare the normal network with a permitted alternative while leaving the account and browser unchanged. Then, if necessary, test a clean browser session while keeping the network unchanged. This method reduces guesswork and makes it easier to return to the previous configuration. Avoid frequent server switching, repeated sign-in attempts, or unexplained DNS changes: they can add new variables without addressing the cause.
Before contacting support, gather the exact error text, the product involved, the device and browser or app, whether the issue occurs on more than one permitted network, and the troubleshooting steps already tried. Include only information requested by the official support process. Never send your password, authentication code, full API key, or private conversation content. If the official region information indicates that access is unavailable where you are, ask support only for clarification of the published requirements; do not request instructions to evade them.
Finally, check current service notices and product documentation before repeating a failed test. A temporary incident may affect many users, while a local browser problem may affect only one device. Neither case can be resolved reliably by guessing at a VPN location. Keep the distinction clear: regional eligibility is a policy question, account access is an account question, and connection stability is a network question. Verify each with the appropriate official source and use the least disruptive test that answers it.