Is the platform having an incident?
Review official status and recent incidents before treating the problem as local.
AI service troubleshooting
ChatGPT works poorly, or Codex and the API cannot connect?
ChatGPT not loading, or Codex and the OpenAI API unable to connect? Check service status, web/API reachability, IP, DNS, WebRTC and browser consistency.
This page helps locate connection problems. It does not predict account enforcement or represent an official OpenAI verdict. The check contacts public Google and Cloudflare STUN nodes; reachability does not prove account access.
Use this page when you run into one of these problems
You do not need to understand ASN, STUN or browser fingerprinting. We translate the underlying evidence into likely problem areas.
- 01ChatGPT will not load
- 02Login, OAuth or verification is failing
- 03The web app works but Codex or the API fails
- 04The connection became unstable after a network change
Diagnosis results
The evidence most relevant to access, login and connection stability is explained together.
Public IP--Waiting
Supported region--Waiting
Network provider--Waiting
ASN / network organization--Waiting
IP type--Waiting
Network type--Waiting
Risk intelligence source--Waiting
Proxy / VPN--Waiting
Route consistency--Waiting
Timezone parity--Waiting
DNS status--Waiting
DNS resolver--Waiting
Likely problem areas
Current-session evidence points to areas worth checking. Unknown data stays neutral, and no single anomaly decides the result.
Waiting
Web, login and API connection checks
These checks only observe whether the browser can start a request or complete a handshake. They do not prove that an account, login, API key or product feature works.
chatgpt.com--Waiting
api.openai.com--Waiting
auth.openai.com--Waiting
ChatGPT WebSocket--Waiting
Codex WebSocket--Waiting
Technical evidence (advanced)For technical review of browser fields, TraceScope API receipts, WebRTC candidates and request timing from this run.
{}
What this diagnosis helps you determine
Separate a platform incident from a local network or browser-environment issue before changing routes or reinstalling anything.
Can your current network reach it?
Check web, login and API routes separately, then compare IP, DNS, WebRTC and IPv6 paths.
Does the browser environment disagree with itself?
Compare IP region, timezone, language and browser claims to surface inconsistencies worth reviewing.