AIToday
Large Language ModelsAI Business & IndustryAI WeeklyPublished: Nov 22, 2026, 19:01 JST

OpenAI's ChatGPT and API hit 75% failure rate for 3.5 hours

Send on LINE
OpenAI's ChatGPT and API hit 75% failure rate for 3.5 hours

3 Key Points

  1. What happened

    Between 1:48 and 5:21 PT on November 21, requests to OpenAI's API and ChatGPT failed at rates peaking at 75%, after maintenance on a PostgresDB service caused both read replicas of the Primary API to fail.

  2. Why it matters

    The Primary API handles user authentication and service-to-service authentication across the entire OpenAI stack, so the replica failure took down login and inter-service handshakes underpinning the rest of the product, OpenAI's writeup says.

WHO IT HITSEnterprises and developers running products on OpenAI's API — especially those depending on Chat Completions, Embeddings, Realtime or Files endpoints — saw requests fail during the window, and teams relying on ChatGPT for login-gated workflows were affected too.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The failure centered on a component OpenAI describes as load-bearing: the two Postgres read replicas behind its Primary API service, which handles user authentication and service-to-service authentication across the entire OpenAI stack. When both replicas failed at the same time during scheduled maintenance, login and inter-service handshakes underneath the rest of the product went with them — which is why the blast radius extended from Chat Completions and Embeddings to Conversations, Search and Voice mode in ChatGPT.

Reviving the existing replicas did not work, according to the writeup. The fix was bringing two new replicas in the same region into service in coordination with the provider, which OpenAI does not name. That detail points to how tightly recovery depended on the underlying database provider's involvement, though the writeup does not specify the provider.

OpenAI's stated fixes split into immediate and longer-term steps. It has placed a moratorium on similar maintenance, retuned its database to reduce connection churn, and shipped a feature flag that can shift traffic away from replicas by percentage. Longer term, it says it will add a pre-maintenance review process and hold adequate buffer capacity as hot standbys during maintenance windows. Whether those measures prevent a repeat will only show at the next maintenance window, which the writeup does not date.

FAQ
When did the OpenAI outage happen and how long did it last?
Requests failed at a peak 75% rate between 1:48 and 5:21 PT on November 21, an outage of roughly three and a half hours.
What caused the outage?
Maintenance on a PostgresDB service used by OpenAI's Primary API service caused both read replicas to fail at the same time, per OpenAI's writeup.
Which OpenAI products were affected?
On the API side: Chat Completions, Fine-tuning, Embeddings, Images, Batch, Audio, Moderations, Realtime and the Files endpoint. In ChatGPT: Conversations, Login, Search, File uploads and Voice mode.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleOrcaRouter opens API access to Alibaba's Qwen4 Max