Delayed Costs data in the Compliance API
All impacted services have now fully recovered.
The latest update from OpenAI.
State
Resolved
Started
23 d ago
2026-10-09 17:23 UTC
Lasted
3 days
until 2026-10-12 16:02 UTC
Worst impact
Degraded
Timeline
5 updatesIdentified
4 h 41 min 7%
Monitoring
3 days 93%
Updates
Times in UTCAs posted by OpenAI
All impacted services have now fully recovered.
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.
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.
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.
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.
OpenAI in the last 90 days
Full historyIncidents in 90 days
24
Days with an incident
16
Median duration
1 h 51 min
This incident
38× the median
Other OpenAI incidents
All incidentsOpenAI·Elevated errors with search in Dots, ChatGPT Work, and certain ChatGPT thinking experiences
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
OpenAI·Elevated errors for GPT Image 2 API image edits
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
OpenAI·6.1 Sol Degraded Model Performance
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
OpenAI·Elevated error rates for most hosted Code Reviews and Security Reviews on private GitHub repositories
The issue is now resolved.
OpenAI·Elevated error rates for Ads POST requests
All impacted services have now fully recovered.
Follow OpenAI
Your coding agent knows when OpenAI is down, and tells you when a failure is theirs, not yours. You can also get OpenAI incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "openai" and tell me if OpenAI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=openai/feed subscribe https://outages.cc/feed.xml?providers=openaiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane