The Pulse
OpenAI Resolves Errors Across ChatGPT, Codex and Its APIs
OpenAI marked elevated errors affecting ChatGPT, Codex and its API resolved on September 29, then posted a further recovery-status update on October 6. The incident record lists affected product components and says the company would publish
AI.info Team · Written with AI ·
OpenAI marked the incident resolved on September 29
OpenAI’s status page records elevated errors affecting ChatGPT, Codex and the API, including the Agents API. The incident began with an update at 5:52 p.m. on September 29, 2026. At 6:24 p.m., the company said it was investigating elevated errors affecting ChatGPT, Codex and the API, and warned that some users might encounter failed requests or tasks that did not complete.
OpenAI posted further investigation updates at 7:08 p.m. and 7:39 p.m. The later update also mentioned difficulty logging in or signing up. Starting at 9:09 p.m., the page records several monitoring updates saying a mitigation had been applied and recovery was being monitored. The incident was formally marked “Resolved” at 11:14 p.m. on September 29—not on October 6.
The page also displays an October 6, 2026, update at 8:26 a.m. stating that all impacted services had fully recovered. That later recovery-status notice follows the September 29 resolution entry in the update history; it does not change the date when OpenAI first marked the incident resolved. The page labels the incident “Degraded performance,” rather than describing every affected service as completely unavailable.
The listed impact crossed three product groups
OpenAI’s affected-components list names 12 API components: Chat Completions, Responses, Agents, Fine-tuning, Embeddings, Images, Batch, Audio, Moderations, Realtime, Files and Login. The ChatGPT group contains 14 entries, including Conversations, Login, ChatGPT Work, Codex in ChatGPT Desktop, Compliance API, Search, file uploads, voice mode, GPTs, Image Generation, Deep Research, Agent, Sites and Connectors/Apps.
The four listed Codex components are Codex Web, Codex API, CLI and the VS Code extension. Taken together, the page’s lists show that the report covered more than ChatGPT conversations or a single developer endpoint. They identify the components OpenAI associated with the incident, but do not provide individual error rates for those components or say that each one was affected in the same way.
OpenAI cautions that its availability metrics are aggregated across tiers, models and types of errors. It says an individual customer’s availability may differ depending on subscription tier and the model or API features used. The incident page gives no count of affected users or requests, so it does not quantify the disruption’s reach.
RCA deadline followed the September resolution
In the September 29 resolution update, OpenAI stated:
“The issue causing elevated errors across ChatGPT, Codex, and the API has been resolved, and all affected services have recovered.”
OpenAI thanked users for their patience and said a detailed root-cause analysis would be published within the next five business days. That deadline was attached to the September 29 resolution update. The October 6 entry says impacted services had fully recovered, but does not establish a new starting date for the RCA deadline.
The incident record reports that a mitigation was applied and recovery monitored, but does not describe the mitigation or identify the cause of the errors. It also does not explain the interval between the September 29 resolution entry and the October 6 recovery-status update. Those details are not provided in the status-page history.