OpenAI logged two separate incidents on 30 October, one hitting GPT Image 2 API edit requests for 4h 3m and another hitting search inside Dots, ChatGPT Work, and some ChatGPT thinking experiences for 1h 36m. Both were faults on OpenAI's side, affecting the APIs and Images components.
Started
14:35 UTC
Duration
Lasted 4h 3m
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: Images, APIs
What happened?
The first incident started at 14:35 UTC, when OpenAI reported elevated errors for some GPT Image 2 API image edit requests. OpenAI said it had identified the issue and was working on a fix, which tells you the cause was known internally even though it wasn't published to you. At 16:06 UTC OpenAI posted that it had applied a mitigation and was monitoring the affected services to confirm recovery. The incident closed out at 4h 3m, the longest of the day. A second, separate incident began at 19:38 UTC, affecting search in Dots, ChatGPT Work, and certain ChatGPT thinking experiences. That one came with a single update, OpenAI saying it was investigating and would share updates, and no further update was filed before it resolved at 1h 36m. Across both incidents, OpenAI published three updates total, and none of them explain what caused either fault. The components list names APIs and Images, which matches the image edit problem directly but is a broader label than the search issue actually touched. No user reports were filed during either window, so this page rests entirely on OpenAI's own status postings. Over the last 90 days OpenAI has logged 103 incidents with a median duration of 1 hour 42 minutes, and the longest incident here, at 4h 3m, ran well past that median.
Learning
Neither incident here came with an explanation of root cause, only a note that a fix or mitigation had been applied, so you're left trusting OpenAI's timeline rather than understanding what broke. Both faults sat inside OpenAI's own infrastructure, image edit processing and search functionality respectively, which is not something your own uptime checks against your product would ever catch, because the failure happened upstream of your integration, not inside your code. If you only monitor your own endpoints, a problem like this shows up to you as mysteriously elevated error rates from your AI features, with nothing in your own logs pointing at OpenAI specifically. Over the last 30 days, external monitoring aimed at OpenAI itself recorded 43 incidents, all resolved, with a median duration of 1h 38m, a pattern consistent with what happened on this day. That comparison matters: your monitoring and a provider's outage can both be telling the truth at once, because they're watching different halves of the same request. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.