Incident report · read from OpenAI's status page

OpenAI incident: Delayed Costs data in the Compliance API

Resolved after 1 d 17 h (14 Oct 2026 17:00 – 16 Oct 2026 10:44 UTC), impact minor, affecting Compliance API.

Timeline

1. 14 Oct 2026 at 17:00 UTC 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. 14 Oct 2026 at 17:02 UTC 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.

3. 14 Oct 2026 at 20:00 UTC identified

   We have identified an issue causing delays in publishing organization cost data through the Costs API. A fix is in progress and currently undergoing testing. API and ChatGPT usage are not affected, and other reporting channels remain available. We are continuing work to restore normal data freshness.

4. 15 Oct 2026 at 22:36 UTC monitoring

   We have deployed a fix and are monitoring recovery. Costs data in the Compliance API remains delayed while we process the backlog. We will provide further updates as processing catches up.

5. 16 Oct 2026 at 10:44 UTC resolved

   All impacted services have now fully recovered.

Affected components

• ChatGPT · Compliance API: degraded for 1 d 17 h

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 30 Oct 2026 at 16:27 UTC.

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.