OpenAI
OpenAI is operational
History
Incidents in 90 days
24
Days with an incident
16
Median duration
1 h 51 min
Longest incident
3 days
Components
25Oct 30, 2026
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.status.openai.com
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.status.openai.com
Oct 27, 2026
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.status.openai.com
The issue is now resolved.status.openai.com
Oct 23, 2026
All impacted services have now fully recovered.status.openai.com
All impacted services have now fully recovered.status.openai.com
All impacted services have now fully recovered.status.openai.com
Oct 22, 2026
All impacted services have now fully recovered.status.openai.com
All impacted services have now fully recovered.status.openai.com
All impacted services have now fully recovered.status.openai.com
Oct 21, 2026
All impacted services have now fully recovered.status.openai.com
All impacted services have now fully recovered.status.openai.com
All impacted services have now fully recovered.status.openai.com
Oct 14, 2026
All impacted services have now fully recovered.status.openai.com
All impacted services have now fully recovered.status.openai.com
All impacted services have now fully recovered.status.openai.com
Oct 9, 2026
All impacted services have now fully recovered.status.openai.com
All impacted services have now fully recovered.status.openai.com
All impacted services have now fully recovered.status.openai.com
Follow OpenAI
Your coding agent knows when OpenAI is down, and tells you when a failure is theirs, not yours. You can also get OpenAI incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "openai" and tell me if OpenAI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=openai/feed subscribe https://outages.live/feed.xml?providers=openaiGo from tracking outages to fixing production issues with Polylane.
Try Polylane