Delayed cost data via Costs API from OpenAI: sources differ on incident status
In one notice, OpenAI reports delays in publishing cost data for organizations through Costs API and a status of Identified; a second notice reports a status of Resolved. Neither the chronological order of the notices nor the current status can be determined from the available information. According to the notice with the Identified status, neither use of the API nor use of ChatGPT is affected.
One notice from OpenAI reports delays in publishing cost data for organizations through Costs API. Compliance API is listed as an affected component with degraded performance. The incident status in this notice is Identified; according to the company, the problem has been identified and work to restore up-to-date data is continuing.
A second notice reports a status of Resolved, full recovery of the affected services and normal operation of Compliance API. The sources therefore differ in the incident status they report; neither their chronological order nor the current status can be determined from the available information. According to the notice with the Identified status, neither use of the API nor use of ChatGPT is affected, and other reporting channels remain available.
Why it matters
Organizations monitoring ongoing spending through Costs API must account for the possibility that the available data may lag behind actual spending. According to the company, the services themselves can still be used, so delayed reporting does not mean that operations or costs have stopped.
What was added since the original report
Verified updates
-
The delay concerns the publication of cost data through Costs API; Compliance API is listed as an affected component.
Relevant practical impact
What this means
For a business
Company dashboards connected to Costs API may provide a delayed view of spending, limiting how up to date the information available for budget monitoring is.
ProcessesCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.