Elevated error rates for gpt-6 Luna API requests
OpenAI gpt-6 Luna API requests had elevated error rates. The incident started on 19 November 2026 at 16:01 UTC. OpenAI reports that the incident is resolved and lasted 57 minutes.
State
Resolved
Started
Lasted
57 min
Worst impact
Partial outage
Timeline
3 updatesInvestigating
23 min 41%
Monitoring
34 min 59%
Updates
Times in UTCAs posted by OpenAI
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
We’ve applied a mitigation and are monitoring the affected services to confirm recovery.
We’re investigating a potential issue for the listed services and checking how it affects users. We’ll share an update when we know more.
OpenAI in the last 90 days
Full historyIncidents in 90 days
42
Days with an incident
33
Median duration
1 h 58 min
This incident
52% shorter than the median
Other OpenAI incidents
All incidentsOpenAI·Elevated conversation errors for Free and Go users
OpenAI reported elevated conversation errors that affected Free and Go users. OpenAI later said all affected services operate normally again. The incident is resolved and lasted 1 hour and 59 minutes.
OpenAI·Costs API data is delayed
The OpenAI Costs API data is delayed. OpenAI reports that the incident is resolved and lasted about 23.5 hours.
OpenAI·Elevated errors with ChatGPT billing and Ads billing
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.
OpenAI·Delayed Costs Data in the Compliance API
OpenAI reported delayed publication of Organization cost data in the Costs API. API and ChatGPT usage were not affected. OpenAI identified the issue, applied a mitigation, and monitored the service. The incident is resolved. It lasted from 13 November 2026 16:10 UTC to 16 November 2026 00:17 UTC.
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.
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.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.
https://outages.live/feed.xml?providers=openai/feed subscribe https://outages.live/feed.xml?providers=openaiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane