🟢 Operational
Overbilling for OpenAI-hosted containers in the Agent API
Resolved
- Started
- 2026-09-18 22:29 UTC
3 days ago - Last update
- 2026-09-19 07:52 UTC
2 days ago - Duration
- 9h 22m
Timeline
-
19 Sep · 07:52 UTC
🟢 Resolved
atom
Status: Resolved
All impacted services have now fully recovered. -
19 Sep · 05:00 UTC
🟡 Monitoring
atom
Status: Monitoring
We have applied the mitigation, and any new sessions would not run into this issue. We are monitoring the recovery. -
19 Sep · 01:08 UTC
⚪ Identified
atom
Status: Identified
We are still implementing the mitigation. -
18 Sep · 23:22 UTC
🟡 Investigating
atom
Status: Investigating
We’re continuing to work on a fix for the container overbilling issue.
We’re also reviewing affected usage to identify impacted customers and calculate refunds. -
18 Sep · 22:29 UTC
🟡 Investigating
atom
Status: Investigating
We’re investigating an issue causing higher-than-expected charges for OpenAI-hosted containers in the Agent API.
We’re working on a fix and preparing refunds for affected customers. We’ll share further updates as we make progress.
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.