Separate entry, sign-in redirect, and chat failures
| Symptom | Check first | Record |
|---|---|---|
| Site and sign-in page both fail | OpenAI status, local DNS, and connectivity | Exact URL, time, and browser error |
| Public page opens; sign-in fails | Sign-in method, required cookies, scripts, and redirects | The failed step and full message |
| Signed in; conversation area is blank | Site data, extensions, API or static-resource failures | Browser-specific result and network errors |
| Only the current network fails | Public exit, DNS, proxy path, and IPv4/IPv6 | Both families, ASN, region, and connection result |
| Only one account fails | Account, organization, billing, or verification message | Exact action, full message, and recovery access |
Rule out service events before isolating the browser session
Review official service status
If a home connection, mobile connection, and another device fail in the same way, check OpenAI Status first. A clear status page cannot exclude every partial incident, but it prevents unrelated local changes during a known event.
Identify the page and sign-in method
Separate the public site, sign-in page, authorization redirect, and authenticated conversation view. Use the same sign-in method used at registration and retain the exact ChatGPT message.
Compare a clean browser environment
Test in an updated supported browser with a clean profile or private window. Review blocked required cookies, damaged site data, script blocking, and extensions, changing one condition at a time.
Try one known stable network
If the same device recovers elsewhere, compare the original public exit, DNS, proxy chain, and route. Do not rotate several exits because that removes attribution from the test.
Escalate according to scope
Continue browser troubleshooting for a browser-only failure, network troubleshooting for a connection-only failure, and the displayed official support path for an account-only failure.
Inspect exits only when the same page changes with the network
Only when the same ChatGPT page recovers consistently after a network switch in a clean browser session should you compare the original public exit, DNS path, proxy chain, and route. Record IPv4, IPv6, region, ASN, network type, and the ChatGPT connectivity result instead of relying on one overall score.
Proxy, VPN, Tor, data-center, and reputation signals can explain differences between networks, but none proves by itself that ChatGPT rejected an address. Recovery after a network switch only establishes that a network variable deserves further comparison.
Use IPv4, IPv6, and WebRTC as path evidence
A dual-stack network can reach this site over IPv4 while selected ChatGPT resources use IPv6. Review the two address families separately when their countries, ASNs, or network types differ.
A WebRTC exit is supporting evidence about a browser-observable path; it does not prove which address ChatGPT used. The comparison is useful only when the exits and symptom can be reproduced consistently.
Record a reproducible ChatGPT page failure
- Date, time, and time zone of the failure
- Exact URL, actions taken, and complete error text
- Whether signed-out pages, another browser, and another device reproduce it
- Comparison between a home connection and a mobile connection
- Current IPv4, IPv6, ASN, region, and any proxy or managed gateway
- Redacted screenshots or network errors only when they are needed
Sources and evidence limits
Sources below support the stated technical or policy boundary. Diagnostic comparisons in this guide remain observations, not account verdicts.
- OpenAI StatusOpenAI · Official guidance
- Why can't I log in to ChatGPT?OpenAI Help Center · Official guidance
- Network recommendations for ChatGPT errors on web and appsOpenAI Help Center · Official guidance