OpenAI uptime
From vendor reports Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.
97.08%free of major or critical incidents, last 30 days
98.59%free of major or critical incidents, last 90 days
76.44%free of any incident, last 90 days
83incidents started, last 90 days
Last 90 days, by UTC day
Aug 7 (UTC day): no vendor-reported incident openAug 8 (UTC day): no vendor-reported incident openAug 9 (UTC day): no vendor-reported incident openAug 10 (UTC day): 0 min with a major or critical incident open, 10 h 43 min with any incident open, 2 incidents startedAug 11 (UTC day): 0 min with a major or critical incident open, 4 h 59 min with any incident open, 3 incidents startedAug 12 (UTC day): no vendor-reported incident openAug 13 (UTC day): 0 min with a major or critical incident open, 8 h 39 min with any incident open, 1 incident startedAug 14 (UTC day): no vendor-reported incident openAug 15 (UTC day): no vendor-reported incident openAug 16 (UTC day): no vendor-reported incident openAug 17 (UTC day): no vendor-reported incident openAug 18 (UTC day): 0 min with a major or critical incident open, 20 min with any incident open, 1 incident startedAug 19 (UTC day): no vendor-reported incident openAug 20 (UTC day): 0 min with a major or critical incident open, 4 h 8 min with any incident open, 3 incidents startedAug 21 (UTC day): 0 min with a major or critical incident open, 5 h 18 min with any incident open, 1 incident startedAug 22 (UTC day): no vendor-reported incident openAug 23 (UTC day): no vendor-reported incident openAug 24 (UTC day): no vendor-reported incident openAug 25 (UTC day): no vendor-reported incident openAug 26 (UTC day): no vendor-reported incident openAug 27 (UTC day): 0 min with a major or critical incident open, 4 h 14 min with any incident open, 1 incident startedAug 28 (UTC day): no vendor-reported incident openAug 29 (UTC day): no vendor-reported incident openAug 30 (UTC day): no vendor-reported incident openAug 31 (UTC day): 5 h 24 min with a major or critical incident open, 6 h 56 min with any incident open, 2 incidents startedSep 1 (UTC day): 0 min with a major or critical incident open, 19 h 6 min with any incident open, 1 incident startedSep 2 (UTC day): no vendor-reported incident openSep 3 (UTC day): 6 min with a major or critical incident open, 2 h 4 min with any incident open, 2 incidents startedSep 4 (UTC day): 0 min with a major or critical incident open, 3 h 46 min with any incident open, 1 incident startedSep 5 (UTC day): no vendor-reported incident openSep 6 (UTC day): no vendor-reported incident openSep 7 (UTC day): no vendor-reported incident openSep 8 (UTC day): 0 min with a major or critical incident open, 7 h 27 min with any incident open, 2 incidents startedSep 9 (UTC day): 0 min with a major or critical incident open, 1 h 9 min with any incident open, 1 incident startedSep 10 (UTC day): 0 min with a major or critical incident open, 13 h 47 min with any incident open, 2 incidents startedSep 11 (UTC day): 0 min with a major or critical incident open, 11 h 6 min with any incident open, 3 incidents startedSep 12 (UTC day): 0 min with a major or critical incident open, 1 h 58 min with any incident openSep 13 (UTC day): 0 min with a major or critical incident open, 2 h 18 min with any incident open, 2 incidents startedSep 14 (UTC day): 0 min with a major or critical incident open, 16 h 52 min with any incident open, 1 incident startedSep 15 (UTC day): 9 min with a major or critical incident open, 13 h 3 min with any incident open, 3 incidents startedSep 16 (UTC day): 31 min with a major or critical incident open, 1 h 21 min with any incident open, 1 incident startedSep 17 (UTC day): 1 h 21 min with a major or critical incident open, 2 h 47 min with any incident open, 2 incidents startedSep 18 (UTC day): no vendor-reported incident openSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): no vendor-reported incident openSep 21 (UTC day): no vendor-reported incident openSep 22 (UTC day): 0 min with a major or critical incident open, 1 h 34 min with any incident open, 2 incidents startedSep 23 (UTC day): 0 min with a major or critical incident open, 1 h 5 min with any incident open, 2 incidents startedSep 24 (UTC day): no vendor-reported incident openSep 25 (UTC day): 56 min with a major or critical incident open, 56 min with any incident open, 1 incident startedSep 26 (UTC day): no vendor-reported incident openSep 27 (UTC day): no vendor-reported incident openSep 28 (UTC day): no vendor-reported incident openSep 29 (UTC day): 0 min with a major or critical incident open, 6 h 7 min with any incident open, 1 incident startedSep 30 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 3 incidents startedOct 1 (UTC day): 53 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 2 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 3 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 4 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 5 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 3 incidents startedOct 6 (UTC day): 0 min with a major or critical incident open, 20 h 1 min with any incident open, 5 incidents startedOct 7 (UTC day): 6 h 22 min with a major or critical incident open, 10 h 19 min with any incident open, 5 incidents startedOct 8 (UTC day): 0 min with a major or critical incident open, 1 h 37 min with any incident open, 1 incident startedOct 9 (UTC day): 2 h 59 min with a major or critical incident open, 6 h 37 min with any incident open, 3 incidents startedOct 10 (UTC day): 27 min with a major or critical incident open, 24 h with any incident openOct 11 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 12 (UTC day): 0 min with a major or critical incident open, 16 h 3 min with any incident openOct 13 (UTC day): 0 min with a major or critical incident open, 8 h 18 min with any incident open, 1 incident startedOct 14 (UTC day): 0 min with a major or critical incident open, 10 h 25 min with any incident open, 3 incidents startedOct 15 (UTC day): 4 h 26 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 16 (UTC day): 0 min with a major or critical incident open, 10 h 45 min with any incident openOct 17 (UTC day): no vendor-reported incident openOct 18 (UTC day): no vendor-reported incident openOct 19 (UTC day): 0 min with a major or critical incident open, 42 min with any incident open, 1 incident startedOct 20 (UTC day): 1 h with a major or critical incident open, 1 h with any incident open, 1 incident startedOct 21 (UTC day): 5 h 44 min with a major or critical incident open, 6 h 45 min with any incident open, 3 incidents startedOct 22 (UTC day): 0 min with a major or critical incident open, 11 h 41 min with any incident open, 3 incidents startedOct 23 (UTC day): 0 min with a major or critical incident open, 58 min with any incident open, 1 incident startedOct 24 (UTC day): no vendor-reported incident openOct 25 (UTC day): no vendor-reported incident openOct 26 (UTC day): 0 min with a major or critical incident open, 11 min with any incident open, 1 incident startedOct 27 (UTC day): 0 min with a major or critical incident open, 1 h 18 min with any incident open, 1 incident startedOct 28 (UTC day): 0 min with a major or critical incident open, 20 h 20 min with any incident open, 1 incident startedOct 29 (UTC day): 0 min with a major or critical incident open, 3 h 40 min with any incident openOct 30 (UTC day): 0 min with a major or critical incident open, 5 h 37 min with any incident open, 2 incidents startedOct 31 (UTC day): no vendor-reported incident openNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): no vendor-reported incident openNov 3 (UTC day): 0 min with a major or critical incident open, 4 h 53 min with any incident open, 1 incident startedNov 4 (UTC day): no vendor-reported incident open
Aug 7today
no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive
Last 7 days, by hour
now
Numbers
| Window | Free of major/critical | Free of any incident | Outage time | Incident time | Incidents |
|---|---|---|---|---|---|
| Last 30 days | 97.08% | 67.06% | 20 h 58 min | 9.9 days | 37 |
| Last 90 days | 98.59% | 76.44% | 30 h 18 min | 21.2 days | 83 |
This is what OpenAI itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .
See the incidents: OpenAI status history · last 90 days · OpenAI status page (opens in new tab) · Markdown