Elevated errors affecting logins, sign-ups, and ChatGPT features
Logins, sign-ups, work mode, dots, sites, and spaces had elevated errors at OpenAI. OpenAI also reported elevated error rates for creating conversations through the OpenAI API. OpenAI reports that the incident is resolved and that all affected services operate normally again. The outage lasted 9 minutes.
State
Resolved
Started
Lasted
9 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
9 min 100%
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’re investigating an outage for logins, signups, work mode, dots, sites, and spaces. We are also investigating elevated error rates when creating conversations through the OpenAI API. We are checking how it affects users. We’ll share an update when we know more.
We’re investigating an outage for logins, signups, work mode, dots, sites, and spaces. We are checking how it affects users. We’ll share an update when we know more.
We’re investigating an outage for logins, signups, work mode, dots, sites, and spaces. We are 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
33
Days with an incident
25
Median duration
1 h 54 min
This incident
92% shorter than the median
Other OpenAI incidents
All incidentsOpenAI·Incorrect cost data in Costs API exports
Costs API exports published between November 6 and November 9 contain incorrect cost data. OpenAI reports that the incident is resolved. The incident lasted 140 minutes.
OpenAI·Elevated Errors On API
OpenAI reported elevated errors on the API. OpenAI later stated that all affected services operate normally again. The incident is resolved and lasted about 43 minutes.
OpenAI·Elevated ChatGPT Conversation Errors
ChatGPT conversation errors increased for some users. OpenAI reported the incident as resolved. The outage lasted 52 minutes.
OpenAI·Elevated errors with image generation
Image generation does not work and users get errors. OpenAI reports that the incident is resolved. The outage lasted about 109 minutes.
OpenAI·Elevated error rates with some U.S. business Mastercards
OpenAI reports payment declines on some U.S. business Mastercards, including some Brex cards. This can block API automatic recharges and one-time credit purchases. OpenAI applied a mitigation and the incident is now resolved, lasting from 6 November to 10 November 2026.
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