OpenAI had two separate incidents on 11 November, one hitting logins, sign-ups, and ChatGPT features, the other blocking new Workspace Agent runs for nearly ten hours. Both were OpenAI's own problems, confirmed on OpenAI's status page.
Started
22:50 UTC
Duration
Lasted 9h 45m
Source
IsDown
Next time
OpenAI is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Operator, ChatGPT, Login
What happened?
The first incident started at 20:43 UTC and lasted 10 minutes. OpenAI's own update described it as an outage affecting logins, signups, work mode, dots, sites, and spaces, with the team checking how far it reached before resolving it. Only one update was filed for that incident, and it closed quickly. The second incident began at 22:50 UTC and ran for 9 hours and 45 minutes, affecting Workspace Agent, which falls under the Operator component on OpenAI's status page. The single update posted said OpenAI was investigating an issue preventing users from starting new Workspace Agent runs, and promised more information later. No further update was published on the record, so there is no explanation of what caused it or what fixed it. Across the day, three components were touched: Login, ChatGPT, and Operator. No user reports were filed during the window on either incident. OpenAI's 90-day history shows 101 incidents with a median duration of 1 hour 42 minutes, so the second incident ran well past that median before it resolved.
Learning
UptimeRobot's 30-day data for OpenAI shows 32 incidents, all resolved, with a median duration of 2h 2m, which gives a sense of how often this provider has problems and how long they typically take to clear. When an incident is scoped to a single feature, like Workspace Agent runs, an external check hitting the main ChatGPT endpoint can stay green the whole time, because the top-level service is answering fine while one function underneath it is broken. That is the shape to watch for: a narrow failure inside a product that looks, from outside, like everything is working. Your own monitoring tells you whether your product can reach OpenAI at all, but it cannot tell you whether a specific feature like Workspace Agent is silently broken on OpenAI's side. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.