OpenAI Status
Official status page for ChatGPT and API systems.
Live Domain Check
Check if OpenAI is down right now (openai.com). Run a live multi-region check to see whether OpenAI is offline for everyone or just you.
Get official OpenAI outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
OpenAI incidents can affect ChatGPT web sessions, API latency, model availability, file uploads, or authentication separately. Checking both web and platform endpoints helps determine whether your issue is local, product-specific, or global.
For OpenAI, incident signals are often feature-specific: ChatGPT UI loads but requests fail or hang. API responses degrade with elevated latency/timeouts. If this matches what you see on openai.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
OpenAI provides an official status page with component-level incident reporting and history.
Official status page for ChatGPT and API systems.
Official support articles and request submission.
Useful to confirm platform access vs consumer UI issues.
Monitor real-time social updates and official posts related to OpenAI outages.
Official teams often post outage status updates and recovery progress through these social channels.
Use these service-specific patterns to identify likely root cause quickly and choose the right next step.
Practical steps to follow when openai.com seems down. Use this checklist to confirm whether OpenAI is down for everyone or only for you.
Run openai.com in WebsiteDown.org first, then open openai.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official OpenAI service status page and compare timestamps with your failed checks.
Test related hosts such as chatgpt.com, status.openai.com. If they work while openai.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for openai.com, then share those details with OpenAI support for faster triage and recovery.
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, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on openai.com. Avoid repeated password or security resets until you confirm this is not a broader OpenAI issue.
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting OpenAI support.
Run the automatic multi-region check on this page for openai.com. If most regions fail at the same time, OpenAI is likely experiencing a broader outage or partial incident.
If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use the Official Status, Support, and Social Channels section above in this order:
Official dashboards are authoritative but can lag during the first minutes of an incident. Combine those sources with this checker to confirm whether OpenAI is down globally, regionally degraded, or only affecting specific users.
That pattern usually points to path-specific issues rather than a full OpenAI outage. Common causes include:
Test in a private window, temporarily disable VPN/extensions, and retry from a second network. If one feature fails while the homepage still loads, treat it as a partial incident.
Use this quick triage sequence for openai.com:
This order helps you avoid unnecessary account resets when the OpenAI issue is provider-side.