OpenAI applied a mitigation and was monitoring recovery from elevated errors affecting multiple ChatGPT products early on October 6, 2026, according to an incident record on the company’s status page. The record lists five affected components with the incident marked at degraded performance.
The incident record carries the title “Elevated errors affecting multiple products including ChatGPT (conversations), Image generations, Spaces and Pages, API rehydration, and Dots.” Its first update, posted at 2:41 AM UTC on October 6, 2026, stated that OpenAI was investigating the issue for the listed services.
A second update at 2:44 AM UTC states: “We have applied the mitigation and are monitoring the recovery.” The incident’s status is listed as Monitoring with degraded performance. OpenAI’s status history lists the incident under October 6 with that mitigation update as its latest entry.
Components Listed on the Incident Record
The record lists five affected components, all within the ChatGPT product group: Conversations, ChatGPT Work, Image Generation, dots, and Space. The incident title separately names Spaces and Pages, API rehydration, and Dots among the affected products.
OpenAI’s main status page displays the incident as an active banner under a notice that the company is currently experiencing issues, marks it as ongoing, and notes that it affects ChatGPT.
Other Incidents on OpenAI’s Status Page
The new incident was not the only open item. The main status page showed a second active incident, titled Elevated error rates in Codex Cloud, listed in Monitoring status with a mitigation applied and marked as ongoing for eight hours. A third incident, titled Elevated Work Mode errors, was listed as mitigated with recovery under monitoring, marked as ongoing for nineteen hours and noted as affecting ChatGPT.
The history page shows the Work Mode incident’s most recent update at 9:50 AM on October 5, 2026, and the Codex Cloud incident’s most recent update at 6:07 PM on October 5, 2026. Two other October 5 entries ended in resolution: the Admin Console was intermittently inaccessible before OpenAI reported all impacted services fully recovered at 9:07 PM, and an issue affecting saving and live editing in Pages was resolved with a 1:04 PM update.
Earlier on October 6, 2026, the history page lists two further incidents that OpenAI says fully recovered: elevated errors in API Platform login and administration APIs, with a 1:35 AM update, and elevated errors in ChatGPT conversations, with a 12:01 AM update.
The log also shows a September 29, 2026 incident involving elevated errors across ChatGPT, Codex, and the API, including the Agents API, which OpenAI reported as resolved with all affected services recovered. In that entry, OpenAI said a detailed root cause analysis would be published within five business days.
Availability Figures and Reporting Methodology
The status page reports availability figures covering July 2026 through October 2026. The ChatGPT group, comprising 16 components, stands at 99.65% uptime for the period, and the APIs group, comprising 13 components, at 99.96%. The Codex group is listed at 99.95% across four components, and the FedRAMP group at 100% across one component. The Ads Platform group shows two components, with the Ads API at 99.992% uptime.
For the five components named in the new incident, the page reports 99.96% uptime for Conversations, 99.86% for ChatGPT Work, 99.79% for Image Generation, 100% for dots, and 100% for Space. Among other ChatGPT group components, the page lists Login at 99.97%, Voice mode at 99.96%, Search at 99.98%, and Connectors/Apps at 99.96%.
Within the APIs group, the page lists the Images component at 99.96% uptime and the Login component at 99.995%. The Codex group’s four components, Codex Web, Codex API, CLI, and the VS Code extension, are each listed at 99.95% uptime.
The page states that availability metrics are reported at an aggregate level across all tiers, models and error types. It adds that individual customer availability may vary depending on subscription tier and the specific model and API features in use.
Credit: Source link
