OpenAI 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 openai.com. Compare the regional responses with the problem you see in OpenAI.
Find OpenAI help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
The openai.com company site is separate from ChatGPT and authenticated API requests.
The checker above requests openai.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual OpenAI 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 OpenAI 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.
Product/model, endpoint, request ID, error and UTC time without keys or confidential input.
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 OpenAI.
These are troubleshooting comparisons, not claims that OpenAI is currently experiencing a particular incident.
Identify the affected product and capture the real failed endpoint or UI action.
Compare the matching OpenAI Status component; for API errors preserve status and request ID before repeating costly requests.
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 OpenAI seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open openai.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 OpenAI 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 OpenAI support.
Run the openai.com check and compare its original timestamps and responses with your actual error. The openai.com company site is separate from ChatGPT and authenticated API requests.
Use the official help/reporting resource linked above. The official help article explains how to contact support through the Help Center.
Identify the affected product and capture the real failed endpoint or UI action. Compare the matching OpenAI Status component; for API errors preserve status and request ID before repeating costly requests.
Product/model, endpoint, request ID, error and UTC time without keys or confidential input.