OpenAI favicon

OpenAI outage on 2026-10-23

openai.com
October 2026 23 Minor incident

OpenAI logged three separate incidents on 23 October 2026, starting with a 2 hour 19 minute spell of delayed customer support responses. Later in the day, Help Center chat support and ChatGPT app connections using CIMD each had shorter spells of degraded service. All three were OpenAI's own systems, and OpenAI's status page is the only record of them.

Started

03:41 UTC

Duration

Lasted 2h 19m

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.

What happened?

The first incident started at 03:41 UTC, when OpenAI said it was investigating technical issues affecting its customer support systems and warned of longer than usual response times. At 03:57 it told customers to email support@openai.com as a workaround while the main system was unavailable. A fix was identified at 04:43 and mitigation was applied by 05:47, closing out the incident at 2 hours 19 minutes, the longest of the day. At 21:30 a second incident began, this time degraded performance in Help Center chat support, with OpenAI again pointing customers to email support in the meantime. That one was mitigated by 21:52, a 35 minute spell. A third incident followed at 22:52, affecting ChatGPT app connections that use CIMD. OpenAI said some app connections failed when connecting a new app or refreshing an existing one, and traced it to an authentication metadata endpoint. That endpoint came back and mitigation was applied by 23:17, closing the incident at 53 minutes. None of the three incidents named components affected beyond their own titles, and OpenAI's page lists no broader service list for any of them. No user reports were filed during the window for any of the three incidents. OpenAI did not publish a cause for any of them beyond naming the system involved, and no post-mortem has been published for the day.

Learning

All three incidents here hit support and account-linking infrastructure, not the core ChatGPT or API traffic that an external check against openai.com would typically probe. That is why a standard uptime check watching the main endpoint can stay green through incidents like a slow Help Center chat tool or a broken authentication metadata endpoint for app connections: those are separate systems with separate failure points, and a green check on one says nothing about the health of the other. Over the past 90 days OpenAI has logged 101 incidents with a median duration of 1 hour 39 minutes, and across all time it averages 15.4 a month, so a short-lived support or auth issue like this one is common rather than exceptional for this provider. If your product depends on ChatGPT app connections or relies on OpenAI support channels, your own monitoring of your integration will not catch an outage that originates entirely inside OpenAI's systems. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.