Cases › operational mistake › LR-2026-0637
ChatGPT unavailable for thousands of users worldwide
Preliminary Why: Publisher not yet named · subject to change
Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.
Status: action reported, no fix
No source states: loss or records, agent tool, could do, deployer, industry.
Severity major: test: many third parties with a stated count of two or more affected parties. The source states thousands of users worldwide reported being unable to access ChatGPT.
OpenAI's ChatGPT service, which also includes its APIs, suffered a widespread disruption in which thousands of users worldwide could not access the product. Users reported login failures, missing chat history, loading problems and prompt errors, and developers reported API connection and authentication errors. OpenAI acknowledged the problem on its official status page and said engineers were investigating elevated error rates. At the time of reporting the company had not identified the underlying cause, and the sources state that no user data was lost. Service availability fluctuated as engineers worked to restore it, and at the latest update OpenAI was still working toward full recovery.
What happened
What was done
Risks
Primary63 incidents
Rising: 5 vs 2.2 a week
Sorted by rule from the case's fields; not yet read from the sources.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
HarnessTool allow-list · Fail-closed defaults · Stop control
ApplicationHuman approval for high-impact actions · Change review and separation of duties · Least-privilege access for the agent · Production kept apart from test · Activity logs · Adversarial testing before deployment
Infrastructure / targetSimilar incidents
Evidence
No source states: when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off.
Show the full account: 5 items from the primary sources
What happened, in order
Not dated in the sources:
- Disruption began with a sudden increase in user reports.
- Outage tracking platforms recorded thousands of complaints across several regions.
- OpenAI published an incident report on its status page.
- OpenAI focused first on restoring service while continuing to investigate.
- At the latest update, restoration was still in progress.
Show every field, with its source and grade
The AI system
What happened
Impact
LR-2026-0637 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON