OpenAI

Founded: 2015
HQ: San Francisco, CA

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.

openai.com ↗status.openai.com ↗

Products

ChatGPT · GPT models · Sora · DALL·E · Codex · Whisper · OpenAI API

Reliability — last 7d

Composite score

69.9/100

uptime · freq · sev · mttr

Uptime

95.25%

severity- and component-weighted

Incidents

top type: elevated errors

Median MTTR

1h 1m

bad day: 36h 1m

What's breaking (last 7d)

Components ranked by incident count. Click a row for the incident list. Down-time is attributed proportionally for multi-component incidents.

Component	Incidents	Down (attr.)	Median MTTR	Last
Unspecified	2	36h 21m	18h 11m	4d ago
FedRAMP	1	22m	22m	3d ago
Responses	1	1h 40m	1h 40m	2d ago

Type of failure

Categorised from the public incident headlines (outage / latency / auth / etc.). Click a category to drill in.

When it breaks

Incident starts by weekday × hour, UTC. Hover a cell for incident detail.

0006121823

Hour of day · UTC

OpenAI — incidents by day (last 7d)

MinorMajorCritical

Total 4 incidents

2d incident-free streak

Worst incidents

Ranked by severity-weighted duration (impact × wall-clock).

#1Elevated 401 errors for API endpointsminor
6d agoduration: 36h 1mtype: Elevated errors
#2ChatGPT FedRAMP workspaces not loadingcritical
3d agoduration: 22mtype: Degradedaffects 1 component
#3Responses API Streaming Errorminor
2d agoduration: 1h 40mtype: Elevated errorsaffects 1 component
#4Account Creation Issuesminor

Score breakdown

Uptime50%

52.5

Frequency20%

90.5

Severity20%

77.9

MTTR10%

99.5

SLA compliance

How often does this provider clear their stated availability target?

OpenAI Business Terms · 99.90% · source ↗

Met SLA in 2 of 13 weeks (15%)

✗ last 7d95.25%-4.65%

Incident history

showing 4 of 80 · 4 of 49 days

Thu, Apr 162026-04-161 incident

Wed, Apr 152026-04-151 incident

Tue, Apr 142026-04-141 incident

Sun, Apr 122026-04-121 incident