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

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the OpenAI status & history page.

Related: OpenAI status & history. SquidGrid is not affiliated with OpenAI.