← Back to Incident History

OpenAI Reliability

AI research and deployment company behind ChatGPT and the OpenAI API

All regions · provider-wide score

Global and unknown-region reports remain visible. Scores use the selected incident history over the last 90 days.

63D
PoorProvisional

Score Summary

  • Geographic scopeProvider-wide
  • PeriodLast 90 days
  • Recorded incidents in period109
  • Incidents included in score109
  • Categoryai
  • Importancecritical

Data notes · Provisional score

  • Historical incident records need verification against the current source.
  • Some resolved incidents have missing or inconsistent fix-time measurements.

The score uses 109 of 109 recorded incidents with usable timing. Incomplete or conflicting intervals are excluded from the calculation and remain in incident history. These notes are reassessed as the underlying records are repaired.

Score Breakdown

⏱️Uptime
35% weight
Provider-reported incident duration68
Total incident hours: 702

An uptime proxy, not measured availability. Overlapping incidents are added together, including across products and regions.

🚀Resolution Speed
25% weight
How fast issues are resolved78
Avg fix time: 6h 5m

38 of 109 included incidents have measured fix times.

📊Incident Frequency
20% weight
Lower is better0
Included incidents in period: 109

Severity-weighted incident count. Providers cover different numbers of products and regions, so comparisons are approximate.

💬Communication
20% weight
Updates, ack time, workarounds97
Avg updates per incident: 3.2

109 of 109 included incidents have update counts; 109 have acknowledgement times.

📋 View Incident History🔧 All Services
Scores describe collected provider-reported incidents, not independently measured uptime or complete historical coverage. The formula weights are unchanged: uptime proxy 35%, resolution speed 25%, incident frequency 20%, and communication 20%.