ChatGPT Outage History
Every incident OpenAI has published for ChatGPT recently, newest first, with how long each one lasted.
Showing 24 published incidents back to 9 Oct 2026.
- Minor3 Nov 20264h 53m
File upload errors in ChatGPT
- Minor30 Oct 20261h 35m
Elevated errors with search in Dots, ChatGPT Work, and certain ChatGPT thinking experiences
- Minor30 Oct 20264h 1m
Elevated errors for GPT Image 2 API image edits
- Minor27 Oct 20261h 18m
6.1 Sol Degraded Model Performance
- Informational27 Oct 202629 min
Elevated error rates for most hosted Code Reviews and Security Reviews on private GitHub repositories
- Minor26 Oct 202611 min
Elevated error rates for Ads POST requests
- Minor23 Oct 202650 min
Degraded experience with ChatGPT app connections using CIMD
- Informational23 Oct 202633 min
Help Center Chat Support Degraded
- Informational23 Oct 20262h 17m
Delays in customer support responses
- Minor22 Oct 20264h 31m
New Ad Accounts failing to provision admins
- Minor22 Oct 20262h 4m
Degraded Performance of Dots on Enterprise
- Minor22 Oct 20266h 32m
Elevated ChatGPT conversation and Responses API errors
- Minor21 Oct 20261h 9m
Elevated error rates for gpt-5.6-luna API requests
- Minor21 Oct 20265h 17m
Elevated FedRAMP API error rates for Astra and Sol
- Minor21 Oct 20261h 2m
Degraded performance in ChatGPT, Codex, and APIs
- Minor19 Oct 202642 min
File Download errors
- Major15 Oct 20262h 27m
Widespread feature degradation
- Minor14 Oct 20261d 17h
Delayed Costs data in the Compliance API
- Minor14 Oct 202640 min
Limited availability on gpt-image-2.5-flare and gpt-image-2.5-sunburst
- Minor14 Oct 20262h 47m
Degraded performance in Codex and ChatGPT Work
- Minor13 Oct 20268h 27m
Degraded performance in GPT-6.1 Sol Codex and Work mode
- Major9 Oct 20261h 38m
Workspace admins may be unable to manage plugins
- Major9 Oct 20263h 26m
Some ChatGPT content may be unavailable on Android
- Minor9 Oct 20262d 22h
Delayed Costs data in the Compliance API
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