Checked 4 minutes ago
2 separate problems in the last 48 hours, most recently 42 hours ago.
This longer record is here so the 48-hour picture above can mean something — without it we could tell you a problem happened, but not whether that is normal for OpenAI.
Something was impaired on 15.89% of our checks over that window. That is how often OpenAI was reporting a problem somewhere, which is not the same as how often it was unreachable. The longest outage we have on record ran 45h 25m.
The last 30 days of OpenAI, one row each.
| Day | Clear | Up | Checks | Started | Longest ended |
|---|---|---|---|---|---|
| 2026-11-01 so far today | 100% | 100% | 158 | none | — |
| 2026-10-31 | 100% | 100% | 287 | none | — |
| 2026-10-30 | 76.31% | 100% | 287 | 2 | 4h 5m |
| 2026-10-29 | 100% | 100% | 287 | none | — |
| 2026-10-28 | 98.26% | 100% | 287 | 1 | 26 min |
| 2026-10-27 | 94.77% | 100% | 287 | 1 | 1h 18m |
| 2026-10-26 | 99.3% | 100% | 287 | 1 | 12 min |
| 2026-10-25 | 100% | 100% | 287 | none | — |
| 2026-10-24 | 100% | 100% | 287 | none | — |
| 2026-10-23 | 96.17% | 100% | 287 | 1 | 5h 19m |
| 2026-10-22 | 51.4% | 100% | 286 | 2 | 6h 32m |
| 2026-10-21 | 76.66% | 97.91% | 287 | 2 | 5h 18m |
| 2026-10-20 | 100% | 100% | 287 | none | — |
| 2026-10-19 | 97.21% | 100% | 287 | 1 | 44 min |
| 2026-10-18 | 100% | 100% | 287 | none | — |
| 2026-10-17 | 100% | 100% | 288 | none | — |
| 2026-10-16 | 55.75% | 100% | 287 | none | 41h 39m |
| 2026-10-15 | 61.32% | 100% | 287 | 1 | 15h 0m |
| 2026-10-14 | 56.45% | 100% | 287 | 3 | 2h 50m |
| 2026-10-13 | 66.19% | 100% | 281 | 1 | 8h 31m |
| 2026-10-12 | 100% | 100% | 287 | none | — |
| 2026-10-11 | 100% | 100% | 287 | none | — |
| 2026-10-10 | 58.19% | 98.26% | 287 | none | 16h 42m |
| 2026-10-09 | 72.47% | 87.8% | 287 | 1 | — |
| 2026-10-08 | 93.38% | 100% | 287 | 1 | 1h 37m |
| 2026-10-07 | 57.14% | 73.52% | 287 | 3 | 6h 23m |
| 2026-10-06 | 70.73% | 100% | 287 | 4 | 17h 1m |
| 2026-10-05 | 29.27% | 100% | 287 | 1 | — |
| 2026-10-04 | 100% | 100% | 287 | none | — |
| 2026-10-03 | 100% | 100% | 287 | none | — |
Clear is the share of checks that found nothing wrong at all; Up is the share that found OpenAI actually reachable — a vendor reporting one impaired component scores zero on the first and a hundred on the second, and both are true. Started counts outages that began that day and Longest ended the longest that finished on it, so a problem running across midnight is counted once, on the day it began, and measured on the day it stopped.
Rows recorded before 8 August 2026 do not carry a check count — the figure was kept and the denominator was not — so their percentages are shown without one rather than with a number borrowed from somewhere else. Rows before 9 August 2026 have no Up figure either: until then we recorded only whether something was wrong, not whether it was down, and the two are different questions.
| Started | Lasted | Severity | What happened |
|---|---|---|---|
| 2026-10-30 19:38 UTC | 1h 37m | having problems | Elevated errors with search in Dots, ChatGPT Work, and certain ChatGPT thinking experiences |
| 2026-10-30 14:35 UTC | 4h 5m | having problems | Elevated errors for GPT Image 2 API image edits |
| 2026-10-28 03:39 UTC | 26 min | having problems | Degraded Performace on ChatGPT Work |
| 2026-10-27 15:02 UTC | 1h 18m | having problems | 6.1 Sol Degraded Model Performance |
| 2026-10-26 18:19 UTC | 12 min | having problems | Ads POST /ads/* endpoints elevated error rates |
| 2026-10-23 22:52 UTC | 53 min | having problems | Degraded experience with ChatGPT app connections using CIMD |
| 2026-10-22 18:51 UTC | 5h 19m | having problems | Dot Message Failures |
| 2026-10-22 02:18 UTC | 6h 32m | having problems | ChatGPT conversion failures in India, Japan and Korea. And Response API errors |
| 2026-10-21 14:17 UTC | 5h 18m | partly down | Elevated FedRAMP API error rates for Astra and Sol |
| 2026-10-21 02:26 UTC | 24 min | having problems | Degraded performance in ChatGPT, Codex, and APIs |
| 2026-10-19 13:31 UTC | 44 min | having problems | File Download errors |
| 2026-10-14 17:00 UTC | 41h 39m | having problems | Delayed Costs data in the Compliance API |
| 2026-10-14 17:00 UTC | 15h 0m | having problems | Delayed Costs data in the Compliance API |
| 2026-10-14 10:18 UTC | 43 min | having problems | Limited availability on gpt-image-2.5-flare and gpt-image-2.5-sunburst |
| 2026-10-14 07:05 UTC | 2h 50m | having problems | Degraded performance in Codex and ChatGPT Work |
| 2026-10-13 08:10 UTC | 8h 31m | having problems | Degraded performance in GPT-6.1 Sol Work mode |
| 2026-10-09 17:23 UTC | 16h 42m | partly down | Delayed data in the Costs API |
| 2026-10-08 03:17 UTC | 1h 37m | having problems | Some APAC users are seeing errors in ChatGPT Work, conversations, and GPTs. |
| 2026-10-07 23:42 UTC | 23 min | having problems | Elevated errors with GPT-5.6 Instant in FedRAMP workspaces |
| 2026-10-07 16:31 UTC | 1h 54m | having problems | Dot in Codex may fail to create new threads |
Status pages report the vendor's view of their own service, and they lag real
outages — often by many minutes, sometimes by hours, because a human usually has to
confirm before anything is posted. They also can't see the two things most likely to
be wrong at your end.
The first is your own connection under load. A line that idles at 20 ms can
jump to 300 ms the moment something starts uploading, which drops you from sessions
and looks exactly like a server fault. Your plan speed says nothing about this; it's
called bufferbloat and almost nobody measures it.
The second is where everyone else in your group is. A service can be healthy in your
region and unwell in theirs, and if one person is hosting, their problem is everyone's
problem.
OpenAI being fine where you are does not mean it is fine for everyone in your group. The live dashboard resolves status against each person's own region, and will tell you which of your friends is in an affected area — plus who has the connection to host, which is usually a different question from who has the fastest plan.
Worth a look when more than one thing feels broken at once: if several are genuinely down together, the fault is usually something they share rather than anything at your end. We are not claiming these particular services fail together — the live dashboard says when they actually do.