ChatGPT Work and Dots Errors
ChatGPT Work and Dots do not work correctly, and users see errors. OpenAI reports that it applied a mitigation and now monitors the services to confirm recovery. The incident started at 15:25 UTC on 5 November 2026 and continues.
State
Monitoring
Started
Ongoing for
9 h 35 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
1 h 35 min 17%
Identified
6 min 1%
Monitoring
7 h 54 min 82%
Updates
Times in UTCAs posted by OpenAI
We’ve applied a mitigation and are monitoring the affected services to confirm recovery.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
We’re investigating a potential issue for the listed services and checking how it affects users. We’ll share an update when we know more.
OpenAI in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
20
Median duration
1 h 59 min
This incident
4.8× the median
Other OpenAI incidents
All incidentsOpenAI·Elevated error rates across paid ChatGPT plans
OpenAI reported elevated error rates for some users on paid ChatGPT plans when they sent messages. OpenAI applied a mitigation and monitored the services. OpenAI reports that the incident is resolved, and it lasted 1 hour and 54 minutes.
OpenAI·File upload errors in ChatGPT
ChatGPT file uploads and reading of uploaded files did not work for some users. OpenAI reported the incident as resolved. The outage lasted about 4 hours and 53 minutes.
OpenAI·Elevated errors with search in Dots, ChatGPT Work, and certain ChatGPT thinking experiences
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
OpenAI·Elevated errors for GPT Image 2 API image edits
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
OpenAI·6.1 Sol Degraded Model Performance
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
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.cc/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.cc/feed.xml?providers=openai/feed subscribe https://outages.cc/feed.xml?providers=openaiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane