Skip to content
context Other verified update

OpenAI has deployed a fix for the Costs API data delay, recovery monitoring underway

clearly official source updated November 17, 2026

OpenAI has deployed a fix for the data delay in the Costs API and is monitoring recovery; according to the status page, the Compliance API still has degraded performance. Regular API usage and ChatGPT are not affected by the incident.

OpenAI is addressing an incident in which the publishing of data in the Costs API was delayed, while the Compliance API showed degraded performance. According to the company's status page, a fix has been deployed and recovery of operations is now being monitored.

The incident follows a previously reported issue with delayed cost data in the Compliance API, which was in the meantime announced as resolved — at that time all affected services returned to normal operation. The current update shows that the data delay issue has recurred, now specifically affecting the Costs API.

According to OpenAI, regular use of the API and the ChatGPT product is not affected by the incident — the impact concerns exclusively the data displayed via the Compliance API and the Costs API.

What changed

Why it matters

This concerns primarily companies that track organizational usage and costs via the Compliance API or Costs API — during the incident, the displayed data may have been outdated. According to OpenAI, regular use of ChatGPT and the API is not affected, so the incident has no practical impact for individual users.

What was added since the original report

Verified updates

  1. New verified information

    The Costs API was affected by a data delay incident; A fix has been deployed and is rolling out into production; Active monitoring of the incident recovery is underway; The scope of the incident is expanding to the Costs API, compared to the original focus on the Compliance API

    • The Costs API was affected by a data delay incident
    • A fix has been deployed and is rolling out into production
    • Active monitoring of the incident recovery is underway
    • The scope of the incident is expanding to the Costs API, compared to the original focus on the Compliance API

Relevant practical impact

What this means

01

For a business

Companies that track organizational costs and usage via the Compliance API or Costs API may have temporarily seen outdated data; OpenAI deployed a fix and is monitoring recovery, and the ChatGPT incident did not affect regular usage of the API.

Risks and compliance
What to decide If a company uses OpenAI's Costs API or Compliance API to track costs, verify that the displayed data is up to date after recovery is complete.
More business impacts →
API Compliance API Costs API incident OpenAI data delay

Check the original

Event sources

clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.

2
OpenAI Status — incident history official service status · first detected Delayed Costs Data in the Compliance API OpenAI Status — incident history official service status Costs API data is delayed