Skip to content
context Other verified update

OpenAI resolved an incident that affected 11 API services

clearly official source updated September 17, 2026

OpenAI confirmed that the incident involving increased API error rates had been resolved — it has now emerged that it affected 11 services (Chat Completions, Images, Sora, Embeddings and others), not just the initially reported Chat Completions.

OpenAI announced that the incident involving increased error rates in its API had been fully resolved. According to the latest information from the official OpenAI Status channel, the incident ultimately proved broader than initially reported — it affected a total of 11 services: Chat Completions, Embeddings, Images, Sora, Batch, Audio, Fine-tuning, Files, Moderations, Responses, Realtime and Login. All affected components are now fully functional again.

According to an earlier report from the same source, the first identified issue was an increased error rate in Chat Completions with the error code invalid_prompt. A more recent update showed that the problem actually affected a much wider range of API services than just this one function.

The sources do not specify the exact duration of the incident, the number of affected users or the cause of the invalid_prompt error. Details can be found in the source article.

What changed

Why it matters

For developers and companies building products on the OpenAI API, the key point is that this was a widespread outage across most of the functions offered, not just an isolated error in one service. This strengthens the case for implementing mechanisms to handle outages (retry logic, status page monitoring) in critical integrations that depend on a single provider.

What was added since the original report

Verified updates

  1. New verified information

    The incident affected 11 OpenAI API services (not just Chat Completions); Complete list of affected services: Chat Completions, Embeddings, Images, Sora, Batch, Audio, Fine-tuning, Files, Moderations, Responses, Realtime, Login; The report came from the official OpenAI Status channel; All affected services have fully recovered and are operational; The scope of the incident was substantially greater than the original description suggested

    • The incident affected 11 OpenAI API services (not just Chat Completions)
    • Complete list of affected services: Chat Completions, Embeddings, Images, Sora, Batch, Audio, Fine-tuning, Files, Moderations, Responses, Realtime, Login
    • The report came from the official OpenAI Status channel
    • All affected services have fully recovered and are operational
    • The scope of the incident was substantially greater than the original description suggested

Relevant practical impact

What this means

01

For a business

Companies running production services on the OpenAI API experienced increased error rates across a wide range of functions (chat, image generation, video, embeddings and login) during the incident, highlighting the risk of relying on a single provider.

Risks and compliance
What to decide Verify that your own integrations with the OpenAI API have retry mechanisms and status monitoring through the official status page in place, in case of similar outages in the future.
More business impacts →
API API incident audio Batch Chat Completions chybové sazby chybovost embeddings fine-tuning Images incident infrastructure infrastruktura OpenAI outage Sora outage

Check the original

Event sources

clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.

2
OpenAI Status — incident history official service status · first detected Elevated error rates with the invalid_prompt error code OpenAI Status — incident history official service status We are seeing elevated error rates across API models