Live / OpenAI / Incident
OpenAI: Delayed Costs Data in the Compliance API
OpenAI · openai.comMinor incidentResolved2026-11-16 00:17 UTC
Public — what happened
Summary
OpenAI said that cost information for organizations was being published late through its Costs API, a problem it listed under the Compliance API and rated as minor. The company said it identified the issue at 16:10 UTC on 2026-11-13 and stated that regular API use and ChatGPT were not affected. By 18:56 UTC it said it had put a mitigation in place and was watching to confirm recovery. As of its latest update at 05:31 UTC on 2026-11-14, OpenAI said delays in cost data were still expected and the incident was not yet marked resolved.
Timeline
- Started — 2026-11-13 16:10 UTC
- Identified — 2026-11-13 16:10 UTC
- Monitoring — 2026-11-13 18:56 UTC (2 updates)
- Resolved — 2026-11-16 00:17 UTC · 2 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach OpenAI against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for OpenAI: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the OpenAI report →
More from OpenAI
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.