|
- OpenAI Status
We’re not aware of any issues affecting our systems System status Mar 2025-Jun 2025
- Elevated error rates - OpenAI Status
We are seeing continued recovery across API and ChatGPT We will provide further updates as progress is made Tue, Jun 10, 2025, 04:23 PM ( 56 minutes earlier)
- API, ChatGPT Sora Facing Issues - OpenAI Status
We began to see recovery for API traffic starting at approximately 5:40pm PST, and for ChatGPT and Sora around 6:50pm PST We mitigated the issues at 7:38 pm PST, and all services are now fully operational OpenAI will run a full root-cause analysis of this outage and will share details on this page when complete
- Periodic outages across ChatGPT and API - OpenAI Status
We are dealing with periodic outages due to an abnormal traffic pattern reflective of a DDoS attack We are continuing work to mitigate this
- Major Outage across ChatGPT and API - OpenAI Status
On November 8th between 5:42AM - 7:16AM PT a large portion of requests to OpenAI failed with 502 or 503 error codes All models and API endpoints saw significant failures over the course of the event The outage occurred due to routing layer nodes hitting memory limits and failing readiness checks
- Outage on ChatGPT and API Platform - OpenAI Status
Between 15:05 PDT and 15:20 PDT, we saw increased error rates with logins on ChatGPT and the API Platform We also experienced increased error rates with account creation between 15:21 PDT - 15:43 PDT This is now resolved
- High error rates for ChatGPT, APIs, and Sora - OpenAI Status
Starting at 10:40 AM PST, we experienced high error rates on ChatGPT, Sora, and a subset of APIs We began to see recovery for Sora at approximately 2:58 PM PST, API traffic starting at approximately 3:05 PM PST, and full recovery for ChatGPT around 8:16 PM PST
- API ChatGPT Performance Degradation - OpenAI Status
These elevated latencies led to 45% of API requests experiencing 499 errors, which appeared as client-side cancellations In the ChatGPT interfaces this latency manifested itself as a 30 second "wait time" after which requests were completed
|
|
|