Uptime50%
19.3
OpenAI status & reliability
OpenAI
AI research and deployment company behind ChatGPT and the GPT family of models. Originally a non-profit; restructured into a capped-profit company in 2019. Mission framed as building AGI that benefits all of humanity.
Reliability — last 24h
Composite Score
0.0/100
uptime · freq · sev · mttr
▼ 58.2 vs prior 24h
Uptime
0.00%
critical + 0.3 × major (Statuspage formula)
Incidents
0
top type: elevated errors
Median MTTR
6h 11m
bad day: 6h 11m
Component
Incidents
Down (attr.)
Median MTTR
Last
Frequency20%
84.6
Severity20%
45.7
MTTR10%
61.3
SLA Compliance
How often does this provider clear their stated availability target?
OpenAI Business Terms · 99.90% · source ↗
✕ last 24h92.27%-7.63%
Met SLA in 8 of 13 weeks (62%)
13 weeks on record
Method: a rolling quarter (13 weeks ≈ 91 days). Each cell is one 7-day slice of Statuspage-standard uptime (1 − (critical + 0.3 × major) / window; minors and maintenance excluded; red when the slice dips below the stated SLA).
MinorMajorCritical
Total 1 incidents
Elevated errors
100%
S
0
M
0
T
0
W
Wednesday04:00–05:00 UTC
1incident
1 major
- Elevated error rates on Codex, ChatGPT and Responses APIJun 3
1
T
0
F
0
S
0
00
06
12
18
HOUR OF DAY · UTC1 incident starts · hover any cell for detail
Hottest hour
Wednesday 04:00 1
Worst day
Wednesday 1
Worst time of day
04:00–05:00 1
Typical fix
6h 11m
half of incidents resolve faster
On a bad day
6h 11m
9 in 10 resolve faster than this
Distribution
<15m
0
15m–1h
0
1–4h
0
4–24h
1
24h+
0
+0 ongoing (not counted above)
MTTR Trend (12 weeks)
Are they recovering faster or slower over time? Lower is better.
159m worstnow 100m
12 weeks agodelta +100m (worse)now
Showing 8 of 131 · 4 of 75 daysLatest first
WED, JUN 32026-06-031 incident
TUE, JUN 22026-06-023 incidents
MON, JUN 12026-06-011 incident
FRI, MAY 292026-05-293 incidents