OpenAI applied a mitigation for elevated errors affecting multiple ChatGPT products in the early hours of October 6, 2026, and moved the incident to monitoring of recovery. The status record lists five affected components inside the ChatGPT group with degraded performance. For companies running sales and support on ChatGPT, the event matters as a reminder to plan for short service degradations.
What the October 6 status record shows
The incident is titled as elevated errors affecting ChatGPT conversations, image generations, Spaces and Pages, API rehydration, and Dots. The first status update at 2:41 AM UTC on October 6 said OpenAI was investigating the issue for the listed services. A second update three minutes later, at 2:44 AM UTC, reported that the mitigation had been applied and recovery was being monitored. The main status page carried the incident as an active banner affecting ChatGPT.
The record names five components within the ChatGPT product group: Conversations, ChatGPT Work, Image Generation, dots, and Space. The incident title separately refers to Spaces and Pages, API rehydration, and Dots, which indicates a spread across conversational, visual, and workspace functions rather than a single feature. The status history lists the mitigation update as the latest entry for October 6. No root cause analysis for this incident was included in the published updates.
The new record sits among several other open items on the status page. A second active incident, titled Elevated error rates in Codex Cloud, was in monitoring status with 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. Earlier on October 6, two further incidents were marked fully recovered: API Platform login and administration APIs at 1:35 AM and ChatGPT conversations at 12:01 AM.
What repeated incidents mean for business users
For teams that use ChatGPT for drafting, image generation, and workspace documents, the practical effect is uneven availability of adjacent functions during the same window. Conversations may degrade while image generation, Spaces, Pages, or rehydration through the API behave differently, which complicates standard operating procedures. Smaller firms with one channel built on ChatGPT feel the pause directly, while larger firms can shift load between teams, models, or manual fallback. Documented fallback steps reduce idle time.
The status history adds context for procurement decisions. Two October 5 entries ended in resolution: Admin Console inaccessibility was marked fully recovered at 9:07 PM, and a Pages saving and live editing issue was resolved at 1:04 PM. A September 29 incident with elevated errors across ChatGPT, Codex, and the API, including the Agents API, was reported resolved, with a detailed root cause analysis promised within five business days. Buyers should ask vendors how such analyses are shared and whether work mode and Codex issues share dependencies.
Availability figures for July through October 2026 provide a baseline for service level discussions. The ChatGPT group with 16 components stands at 99.65% uptime, while the APIs group with 13 components stands at 99.96%. Among the five named components, Conversations is listed at 99.96%, ChatGPT Work at 99.86%, Image Generation at 99.79%, and dots and Space at 100%. The page notes that metrics are aggregate across tiers, models, and error types, so individual availability may vary by subscription and model.
