Incident report · read from OpenAI's status page

OpenAI incident: Delayed Costs data in the Compliance API

Resolved after 2 d 22 h (9 Oct 2026 17:23 – 12 Oct 2026 16:02 UTC), impact minor, affecting Compliance API.

Timeline

  1. identified

    We have identified an issue causing delays in publishing organization cost data through the Costs API. API and ChatGPT usage are not affected, and other reporting channels remain available. We are working to restore normal data freshness.

  2. identified

    We have identified an issue causing delays in publishing Costs data through the Compliance API. The API Platform organization costs endpoint and ChatGPT usage are not affected, and other reporting channels remain available. We are working to restore normal data freshness.

  3. identified

    Some customers may continue to experience delayed Costs data through the Compliance API. ChatGPT usage and API Platform requests are not affected, and other reporting channels remain available. We have identified the cause and are continuing work to restore normal data freshness. We will provide another update as work progresses.

  4. monitoring

    We have implemented a mitigation, and delayed Costs data is now processing through the Compliance API. Some customers may continue to see incomplete Costs data while the backlog catches up. We expect this catch-up process to continue through Sunday, October 11. ChatGPT usage and API Platform requests remain unaffected. We are monitoring recovery.

  5. resolved

    All impacted services have now fully recovered.

Affected components

What the crowd did

That is this site's own record of the crowd at OpenAI's gate, not anything OpenAI published.

Source

OpenAI's own report of this incident, on OpenAI's status page. This page is a record of OpenAI's own report; where the two disagree, theirs is right.

Last checked .

Must Have AI is a parody and is not affiliated with, endorsed by or connected to OpenAI, Anthropic or Google. Every outage shown here is read from the provider's own public status page.