- ChatGPT Work Degraded performance
- Ads API Operational
- Ads Manager Operational
- Agent Operational
- Audio Operational
- Batch Operational
- Chat Completions Operational
- ChatGPT Atlas Operational
- CLI Operational
- Codex API Operational
- Codex in ChatGPT Desktop Operational
- Codex Web Operational
- Compliance API Operational
- Connectors/Apps Operational
- Conversations Operational
- Deep Research Operational
- Embeddings Operational
- FedRAMP Operational
- File uploads Operational
- Files Operational
- Fine-tuning Operational
- GPTs Operational
- Image Generation Operational
- Images Operational
- Login Operational
- Login Operational
- Moderations Operational
- Realtime Operational
- Responses Operational
- Search Operational
Official OpenAI service status, supplemented with active incidents already imported into this site.
Live OpenAI Status Across Key Services
OpenAI publishes separate status components for multiple products and workflows, and an incident may be limited to one or more of them. The component-aware card above shows the public feed coverage available now; the sections below organize recent incidents by service.
ChatGPT (Web and Mobile)
The consumer-facing chatbot at chatgpt.com and the iOS/Android apps. This is the most-used service and the primary focus of our monitoring.
OpenAI API
Programmatic access for developers. API availability can differ from consumer ChatGPT availability, so check the component-specific status and your own authenticated requests.
Codex
Code generation models (GPT-powered code completion and agentic code tools).
Sora
OpenAI’s video-generation model. Typically rolled out gradually and experiences outages independent of ChatGPT.
DALL-E and Image Generation
Image generation, available both inside ChatGPT and via the API. Can fail independently of the chat service.
Voice Mode
Voice conversations inside ChatGPT. Official incidents may affect Voice Mode while other ChatGPT features remain available.
Frequently Asked Questions
Is OpenAI one service or many?
OpenAI publishes component-level status for many services. An incident can affect one component, several components or the broader service, so scope should be read from the official incident update rather than inferred.
If ChatGPT is down, is the API down too?
Not necessarily. OpenAI reports component-level incident scope, and the API and consumer ChatGPT can show different availability. Check the official affected components and your own authenticated requests.
Sources and scope
The live card summarizes the components currently exposed in OpenAI's public status feed. Missing components remain unknown rather than being inferred as operational.