OpenAI incident

Elevated 401 errors for API endpoints

Minor Resolved View vendor source →

OpenAI experienced a minor incident on April 14, 2026 affecting Responses and Embeddings and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.

Started
Apr 14, 2026, 08:41 AM UTC
Resolved
Apr 14, 2026, 08:41 AM UTC
Duration
Detected by Pingoru
Apr 14, 2026, 08:41 AM UTC

Affected components

ResponsesEmbeddingsChat Completions

Update timeline

  1. investigating Apr 12, 2026, 08:40 PM UTC

    Status: Investigating We are investigating the issue for the listed services.

  2. monitoring Apr 12, 2026, 10:28 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery.

  3. investigating Apr 13, 2026, 05:55 AM UTC

    Status: Investigating We are investigating the issue for the listed services.

  4. monitoring Apr 13, 2026, 06:34 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery.

  5. identified Apr 13, 2026, 12:57 PM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

  6. identified Apr 13, 2026, 05:10 PM UTC

    Status: Identified We've identified that intermittent 401 errors on some API endpoints are being caused by timeouts. We have applied mitigations that reduced impact in parts of the system and are continuing to deploy additional fixes and monitor recovery until error rates return to expected levels.

  7. identified Apr 13, 2026, 08:14 PM UTC

    Status: Identified We've identified that intermittent 401 errors on some API endpoints are being caused by timeouts. We have applied mitigations that reduced impact in parts of the system and are continuing to deploy additional fixes and monitor recovery until error rates return to expected levels.

  8. identified Apr 13, 2026, 11:26 PM UTC

    Status: Identified We've identified that intermittent 401 errors on some API endpoints are being caused by timeouts. We have applied mitigations that reduced impact in parts of the system and are continuing to deploy additional fixes and monitor recovery until error rates return to expected levels. Affected components Chat Completions (Degraded performance) Embeddings (Degraded performance) Responses (Degraded performance)

  9. monitoring Apr 14, 2026, 01:26 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Chat Completions (Degraded performance) Embeddings (Degraded performance) Responses (Degraded performance)

  10. resolved Apr 14, 2026, 08:41 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Chat Completions (Operational) Embeddings (Operational) Responses (Operational)