🟢 Operational
Delayed Costs data in the Compliance API
Resolved
- Started
- 2026-10-09 17:27 UTC
28 days ago - Last update
- 2026-10-12 16:02 UTC
25 days ago - Duration
- 2d 22h
Timeline
-
12 Oct · 16:02 UTC
🟢 Resolved
atom
Status: Resolved
All impacted services have now fully recovered.
Affected components
Compliance API (Operational) -
09 Oct · 22:03 UTC
⚪ Monitoring
atom
Status: 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.
Affected components
Compliance API (Degraded performance) -
09 Oct · 18:46 UTC
🟡 Identified
atom
Status: 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.
Affected components
Compliance API (Degraded performance) -
09 Oct · 17:27 UTC
🟡 Identified
atom
Status: 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.
Affected components
Compliance API (Degraded performance)
Source
Official OpenAI status — view original incident ↗
IT Status normalizes vendor wording into a common vocabulary and rewrites machine-shaped titles for readability. The vendor's page remains authoritative.