“ChatGPT won’t open” is almost never an OpenAI-wide outage. Real platform-wide outages happen 2–3 times a year and don’t last long. The “won’t open” you see day to day is 95% client-side: regional gating, DNS, proxy node, Cloudflare challenge, browser extensions.
The right order is confirm the service is up → isolate the client → tune the network → switch device only as a last resort. The rest of this guide walks that order.
Symptoms
- Blank page or infinite spinner on chat.openai.com
- Cloudflare 5xx errors / “Checking your browser” hangs
Access denied,Unsupported region,We're sorry, you are not eligible- You can log in but can’t send a message (button does nothing)
- The page loads but every message returns an error
Common causes
In rough order of frequency:
1. Current IP is in an unsupported region
OpenAI explicitly doesn’t serve mainland China, Hong Kong (intermittently), Russia, Iran, Cuba, North Korea, Syria, and others. Even on VPN, if your exit IP geo-locates to one of these, you’ll see “unsupported region.”
How to verify: browserleaks.com/ip — check the country / region. In an unsupported region → switch VPN.
2. DNS poisoning / public resolver flake
In some regions, ISP DNS poisons chat.openai.com, chatgpt.com, auth0.openai.com — wrong IP or no resolution. Symptom: google.com loads fine, only ChatGPT doesn’t.
How to verify: in a terminal, nslookup chatgpt.com 1.1.1.1. Should return Cloudflare / OpenAI IP ranges (typical 104.18.x.x, 104.16.x.x). A weird IP or timeout = poisoned.
3. Proxy / VPN exit node is flagged
OpenAI maintains an IP risk list. Free VPNs, shared proxies, datacenter IPs all get 403’d outright. Symptom: any OpenAI domain returns Access denied or Cloudflare 1020.
How to verify: switch to a commercial US-East / US-West node and retry. If that works, the previous node was blacklisted.
4. Cloudflare challenge blocked by browser extension
OpenAI uses Cloudflare for bot protection — challenges show as “Checking your browser…” Privacy / anti-tracking extensions (Privacy Badger, uMatrix, ScriptSafe, strict Brave Shields) break the JS the challenge runs.
How to verify: open an incognito window (extensions disabled) and check if it loads.
5. OpenAI is genuinely down
Low probability, but when it happens everyone hits it.
How to verify: status.openai.com. “All Systems Operational” = green. Anything else = real outage, wait.
6. Browser cookie / cache corrupted
Old cookies cause login to hang, or a service worker loaded a bad chunk and now spins forever.
How to verify: incognito works = your normal browser’s cookies / cache are bad.
Shortest path to fix
30-second checks first:
Step 1: Check the OpenAI status page
Open status.openai.com. Anything not all-green → wait — no client-side fix will help.
# CLI equivalent
curl -s https://status.openai.com/api/v2/status.json | python -m json.toolStep 2: Incognito + no extensions
Cmd/Ctrl + Shift + N to open an incognito window (extensions disabled by default), visit chatgpt.com.
- Loads → your regular browser’s extensions / cookies / cache are the issue (Step 3)
- Still won’t load → network layer issue (Step 4)
Step 3: Whitelist extensions + clear site data (if browser-side)
- Find the offending extension: add
chatgpt.comto the whitelist of each privacy / ad-block extension - Clear cookies + cache for chatgpt.com: DevTools → Application → Storage → Clear site data
- Sign in again
Step 4: Switch DNS
A lot of “won’t open” cases are DNS poisoning. Change system DNS to:
| Pick | DNS |
|---|---|
| Recommended | 1.1.1.1 (Cloudflare) + 1.0.0.1 |
| Backup | 8.8.8.8 (Google) + 8.8.4.4 |
| Privacy | 9.9.9.9 (Quad9) |
macOS: System Settings → Network → current network → Details → DNS → add the IPs above.
Windows: Settings → Network → select adapter → DNS → switch to manual.
iOS: Settings → Wi-Fi → current network → Configure DNS → Manual.
Then verify with nslookup chatgpt.com — should return OpenAI / Cloudflare IPs.
Step 5: Switch VPN / proxy node
If you use a VPN:
- Switch to a commercial / paid node (not free)
- Prefer US-East / US-West (OpenAI’s main service region)
- If a single node keeps getting blocked, the VPN provider as a whole is being risk-listed — switch providers
- Don’t use auto IP rotation
Test: after switching, visit browserleaks.com/ip to confirm the IP isn’t labeled “Hosting” / “Datacenter.”
Step 6: Last-resort device / network swap
Phone off Wi-Fi → 4G/5G → ChatGPT app.
- App works → your computer’s network or browser is the issue
- App also fails → your account or IP range is broadly locked, see suspicious activity
Step 7: Still nothing — check recent changes
If it worked hours ago but doesn’t now:
- Did you update macOS / Windows / the browser?
- Did you install a new extension?
- Did you switch VPN nodes or run any new proxy app?
- Did your office network add a new firewall rule?
Roll changes back one at a time and retest.
When this guide applies
This covers the “won’t load / Cloudflare 5xx / access denied” cluster. For payment / account-suspended / wrong-password issues, see ChatGPT login fails. For “loads but answers slowly,” see ChatGPT slow response.
Prevention
- Bookmark status.openai.com
- Don’t flip proxy nodes constantly — IP reputation matters; pick a stable node and stick with it
- Chrome / Edge are more stable here than niche browsers (OpenAI mostly tests on Chromium)
- Permanently set system DNS to 1.1.1.1 + 1.0.0.1 to avoid ISP-level flakes
- Don’t install new browser extensions during critical work — many extensions block ChatGPT
- Pick one stable, paid VPN provider; use a single node long-term
Related
- ChatGPT login fails
- ChatGPT stuck on loading / thinking
- ChatGPT network error fixes
- ChatGPT suspicious activity
- ChatGPT beginner guide
- ChatGPT prompt improvement
- ChatGPT model selection guide
- ChatGPT Response Cuts Off Mid-Sentence — Why and the Fastest Fix
Tags: #ChatGPT #Debug #Troubleshooting