OpenAI expands the description of the ChatGPT Work incident: Codex Web was also affected, mitigation deployed
OpenAI has updated the incident in ChatGPT Work: it has now emerged that it also affected Codex Web, and a mitigation has been deployed. Sources differ on whether the status is "monitoring" or already "resolved".
OpenAI has published the latest update on the incident that affected ChatGPT Work mode: according to the status page, a mitigation has been deployed, and the affected components — Codex Web, ChatGPT Work, and dots — were being monitored to confirm full recovery. The new update mentions the Codex Web component for the first time, which previous reports did not include.
Sources differ on the current status of the incident: one record states the status as "Monitoring," with the components already in Operational status, while another record states the status as "Resolved," claiming that all affected services are working normally again.
According to earlier records from the OpenAI Status incident history, this involved increased error rates when searching in Dots, in ChatGPT Work, and in some ChatGPT thinking experiences. This earlier incident was subsequently announced as resolved, with a message stating that the affected services had fully recovered.
Why it matters
Incidents in ChatGPT Work mode and related components such as Codex Web or dots can disrupt the work of individuals as well as company workflows built on these tools. The expansion of affected components and the conflicting status information (monitoring vs. resolved) show that companies relying on these services should monitor OpenAI's status page when planning critical tasks.
What was added since the original report
Verified updates
-
The incident also affected the Codex Web component, which was not mentioned in the original report; A specific mitigation for the issue was applied; The services are undergoing continuous monitoring after recovery, not just a one-time resolution; Primary source: OpenAI Status with an operational role
- The incident also affected the Codex Web component, which was not mentioned in the original report
- A specific mitigation for the issue was applied
- The services are undergoing continuous monitoring after recovery, not just a one-time resolution
- Primary source: OpenAI Status with an operational role
-
The incident also affected Dots (elevated errors in search); Certain ChatGPT thinking experiences were affected; The source is primary documentation from OpenAI Status (official incident history); The scope of the incident was broader than just ChatGPT Work
- The incident also affected Dots (elevated errors in search)
- Certain ChatGPT thinking experiences were affected
- The source is primary documentation from OpenAI Status (official incident history)
- The scope of the incident was broader than just ChatGPT Work
Two audiences, two different impacts
What this means
For individuals
Users who recently experienced failed responses in ChatGPT Work mode or when searching in Dots can now expect normal operation.
For a business
Companies using ChatGPT Work mode on the Plus, Pro, Business, Enterprise, and Education plans may have encountered increased error rates during the incident, which could have disrupted automated or team workflows built on this mode.
ProcessesCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.