OpenAI's image generation and ChatGPT hit elevated errors for 1h 52m on 8 November 2026. OpenAI identified the problem and applied a mitigation on their end, so this one sits on their side of the ledger, not yours.
Started
15:11 UTC
Duration
Lasted 1h 52m
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: Image Generation, ChatGPT
What happened?
OpenAI's status page logged one incident on 8 November 2026, starting at 15:11 UTC and running 1h 52m. Two components were listed as affected: Image Generation and ChatGPT. The first update, at 15:11, said users were experiencing elevated errors for the impacted services and that OpenAI was working on a mitigation. The second and final update, at 15:43, said a mitigation had been applied and the team was monitoring to confirm recovery. No update after that was published, and the incident's end is inferred only from the stated 1h 52m duration, not from a closing note on the record. There is no post-mortem, and OpenAI's own filing is thin: two updates, 32 minutes apart, with no root cause stated at any point. No user reports were filed during the window, which is unusual for an OpenAI incident of this length but is what the record shows. Over the past 90 days, OpenAI has logged 101 incidents with a median duration of 1 hour 46 minutes, so this one is close to typical in length even though OpenAI never said what caused it. Across all time, OpenAI has filed 996 incidents, averaging 15.3 a month, which puts this day in the normal run rate rather than anything exceptional.
Learning
OpenAI's incident updates describe elevated errors on their own services, which means the fault sat inside their infrastructure rather than in anything you control. If you were only watching your own endpoints that call the OpenAI API, you would have seen failed or slow requests without any way to tell whether the problem was your code, your network, or OpenAI's backend. That is the layer a status page from the provider itself is built to answer, and in this case it answered with two brief updates and no explanation of cause. Over the last 30 days, UptimeRobot's own checks against OpenAI logged 29 incidents with 28 resolved and a median duration of 2h 2m, a different number from OpenAI's self-reported 90 day median of 1h 46m, which is a normal gap between two different vantage points watching the same provider. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.