ChatGPT Outage History
Every incident OpenAI has published for ChatGPT recently, newest first, with how long each one lasted.
Showing 25 published incidents back to 25 Sep 2026.
- Minor9 Oct 2026ongoing
Delayed Costs data in the Compliance API
- Minor8 Oct 20261h 34m
Some APAC users are seeing errors in ChatGPT Work, conversations, and GPTs.
- Minor7 Oct 202621 min
Elevated errors with GPT-5.6 Instant in FedRAMP workspaces
- Minor7 Oct 20261h 2m
Degraded performance in Codex and Work mode: Dot turn failures, delayed responses, and reduced proactivity
- Minor7 Oct 20261h 35m
Dot in Codex may fail to create new threads
- Major7 Oct 20266h 22m
Unable to create new ChatGPT Work threads in latest version of desktop app
- Minor7 Oct 20261h 48m
Workspace Agents Degraded and Responses Impacted
- Minor6 Oct 20262h 45m
Computer Use Is Experiencing Issues
- Minor6 Oct 20262h 4m
Errors processing large PDFs in the Responses API
- Minor6 Oct 20261h 5m
Elevated error rates in ChatGPT Go conversations
- Minor6 Oct 202636 min
Elevated errors affecting multiple products including ChatGPT (conversations), Image generations, Spaces and Pages, API rehydration, and Dot
- Minor6 Oct 202655 min
Elevated errors in API Platform login and administration APIs.
- Informational5 Oct 20266h 3m
Elevated error rates in Codex Cloud
- Minor5 Oct 20267h 2m
Elevated errors in ChatGPT conversations
- Informational5 Oct 20265h 17m
Admin Console Intermittently Inaccessible
- Minor5 Oct 202620 min
Issues saving and editing Pages
- Minor5 Oct 202619h 6m
Elevated Work Mode errors
- Minor2 Oct 202648 min
Issues with data analysis and file creation in ChatGPT
- Major1 Oct 202653 min
Issues with login, signup, and ads
- Minor30 Sep 20263h 30m
Elevated latency for some API requests
- Minor30 Sep 20267h 36m
Elevated error rates for ChatGPT Pro and Plus users
- Minor30 Sep 20261d 21h
Elevated errors in ChatGPT Space Pages
- Minor29 Sep 20265h 21m
Elevated errors across ChatGPT, Codex, and the API including the Agents API
- Informational29 Sep 20265h 30m
Support available via email
- Critical25 Sep 202656 min
Issues with Codex
What this record shows
OpenAI reports openly and often. It posts short notices for problems many companies would never mention publicly, which is why this list is longer than you might expect for a service that is available well over 99% of the time. Most entries below are minor: a few minutes to a couple of hours, affecting some users rather than all.
That reporting habit is exactly why counting incidents is a poor measure of reliability. What matters is how much time was lost, not how many notices were posted — so read the durations rather than the row count. A month with ten brief minor incidents is a better month than one with a single four-hour outage.
One limitation to note: OpenAI does not tag its incidents by component, so this is OpenAI’s published record rather than a ChatGPT-only list. Some entries will have affected the API, Sora or another surface rather than ChatGPT itself — the titles usually say which. It is also why there is no separate Sora history page: the feed cannot distinguish one.
How to read the durations
Each entry runs from when OpenAI opened the incident to when it was marked resolved. That is a generous measure: an incident is usually opened once the problem is confirmed and closed after it has been stable for a while, so the window is wider than the period in which most people were actually affected.
Severity comes from the provider. Only major and critical entries count against the uptime figure on the ChatGPT status page, because a minor incident normally means degraded performance for some users rather than the service being unavailable.
This list is limited to what the provider has published and still exposes. Providers cap how far their public feed reaches, so an empty stretch further back means the record has aged out, not that nothing happened.
🔗 Keep checking