Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The incident concerns Costs API exports published November 6–9; those dates describe export publication, not necessarily when the underlying usage or charges occurred.
- The incident is now Resolved, with a recorded end time of November 10, 2026 at 07:02:33 UTC. OpenAI says affected services are operating normally again.
- The notice does not identify affected accounts, plans, countries, data fields or the time zone for the export publication window.
- Editorial advice: retain original and available replacement exports, record each version and retrieval time, and compare matching scopes and complete windows. A status update does not change a previously downloaded file.
What has OpenAI confirmed?
OpenAI has marked the incident Resolved and says affected services are operating normally again. Its recorded end time is November 10, 2026 at 07:02:33 UTC, after the earlier Monitoring update at 04:42:21 UTC. The initial notice identified incorrect cost data in Costs API exports published November 6–9.
This is the official recovery confirmation for the export data incident, not an account-by-account reconciliation result. The notice does not say downloaded files update automatically, provide a per-account correction list or confirm changes to actual charges, invoices or refunds.
What do November 6–9 refer to?
The notice uses those dates for when the affected exports were published. It does not say that the underlying usage, requests or charges occurred during November 6–9, and it does not specify a time zone for the export publication window. A file’s publication date is not automatically its billing period.
The notice does not list affected countries, plans, accounts or cost fields, and it provides no organization-by-organization impact list. The specific account scope remains unknown; a date or plausible total alone cannot identify which rows in your report are wrong.
Keep the original before comparing a replacement
Editorial advice: keep each downloaded export exactly as received. Record its available publication and retrieval times, time zone, organization scope, filters and version identifier. Keep older files published in the stated window marked “awaiting comparison with a replacement.” Do not overwrite them or assume they are corrected solely because the incident is resolved.
For comparisons, use the same organization scope, field definitions and filters, and confirm that both reports cover complete, matching time windows. Export publication time and the period represented by its data are separate dimensions. If either is unknown, record that gap; do not treat a missing row as zero cost.
For example, suppose an export published on November 7 covers November 1–5, while another covers November 1–6. This is a hypothetical illustration: subtracting the totals does not identify the erroneous amount. Align the data periods and filters first, and retain query parameters and sync checkpoints for comparison with a replacement. Keep unclear fields marked as unknown.
How should you check an available replacement now?
Editorial advice: with service recovery confirmed, obtain an available replacement export and preserve it separately from the original. Record its retrieval time and any publication time or version identifier. Compare matching scopes and complete windows, retaining the differences. If it is unclear whether the replacement includes corrections to the relevant historical records, keep those records pending verification rather than assuming every row has been fixed.
If a real invoice or billing amount still differs after review, use your existing authorized OpenAI support channel and provide the relevant evidence. The current notice does not say that actual charges were wrong or describe refunds. It also does not instruct customers to change API keys, models or account settings.
Sources
Frequently Asked Questions
Does Resolved mean my previously downloaded file has been corrected?
You cannot infer that. OpenAI confirmed that affected services are operating normally again, but did not say old files change automatically or provide account-level verification results. Keep the original, obtain an available replacement and compare matching scopes. Leave unclear historical records pending verification.
What if an internal allocation or budget summary already uses these exports?
Editorial advice: mark the derived report for review too, recording its source file, data period and calculation rules. After obtaining an available replacement export and checking the relevant records, recalculate using the same rules and retain both versions. This does not establish any change to actual charges or refunds.