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.
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).
OpenAI — Incidents by Day last 7d
MinorMajorCritical
Total 10 incidents
0
1
1
2
2
07-1407-1507-1607-1707-1807-1907-2007-21
Worst Incidents
Ranked by severity-weighted duration (impact × wall-clock). Click any incident for the full update timeline.
Type of Failure
Categorised from the public incident headlines (outage / latency / auth / etc.).
Elevated errors
4
36%
Degraded
2
18%
Other
2
18%
Outage
1
9%
Auth & login
1
9%
Integrations
1
9%
When It Breaks
Incident starts by weekday × hour, UTC. Hover a cell for incident detail.
S
Sunday14:00–15:00 UTC
1incident
1 major
Elevated errors affecting ChatGPTJul 19
1
M
Monday00:00–01:00 UTC
1incident
1 minor
Elevated errors for GitHub-dependent ChatGPT and Codex workflowsJul 20
1
T
Tuesday10:00–11:00 UTC
1incident
1 minor
Image generation unavailable for some ChatGPT usersJul 21
Tuesday15:00–16:00 UTC
1incident
1 minor
Some ChatGPT Go users may experience conversation failures when using GPT-5.5.Jul 14
Tuesday23:00–00:00 UTC
1incident
1 major
Elevated errors affecting ChatGPTJul 14
3
W
Wednesday00:00–01:00 UTC
1incident
1 critical
Issue affecting voice mode in ChatGPTJul 15
1
T
Thursday08:00–09:00 UTC
1incident
1 minor
Elevated Error Rates For SSO LoginJul 16
Thursday22:00–23:00 UTC
1incident
1 minor
Elevated errors for Github connectorJul 16
2
F
Friday15:00–16:00 UTC
1incident
1 major
New ChatGPT App Not Available For Enterprise Users Without Codex PermissionsJul 17
1
S
Saturday08:00–09:00 UTC
1incident
1 minor
Some users are unable to access CodexJul 18
1
00
06
12
18
HOUR OF DAY · UTC10 incident starts · hover any cell for detail
Hottest hour
Sunday 14:00 1
Worst day
Tuesday 3
Worst time of day
00:00–01:00 2
How fast they fix things
Distribution of resolution times alongside the 12-week trend so you can see whether they're getting faster or slower.
Typical fix
2h 15m
half of incidents resolve faster
On a bad day
6h 46m
9 in 10 resolve faster than this
Distribution
<15m
1
15m–1h
2
1–4h
4
4–24h
3
24h+
0
+1 ongoing (not counted above)
MTTR Trend (12 weeks)
Are they recovering faster or slower over time? Lower is better.