In this article
OpenAI delays Organization cost data in the Costs API
OpenAI identified an issue that delayed publishing of Organization cost data through the Costs API, according to its status page. According to OpenAI's status page, the incident is titled "Delayed Costs Data in the Compliance API", while the body text refers to the Costs API. OpenAI has since marked it resolved.
Only cost data freshness was hit, not API or ChatGPT usage
OpenAI says API and ChatGPT usage were not affected. The only thing hit was how fresh the Organization cost data was. OpenAI has not said how many organizations were affected or how long the delay lasted.
From identification to resolution on OpenAI's status page
OpenAI posted three updates, in this order:
- Identified: OpenAI found the issue behind the delayed cost data and said it was working to restore normal data freshness.
- Monitoring: OpenAI applied a mitigation and watched the affected services to confirm recovery, while saying delays in cost data were still expected.
- Resolved: OpenAI states all affected services are operating normally again. The status page text we have gives no timestamps for these steps. OpenAI apologised for the disruption and thanked users for their patience.
OpenAI has not named a cause
OpenAI has not stated a root cause, and no workaround was published. The status page also does not explain why the title says Compliance API while the body says Costs API.
Check your cost figures for the affected window
If you pull Organization cost data from the Costs API, compare recent figures against what you expect before relying on them. OpenAI reports the affected services are operating normally again, but it did not say when the delay began or ended, so you cannot tell from the status page which period was late. Watch the OpenAI status page for any follow-up on the cause.
Sources
Image: Photo by Brecht Corbeel on Unsplash
This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].


Discussion