ChatGPT or Claude Not Working? A Network-First Checklist

The IP is one suspect, not the only one

When ChatGPT, Claude, or a similar service refuses access, the community reflex is "my IP is dirty". Sometimes that is true. But identical symptoms—"not available in your country", endless verification loops, 1020 errors, blank screens after login—are also produced by account region settings, browser extensions, DNS misconfiguration, IPv6 leaks, payment-country mismatches, rate limits, and plain provider outages. Changing your network before isolating the variable is how people spend money on new proxies to fix a browser cookie.

This guide works from the cheapest, most common causes to the most expensive. Follow the order; each step either fixes the problem or removes a suspect, so the final network change—if it is ever needed—is made with evidence instead of hope.

Step 0: Record the exact error

Different failures point to different layers. "Access denied / Error 1020" is a CDN-level block (network or reputation). "Not available in your country" is region policy (IP location or account region). A login loop or instant logout is usually cookies or extensions. "Something went wrong" after sending a message is often rate limiting or an outage. Slow, partial page loads with console errors suggest DNS or blocked third-party scripts. Write down the exact text and the URL where it happens—this one habit eliminates half the guesswork.

Step 1: Rule out the platform itself

Check the provider’s official status page (status.openai.com, status.anthropic.com) and a third-party outage tracker before touching anything on your side. Then test public reachability while logged out: if the marketing homepage loads but the app does not, the platform is reachable and your problem is account- or browser-side. If even the homepage fails at the CDN layer with an access error, the network moves up the suspect list.

Step 2: Compare the regions end to end

AI services evaluate several regions at once, and any mismatch can trip a check. List them explicitly: the country your IP geolocates to (check it—a VPN may exit in a different country than its app claims), the country of your account registration, your payment method’s issuing country, your DNS resolver’s location (some providers answer with region-specific results), and your system/browser language. A common failure: IP in Japan, account registered in an unsupported region, payment card from a third country. The platform sees three conflicting stories and chooses the safest answer—refusal.

Also check both IP families. Many setups route IPv4 through a proxy while IPv6 goes direct (or vice versa), so the service sees your real location on one protocol and your proxy location on the other. Disable IPv6 temporarily or verify that both protocols exit in the same country. This single mismatch is responsible for a large share of "my VPN says US but I am still blocked" reports.

Step 3: Clean the browser before the network

Browser state is the most underestimated cause. Test in a clean profile or private window with all extensions disabled—ad blockers, script blockers, "privacy" extensions, and even some grammar tools break the challenge scripts these services depend on. If the clean profile works, re-enable extensions one at a time to find the culprit. Clear cookies for the service’s domain if you see login loops. And confirm your device clock is accurate: a skewed clock breaks TLS and token validation in ways that look exactly like network blocks.

Step 4: Only now, evaluate the IP

With platform, regions, and browser eliminated, check the address itself. Run a diagnostic and look at the specific fields that matter for AI services: detected country, ASN type (hosting ranges face stricter controls from some providers), and dated reputation evidence rather than a generic score. A hosting IP with clean history may work fine; a residential IP on a blocklist may not. Remember that services update their policies and range lists independently, so a network that worked last month can stop working without anything being "wrong" with it.

If you conclude the network is the problem, change one variable and retest with the exact error text from Step 0. Keep a simple log of what you tried—date, exit country, result. It turns a frustrating guessing game into a short, reproducible experiment, and it is exactly the information a support team will ask for if you escalate.

What never to do

• Never send passwords, API keys, session cookies, or recovery codes to anyone offering to "fix" your access—including support-looking accounts on social media.
• Never buy "guaranteed unblocked" accounts from resellers; they are typically stolen or shared and create far bigger problems than a blocked IP.
• Never rapid-fire retry a blocked login; repeated attempts escalate automated defenses and can convert a temporary block into an account review.
• Never run a full network change (new proxy, new DNS, new browser) all at once—you will never learn which variable mattered.

References and source material

These sources are provided so readers can verify the technical background. Inclusion does not imply endorsement of TrustIP.

• OpenAI status page
• Anthropic status page
• Cloudflare Error 1020 documentation