outages.live
Live
OpenAIIncident ·

Elevated errors with ChatGPT billing and Ads billing

ResolvedOfficial update
0

OpenAI reports errors with ChatGPT billing, including checkout, and with Ads invoice retrieval. OpenAI monitored the recovery. The incident is resolved and lasted 77 minutes.

State

Resolved

Started

Lasted

1 h 17 min

Worst impact

Notice

Timeline

2 updates
04:1104:3004:4905:0805:27
NoticeUpdate postedTimes in UTC

Monitoring

1 h 17 min 100%

Updates

Times in UTC

As posted by OpenAI

Resolved

All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.

Monitoring

We are monitoring recovery from errors affecting ChatGPT billing, including checkout, and Ads invoice retrieval.

OpenAI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

39

Days with an incident

28

Median duration

1 h 56 min

This incident

33% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 days
median 1 h 56 min
90 days agoToday

Other OpenAI incidents

All incidents

OpenAI·Delayed Costs Data in the Compliance API

OpenAI reports delays in publishing Organization cost data through the Costs API. API and ChatGPT usage are not affected. OpenAI applied a mitigation and monitors the service; delays in cost data are still expected.

Degraded

OpenAI·Sites: Publishing failing

OpenAI reports that publishing on Sites failed for some users. OpenAI identified the problem and applied a fix. The incident is resolved and lasted about 2 hours.

Resolved

OpenAI·Elevated errors affecting the Microsoft 365 connector

The Microsoft 365 connector had elevated errors. New connections could fail and tools did not work as expected. OpenAI reports that this incident is resolved. It lasted about 30 hours.

Resolved

OpenAI·GPT-image-2.5 and 2.6 Sunburst & Flare High error rate

OpenAI reports a high error rate for GPT-image-2.5 Sunburst, 2.5 Flare, 2.6 Sunburst, and 2.6 Flare. OpenAI applied a mitigation and monitored the services. The incident is resolved and lasted 33 minutes.

Resolved

OpenAI·Unable to start new Workspace Agent runs

OpenAI reports that users could not start new Workspace Agent runs. OpenAI marked the incident as resolved. The outage lasted 9 hours and 42 minutes.

Resolved

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=openai
Slack
/feed subscribe https://outages.live/feed.xml?providers=openai

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane