Productspublished

OpenAI Applies Mitigation as ChatGPT and Codex Errors Hit Core Services

The incident affected basic access and conversations as well as tools for search, files, voice, research, agents and coding. OpenAI was monitoring recovery, but had not published a cause.

By 2 min read
OpenAI Applies Mitigation as ChatGPT and Codex Errors Hit Core Services
OpenAI Applies Mitigation as ChatGPT and Codex Errors Hit Core Services

Listen to this story

The audio brief

About 1:31
0:001:31
Read transcript
OpenAI has applied a mitigation after elevated errors disrupted ChatGPT and Codex, but the company is still monitoring recovery and continues to list the incident as degraded performance. The disruption began around 10:58 a.m. Eastern time on September 3, reaching far beyond ordinary chat. Users encountered problems with login and conversations, while affected tools included ChatGPT Search, file uploads, Voice, GPTs, image generation, Deep Research, Agent, and ChatGPT Work. Codex services were affected as well, putting both everyday users and coding workflows in the same outage window. OpenAI says it began investigating the listed services at 2:58 p.m. Eastern time, then reported the mitigation at 3:22 p.m. The incident covered 15 ChatGPT components and four Codex components. Those counts describe the number of marked services, not the number of people affected. For the displayed period, the status page showed aggregate uptime of 99.62 percent for ChatGPT and 99.98 percent for Codex. OpenAI cautions that those figures combine subscription tiers, models, and error types, so any individual user’s experience could differ. The company had not disclosed a cause or confirmed full restoration when reported. The key thing to watch is whether recovery monitoring ends with a clear all-clear—and whether OpenAI explains what produced the elevated errors in the first place.

Story brief

3 key points

OpenAI’s September 3 incident extended beyond ordinary ChatGPT conversations: login, Search, file uploads, Voice, GPTs, image generation, Deep Research, Agent, ChatGPT Work and Codex were marked affected. The company began investigating at 2:58 p.m. ET and reported a mitigation at 3:22 p.m., but continued recovery monitoring without identifying a cause or confirming full restoration. The status page recorded 15...

  1. 01

    The disruption began around 10:58 a.m. Eastern time on September 3.

  2. 02

    OpenAI listed 15 affected ChatGPT components and four affected Codex components.

  3. 03

    Aggregate displayed uptime was 99.62% for ChatGPT and 99.98% for Codex.

OpenAI has applied a mitigation for elevated errors across ChatGPT and Codex, moving a disruption that touched login, conversations and specialized tools into recovery monitoring. The company still listed the incident as degraded performance.

The disruption began at approximately 10:58 a.m. Eastern time on September 3. It affected ChatGPT conversations and login, while Codex services were also affected. The breadth matters because the incident was not confined to the core chat experience: it also reached functions used for information retrieval, file work, voice interaction and longer-running tasks.

OpenAI’s status incident counted 15 affected ChatGPT components and four affected Codex components. Those component counts describe the services marked in the incident, rather than a measure of how many people encountered errors.

Services named as affected

  • ChatGPT Search, file uploads, Voice, GPTs and image generation were among the affected functions.
  • Deep Research, Agent and ChatGPT Work were also named as affected services.
  • Codex joined ChatGPT’s consumer and workplace functions in the disruption.

For the displayed period, OpenAI’s status page showed aggregate uptime of 99.62% for ChatGPT and 99.98% for Codex. The company says those availability figures combine subscription tiers, models and error types; individual availability may vary with the tier, model and API features in use.

OpenAI had not published a cause for the disruption at the time of the report. Its last status update said recovery monitoring was ongoing, leaving users without an explanation of what produced the elevated errors or whether the mitigation had fully restored affected functions.

Sources

  1. status.openai.comChatGPT Work Mode High Error Rates
  2. status.openai.comElevated errors across ChatGPT and Codex - OpenAI Status