ChatGPT service status
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
Live Domain Check
Run a live reachability check for chatgpt.com. Compare the regional responses with the problem you see in ChatGPT.
Find ChatGPT help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
ChatGPT sign-in, one conversation, file upload and response generation require different checks.
The checker above requests chatgpt.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual ChatGPT action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
The official help article explains how to contact support through the Help Center.
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
The official help article explains how to contact support through the Help Center.
Open ChatGPT help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Model/feature, error text, UTC time, browser/app version and request/conversation reference through private support.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to ChatGPT.
These are troubleshooting comparisons, not claims that ChatGPT is currently experiencing a particular incident.
Try a short new conversation to distinguish a thread-specific failure, keeping the original conversation intact.
Compare the exact ChatGPT component on OpenAI Status and the official help topic for the displayed error.
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when ChatGPT seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open chatgpt.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader ChatGPT issue.
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting ChatGPT support.
Run the chatgpt.com check and compare its original timestamps and responses with your actual error. ChatGPT sign-in, one conversation, file upload and response generation require different checks.
Use the official help/reporting resource linked above. The official help article explains how to contact support through the Help Center.
Try a short new conversation to distinguish a thread-specific failure, keeping the original conversation intact. Compare the exact ChatGPT component on OpenAI Status and the official help topic for the displayed error.
Model/feature, error text, UTC time, browser/app version and request/conversation reference through private support.