Part of OpenAI

OpenAI API Outage History

OpenAI API is up right now

OpenAI API had 60 outages in the last 2 years — averaging 2.5 incidents per month.

There were 60 OpenAI API outages since January 27, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.openai.com

Minor June 29, 2026

Codex Usage Limits Depleting Faster Than Expected

Detected by Pingoru
Jun 29, 2026, 05:06 PM UTC
Resolved
Jun 29, 2026, 05:06 PM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 3 updates
  1. investigating Jun 26, 2026, 05:04 PM UTC

    Status: Investigating We are investigating reports that Codex usage limits are being consumed faster than expected. Affected components Codex API (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance)

  2. monitoring Jun 26, 2026, 11:24 PM UTC

    Status: Monitoring We have identified that some reports of Codex usage limits depleting faster than expected are related to our abuse and fraud prevention systems incorrectly rate limiting certain accounts. The impact appears limited, and we have not observed broader degradation to Codex usage. We are continuing to monitor the situation. Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

  3. resolved Jun 29, 2026, 05:06 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

Read the full incident report →

Minor June 26, 2026

FedRAMP workspaces and API orgs have degraded performance

Detected by Pingoru
Jun 26, 2026, 11:07 PM UTC
Resolved
Jun 26, 2026, 11:07 PM UTC
Duration
—
Affected: FedRAMP
Timeline · 5 updates
  1. identified Jun 15, 2026, 09:23 PM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components FedRAMP (Degraded performance)

  2. investigating Jun 15, 2026, 10:16 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components FedRAMP (Degraded performance)

  3. investigating Jun 17, 2026, 01:24 AM UTC

    Status: Investigating We are still investigating the issue for the listed services. Affected components FedRAMP (Degraded performance)

  4. investigating Jun 18, 2026, 07:41 PM UTC

    Status: Investigating We are still investigating the issue for the listed services. Affected components FedRAMP (Degraded performance)

  5. resolved Jun 26, 2026, 11:07 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components FedRAMP (Operational)

Read the full incident report →

Minor June 25, 2026

Users may encounter issues using access token with Codex

Detected by Pingoru
Jun 25, 2026, 11:03 AM UTC
Resolved
Jun 25, 2026, 11:03 AM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 4 updates
  1. investigating Jun 25, 2026, 05:51 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  2. monitoring Jun 25, 2026, 08:02 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  3. resolved Jun 25, 2026, 11:03 AM UTC

    Status: Resolved This is now resolved. Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

  4. resolved Jun 25, 2026, 11:03 AM UTC

    Status: Resolved This is now resolved Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

Read the full incident report →

Minor June 24, 2026

gpt-4o-mini high error rate

Detected by Pingoru
Jun 24, 2026, 06:07 AM UTC
Resolved
Jun 24, 2026, 06:07 AM UTC
Duration
—
Affected: LoginResponsesFine-tuningImagesBatchAudioModerationsSoraEmbeddingsChat CompletionsRealtimeFiles
Timeline · 2 updates
  1. monitoring Jun 24, 2026, 05:59 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Responses (Degraded performance) Sora (Degraded performance) Images (Degraded performance) Batch (Degraded performance) Audio (Degraded performance) Embeddings (Degraded performance) Login (Degraded performance) Chat Completions (Degraded performance) Fine-tuning (Degraded performance) Realtime (Degraded performance) Files (Degraded performance) Moderations (Degraded performance)

  2. resolved Jun 24, 2026, 06:07 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Images (Operational) Batch (Operational) Fine-tuning (Operational) Files (Operational) Moderations (Operational) Responses (Operational) Login (Operational) Sora (Operational) Chat Completions (Operational) Audio (Operational) Realtime (Operational) Embeddings (Operational)

Read the full incident report →

Minor June 16, 2026

Codex "Selected Model is at Capacity" Error

Detected by Pingoru
Jun 16, 2026, 01:48 PM UTC
Resolved
Jun 16, 2026, 01:48 PM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 3 updates
  1. identified Jun 16, 2026, 10:32 AM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  2. monitoring Jun 16, 2026, 01:32 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Codex API (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance)

  3. resolved Jun 16, 2026, 01:48 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex API (Operational) Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational)

Read the full incident report →

Minor June 16, 2026

Users may experience issue with Codex Cloud tasks

Detected by Pingoru
Jun 16, 2026, 12:55 AM UTC
Resolved
Jun 16, 2026, 12:55 AM UTC
Duration
—
Affected: Codex Web
Timeline · 2 updates
  1. investigating Jun 16, 2026, 12:07 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Codex Web (Degraded performance)

  2. resolved Jun 16, 2026, 12:55 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational)

Read the full incident report →

Minor June 12, 2026

Elevated 431 Errors

Detected by Pingoru
Jun 12, 2026, 12:47 AM UTC
Resolved
Jun 12, 2026, 12:47 AM UTC
Duration
—
Affected: LoginResponsesFine-tuningImagesBatchAudioModerationsSoraEmbeddingsChat CompletionsRealtimeFilesLogin
Timeline · 4 updates
  1. identified Jun 11, 2026, 10:22 PM UTC

    Status: Identified We have identified that some users are experiencing elevated 431 errors for the impacted services. We are working on implementing a mitigation. Affected components Images (Degraded performance) Batch (Degraded performance) Chat Completions (Degraded performance) Fine-tuning (Degraded performance) Files (Degraded performance) Moderations (Degraded performance) Responses (Degraded performance) Login (Degraded performance) Audio (Degraded performance) Realtime (Degraded performance) Embeddings (Degraded performance) Sora (Degraded performance)

  2. investigating Jun 11, 2026, 10:59 PM UTC

    Status: Investigating We are continuing to investigate the issue regarding elevated 431 errors and are working on the mitigation. Affected components Batch (Degraded performance) Chat Completions (Degraded performance) Files (Degraded performance) Embeddings (Degraded performance) Responses (Degraded performance) Sora (Degraded performance) Images (Degraded performance) Audio (Degraded performance) Fine-tuning (Degraded performance) Realtime (Degraded performance) Moderations (Degraded performance) Login (Degraded performance)

  3. monitoring Jun 11, 2026, 11:25 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Responses (Degraded performance) Login (Degraded performance) Batch (Degraded performance) Realtime (Degraded performance) Files (Degraded performance) Sora (Degraded performance) Images (Degraded performance) Chat Completions (Degraded performance) Audio (Degraded performance) Fine-tuning (Degraded performance) Embeddings (Degraded performance) Moderations (Degraded performance)

  4. resolved Jun 12, 2026, 12:47 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Chat Completions (Operational) Realtime (Operational) Files (Operational) Embeddings (Operational) Responses (Operational) Login (Operational) Images (Operational) Batch (Operational) Audio (Operational) Fine-tuning (Operational) Moderations (Operational) Sora (Operational)

Read the full incident report →

Minor June 11, 2026

Elevated error rates for GPT 5.5 in Codex

Detected by Pingoru
Jun 11, 2026, 10:28 PM UTC
Resolved
Jun 11, 2026, 10:28 PM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 3 updates
  1. identified Jun 11, 2026, 08:59 PM UTC

    Status: Identified We have identified that users are experiencing elevated errors when using GPT 5.5 in Codex. We are working on implementing a mitigation. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  2. monitoring Jun 11, 2026, 09:33 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance)

  3. resolved Jun 11, 2026, 10:28 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components VS Code extension (Operational) Codex API (Operational) Codex Web (Operational) CLI (Operational) App (Operational)

Read the full incident report →

Minor June 4, 2026

Increased latency for Codex compaction for a subset of users

Detected by Pingoru
Jun 04, 2026, 04:37 AM UTC
Resolved
Jun 04, 2026, 04:37 AM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 2 updates
  1. identified Jun 04, 2026, 02:57 AM UTC

    Status: Identified We have identified that users are experiencing elevated latency for the impacted services. We are working on implementing a mitigation. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  2. resolved Jun 04, 2026, 04:37 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

Read the full incident report →

Minor June 3, 2026

codex-gpt-image-2-does-not-exist-errors

Detected by Pingoru
Jun 03, 2026, 12:13 AM UTC
Resolved
Jun 03, 2026, 12:13 AM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 2 updates
  1. monitoring Jun 02, 2026, 11:35 PM UTC

    Status: Monitoring We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  2. resolved Jun 03, 2026, 12:13 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational) Codex Web (Operational)

Read the full incident report →

Minor May 28, 2026

Codex Context Compaction Latency

Detected by Pingoru
May 28, 2026, 06:59 AM UTC
Resolved
May 28, 2026, 06:59 AM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 6 updates
  1. identified May 27, 2026, 05:57 PM UTC

    Status: Identified We're investigating an issue causing Codex context compaction to be slower than expected. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  2. investigating May 28, 2026, 12:14 AM UTC

    Status: Investigating We are still investigating the issue for the listed services. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  3. investigating May 28, 2026, 01:47 AM UTC

    Status: Investigating We are still investigating the issue for the listed services. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  4. identified May 28, 2026, 02:31 AM UTC

    Status: Identified We've identified a configuration error that caused Codex to be slow. We are working on implementing the mitigation at the moment. Affected components Codex API (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance)

  5. monitoring May 28, 2026, 03:09 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  6. resolved May 28, 2026, 06:59 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

Read the full incident report →

Minor May 28, 2026

Subscription checkout failing

Detected by Pingoru
May 28, 2026, 05:27 AM UTC
Resolved
May 28, 2026, 05:27 AM UTC
Duration
—
Affected: LoginResponsesFine-tuningImagesBatchAudioModerationsSoraCodex WebCodex APICLIVS Code extensionChatGPT AtlasFedRAMPEmbeddingsChat CompletionsRealtimeFilesFile uploadsConversationsAgentVoice modeConnectors/AppsCompliance APIAppDeep ResearchSearchGPTsImage GenerationLogin
Timeline · 1 update
  1. resolved May 28, 2026, 05:27 AM UTC

    Status: Resolved Resolved - Some users were unable to complete subscriptions on web and mobile. Affected users may have experienced the Subscribe button becoming unresponsive or encountered the error message submit_error_source:email during checkout. Affected components Conversations (Operational) Embeddings (Operational) Connectors/Apps (Operational) Login (Operational) CLI (Operational) App (Operational) File uploads (Operational) Batch (Operational) Audio (Operational) Compliance API (Operational) Responses (Operational) Agent (Operational) Search (Operational) Deep Research (Operational) VS Code extension (Operational) Chat Completions (Operational) ChatGPT Atlas (Operational) Files (Operational) GPTs (Operational) Sora (Operational) FedRAMP (Operational) Images (Operational) Fine-tuning (Operational) Login (Operational) Codex API (Operational) Voice mode (Operational) Realtime (Operational) Moderations (Operational) Image Generation (Operational) Codex Web (Operational)

Read the full incident report →

Minor May 27, 2026

Elevated Latency and Errors on API

Detected by Pingoru
May 27, 2026, 08:06 PM UTC
Resolved
May 27, 2026, 08:06 PM UTC
Duration
—
Affected: AudioEmbeddingsChat Completions
Timeline · 7 updates
  1. investigating May 27, 2026, 02:47 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Chat Completions (Degraded performance) Audio (Degraded performance) Embeddings (Degraded performance)

  2. investigating May 27, 2026, 03:21 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Audio (Degraded performance) Embeddings (Degraded performance) Chat Completions (Degraded performance)

  3. identified May 27, 2026, 03:45 PM UTC

    Status: Identified We are still implementing the mitigation. Affected components Chat Completions (Degraded performance) Audio (Degraded performance) Embeddings (Degraded performance)

  4. monitoring May 27, 2026, 03:59 PM UTC

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

  5. resolved May 27, 2026, 05:12 PM UTC

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

  6. monitoring May 27, 2026, 05:54 PM UTC

    Status: Monitoring We have received additional reports of elevated latency and errors after our previous recovery update. Mitigation remains in place, and we are monitoring recovery while we validate the remaining impact. Affected components Chat Completions (Degraded performance) Audio (Degraded performance) Embeddings (Degraded performance)

  7. resolved May 27, 2026, 08:06 PM UTC

    Status: Resolved The API issue has been Resolved. Affected components Chat Completions (Operational) Audio (Operational) Embeddings (Operational)

Read the full incident report →

Minor May 27, 2026

Login issues for FedRAMP users who recently logged out

Detected by Pingoru
May 27, 2026, 06:01 AM UTC
Resolved
May 27, 2026, 06:01 AM UTC
Duration
—
Affected: LoginFedRAMPLogin
Timeline · 4 updates
  1. investigating May 26, 2026, 01:59 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Login (Degraded performance) FedRAMP (Degraded performance)

  2. identified May 26, 2026, 02:20 PM UTC

    Status: Identified We have identified that users are experiencing login issues for the impacted services. We are working on implementing a mitigation. Affected components Login (Degraded performance) FedRAMP (Degraded performance)

  3. monitoring May 27, 2026, 05:31 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Login (Degraded performance) FedRAMP (Degraded performance)

  4. resolved May 27, 2026, 04:16 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Login (Operational) FedRAMP (Operational)

Read the full incident report →

Minor May 23, 2026

Increase in users hitting Codex rate limits

Detected by Pingoru
May 23, 2026, 10:58 AM UTC
Resolved
May 23, 2026, 10:58 AM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 4 updates
  1. investigating May 22, 2026, 04:37 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  2. monitoring May 22, 2026, 07:16 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components VS Code extension (Degraded performance) Codex API (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance)

  3. monitoring May 22, 2026, 07:16 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components VS Code extension (Degraded performance) Codex API (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance)

  4. resolved May 23, 2026, 10:58 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components App (Operational) VS Code extension (Operational) Codex API (Operational) Codex Web (Operational) CLI (Operational)

Read the full incident report →

Minor May 20, 2026

API users may see increased error rates for GPT-5.4 and GPT-5.5

Detected by Pingoru
May 20, 2026, 12:37 AM UTC
Resolved
May 20, 2026, 12:37 AM UTC
Duration
—
Affected: ResponsesChat Completions
Timeline · 4 updates
  1. identified May 19, 2026, 11:32 PM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  2. monitoring May 19, 2026, 11:38 PM UTC

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

  3. monitoring May 19, 2026, 11:59 PM UTC

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

  4. resolved May 20, 2026, 12:37 AM UTC

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

Read the full incident report →

Minor May 13, 2026

Codex 5.5 engines are experiencing high error rate

Detected by Pingoru
May 13, 2026, 10:20 AM UTC
Resolved
May 13, 2026, 10:20 AM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 4 updates
  1. investigating May 13, 2026, 08:18 AM UTC

    Status: Investigating We are currently experiencing elevated error rates for gpt-5.5. Affected components CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance) Codex Web (Degraded performance)

  2. identified May 13, 2026, 09:00 AM UTC

    Status: Identified High error rate on codex gpt 5.5 for free users. Degraded latency on gpt 5.5 for all codex users. Affected components Codex API (Degraded performance) Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance)

  3. monitoring May 13, 2026, 09:34 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Codex Web (Degraded performance) CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance)

  4. resolved May 13, 2026, 10:20 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

Read the full incident report →

Minor May 13, 2026

Realtime API - SIP/WebRTC flow are down

Detected by Pingoru
May 13, 2026, 09:23 AM UTC
Resolved
May 13, 2026, 09:23 AM UTC
Duration
—
Affected: Audio
Timeline · 3 updates
  1. investigating May 13, 2026, 06:28 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Audio (Degraded performance)

  2. investigating May 13, 2026, 06:37 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Audio (Degraded performance)

  3. resolved May 13, 2026, 09:23 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Audio (Operational)

Read the full incident report →

Minor May 11, 2026

Elevated error rates with GPT 5.5

Detected by Pingoru
May 11, 2026, 05:59 PM UTC
Resolved
May 11, 2026, 05:59 PM UTC
Duration
—
Affected: ResponsesChat Completions
Timeline · 4 updates
  1. investigating May 11, 2026, 04:11 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Responses (Degraded performance) Chat Completions (Degraded performance)

  2. identified May 11, 2026, 04:35 PM UTC

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  3. monitoring May 11, 2026, 05:04 PM UTC

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

  4. resolved May 11, 2026, 05:59 PM UTC

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

Read the full incident report →

Minor May 11, 2026

Users may experience elevated errors in ChatGPT uploading files and Codex Cloud creating tasks

Detected by Pingoru
May 11, 2026, 05:35 AM UTC
Resolved
May 11, 2026, 05:35 AM UTC
Duration
—
Affected: Codex WebFile uploads
Timeline · 3 updates
  1. investigating May 11, 2026, 01:23 AM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components File uploads (Degraded performance) Codex Web (Degraded performance)

  2. monitoring May 11, 2026, 03:23 AM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components File uploads (Degraded performance) Codex Web (Operational)

  3. resolved May 11, 2026, 05:35 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational) File uploads (Operational)

Read the full incident report →

Minor May 9, 2026

Elevated errors for Responses API

Detected by Pingoru
May 09, 2026, 12:08 AM UTC
Resolved
May 09, 2026, 12:08 AM UTC
Duration
—
Affected: Responses
Timeline · 2 updates
  1. monitoring May 09, 2026, 12:07 AM UTC

    Status: Monitoring Between 4:05pm and 4:40pm PT on May 8, some customers using the Responses API may have experienced elevated 404 errors. We identified the issue as related to a recent deploy and rolled it back. Responses API traffic has recovered, and we are marking this incident as resolved. Affected components Responses (Partial outage)

  2. resolved May 09, 2026, 12:08 AM UTC

    Status: Resolved All impacted services have now fully recovered. Between 4:05pm and 4:40pm PT on May 8, some customers using the Responses API may have experienced elevated 404 errors. We identified the issue as related to a recent deploy and rolled it back. Responses API traffic has recovered, and we are marking this incident as resolved. Affected components Responses (Operational)

Read the full incident report →

Minor May 8, 2026

Degraded Performance with Codex Cloud Tasks

Detected by Pingoru
May 08, 2026, 04:17 PM UTC
Resolved
May 08, 2026, 04:17 PM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionApp
Timeline · 2 updates
  1. investigating May 08, 2026, 03:07 PM UTC

    Status: Investigating We are observing an issue with follow-up prompts to Codex Cloud tasks failing at higher than expected rate. We are investigating the issue. Affected components Codex Web (Degraded performance)

  2. resolved May 08, 2026, 04:17 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational) CLI (Operational) App (Operational) VS Code extension (Operational) Codex API (Operational)

Read the full incident report →

Minor May 8, 2026

Increased Error Rate for gpt-5.5 model in the API

Detected by Pingoru
May 08, 2026, 02:14 PM UTC
Resolved
May 08, 2026, 02:14 PM UTC
Duration
—
Affected: ResponsesChat Completions
Timeline · 5 updates
  1. investigating May 08, 2026, 12:31 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  2. investigating May 08, 2026, 01:26 PM UTC

    Status: Investigating We are seeing partial recovery, but are still working on implementing additional mitigations. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  3. identified May 08, 2026, 01:42 PM UTC

    Status: Identified We implemented the mitigations and are observing reduction in error rates, but are still seeing higher than normal latency. Affected components Chat Completions (Degraded performance) Responses (Degraded performance)

  4. monitoring May 08, 2026, 01:57 PM UTC

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

  5. resolved May 08, 2026, 02:14 PM UTC

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

Read the full incident report →