Costs API data is delayed
minor- Started
- Nov 17, 12:46 PM EST
- Resolved
- Nov 18, 12:15 PM EST
- Duration
- 23h 30m
OpenAI's updates (4)
- investigating · Nov 17, 12:46 PM EST
We have identified a delay in our Costs API. We are working to resolve the issue.
- investigating · Nov 17, 1:41 PM EST
We have identified the issue, it was due to an internal account, that jumped from 100 groups to 400+ groups, breaking rockset's ingestion. We have identified a simple fix for this and waiting for it to deploy, we will rerun the jobs for these hours, and expect to start catching up in 2 hours, And expect to fully recover in 8 hours.
- monitoring · Nov 17, 2:53 PM EST
We've pushed a fix and are monitoring the recovery.
- resolved · Nov 18, 12:15 PM EST
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
What our checks recorded
We checked ChatGPT 282 times from OpenAI's start time to its resolution, once every five minutes. Every one of them reached ChatGPT's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 499 ms, against 536 ms over the 24 hours before. OpenAI posted the incident at Nov 17, 12:46 PM EST.
Updates are OpenAI's own words from its status page (status: resolved); we never add an inferred cause.