Get 30 days of Pro free

OpenAI outage on November 19, 2026

Measured window 16:01 UTC to 16:59 UTC on November 19, 2026, 57 minutes. Worst status observed: major.

StatusBird recorded OpenAI as not operational from 16:01 UTC on 19 November 2026. The worst state we measured was major. We check every two minutes, and 29 of those checks came back non-operational, covering about one hour. The service had not recovered when this note was written, so the disruption may still be running as you read it.

Incident at a glance

ServiceOpenAI
DateNovember 19, 2026
StatusBird first saw it16:01 UTC
Vendor posted an incident Not published
Recovery observed 16:59 UTC
Duration 57 minutes
Worst status observed major
Non-operational readings29

All times UTC. StatusBird polls OpenAI every 2 minutes from its own infrastructure, so the true start and end sit within 2 minutes of the times above.

Was OpenAI down on November 19, 2026?

Yes. StatusBird recorded OpenAI as major from 16:01 UTC until 16:59 UTC, a measured 57 minutes. 29 consecutive checks came back non-operational.

What caused the OpenAI outage?

No cause is known. The vendor's status page had posted no incident at the time of writing, and OpenAI has published no explanation. StatusBird reports only what its own checks measured, so we will not guess at what went wrong inside the service. If a cause is published later, treat that as the authoritative account.

The cause has not yet been published by OpenAI. StatusBird measures availability from outside the vendor, which shows when a service stopped responding normally but never why. This section is updated if OpenAI publishes a root cause.

How long was OpenAI down?

57 minutes, measured from the first non-operational reading at 16:01 UTC to the first reading that cleared it at 16:59 UTC. StatusBird counts a service down from the first reading it fails, not from the moment the vendor admits it, which is why this number can be larger than the one on the vendor's own incident report.

Timeline, in UTC

Time (UTC)Event
16:01 UTCStatusBird records its first non-operational reading
16:04 UTCA second consecutive non-operational reading confirms the outage, alerts go out and this page is published
16:59 UTCStatusBird records the first reading that clears the outage

Who and what was affected

This affects any store that calls OpenAI during a customer's visit or during order handling. Typical things that stop working are AI chat and support replies, automatic product descriptions and tags, review or ticket summaries, and search or recommendation features that ask a model for results. If your checkout, order confirmation or returns flow waits on one of these calls, customers may see slow pages, errors or blank sections instead of a clear message.

How StatusBird detected it

StatusBird recorded its first non-operational reading for OpenAI at 16:01 UTC, polling the vendor's status endpoint every 2 minutes from its own infrastructure. No incident had been posted on OpenAI's own status page when this page was written, so the times here are StatusBird's observations rather than a restatement of the vendor's report.

Method: StatusBird reads OpenAI's published status endpoint every 2 minutes and records every reading. Availability figures count major and critical only. The full method is at statusbird.io/methodology.

Lessons for merchants

  1. Set a short timeout on every AI call and show a plain fallback message when it fails.
  2. Keep AI features out of the checkout and payment path so orders can still complete.
  3. Do not rely on the vendor status page alone, since it showed no incident during this outage.
  4. Write a manual fallback for support replies and product copy so staff can keep working.

The longer version, with the checks specific to this service, is in the OpenAI outage playbook.

Frequently asked questions

Was OpenAI down on November 19, 2026?

Yes. StatusBird recorded OpenAI as major from 16:01 UTC on November 19, 2026, for a measured 57 minutes.

How long was OpenAI down?

57 minutes, measured from the first non-operational reading at 16:01 UTC to the first clear reading at 16:59 UTC. Readings are taken every 2 minutes, so the true start and end sit within 2 minutes of those times.

What caused the OpenAI outage?

The cause has not yet been published by OpenAI. StatusBird measures availability from outside the vendor, which shows when a service stopped responding normally but never why. This section is updated if OpenAI publishes a root cause.

How was this OpenAI outage detected?

StatusBird recorded its first non-operational reading for OpenAI at 16:01 UTC, polling the vendor's status endpoint every 2 minutes from its own infrastructure. No incident had been posted on OpenAI's own status page when this page was written, so the times here are StatusBird's observations rather than a restatement of the vendor's report.

Was my store affected?

If your store calls OpenAI during checkout or fulfillment, the requests to check are the ones made between 16:01 UTC and 16:59 UTC on November 19, 2026. Orders created in that window without a matching downstream record are the usual casualty.

Monitor OpenAI with StatusBird

This page exists because StatusBird was already watching. It checks OpenAI and the rest of the stack an online store runs on every 2 minutes and sends an SMS, email, Slack, Teams or Discord alert the moment a reading goes non-operational, which on this incident was 16:01 UTC.

Start monitoring free Live OpenAI status All OpenAI outages

Other OpenAI outages