OpenAI Outage History

OpenAI is up right now

OpenAI had 144 outages in the last 2 years — averaging 5.9 incidents per month.

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

Source: https://status.openai.com · Aggregated across OpenAI products

Minor May 28, 2026

Android ChatGPT Business users having trouble switching workspaces

Detected by Pingoru
May 28, 2026, 03:59 AM UTC
Resolved
May 28, 2026, 03:59 AM UTC
Duration
—
Affected: LoginLogin
Timeline · 2 updates
  1. investigating May 27, 2026, 04:24 PM UTC

    Status: Investigating Android ChatGPT users may have trouble switching workspaces. We are investigating and will provide updates as more information becomes available. Affected components Login (Degraded performance)

  2. resolved May 28, 2026, 03:59 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Login (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 26, 2026

Users unable to access chat support on help center

Detected by Pingoru
May 26, 2026, 08:30 PM UTC
Resolved
May 26, 2026, 08:30 PM UTC
Duration
—
Affected: LoginLogin
Timeline · 2 updates
  1. identified May 26, 2026, 08:27 PM UTC

    Status: Identified We are aware of reports from users who are experiencing errors when attempting access Chat support the help center. For help, please email [email protected] "[email protected]": mailto:[email protected] We are working implementing the mitigation. Affected components Login (Degraded performance)

  2. resolved May 26, 2026, 08:30 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Login (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 21, 2026

Elevated latency and error rates for ChatGPT 5.5 Thinking

Detected by Pingoru
May 21, 2026, 11:22 PM UTC
Resolved
May 21, 2026, 11:22 PM UTC
Duration
—
Affected: Conversations
Timeline · 4 updates
  1. identified May 21, 2026, 10:05 PM UTC

    Status: Identified We have identified that users are experiencing elevated latency and error rates for ChatGPT 5.5 Thinking. We are working on implementing a mitigation. Affected components Conversations (Degraded performance)

  2. monitoring May 21, 2026, 10:25 PM UTC

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

  3. monitoring May 21, 2026, 10:57 PM UTC

    Status: Monitoring We are continuing to monitor recovery. Affected components Conversations (Degraded performance)

  4. resolved May 21, 2026, 11:22 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Conversations (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 17, 2026

GPT5.5 Performance Degradation

Detected by Pingoru
May 17, 2026, 12:15 AM UTC
Resolved
May 17, 2026, 12:15 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 15, 2026, 04:11 PM UTC

    Status: Investigating We are investigating the issue for reports of GPT 5.5 performing worse for some users.

  2. monitoring May 16, 2026, 12:35 AM UTC

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

  3. resolved May 17, 2026, 12:15 AM UTC

    Status: Resolved All impacted services have now fully recovered.

Read the full incident report →

Minor May 14, 2026

Codex Cloud and Code Review experiencing high failure rate

Detected by Pingoru
May 14, 2026, 09:28 PM UTC
Resolved
May 14, 2026, 09:28 PM UTC
Duration
—
Timeline · 3 updates
  1. identified May 14, 2026, 08:58 PM UTC

    Status: Identified We have identified that users are experiencing elevated errors for Codex Cloud and Code Review. We are working on implementing a mitigation.

  2. investigating May 14, 2026, 09:18 PM UTC

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

  3. resolved May 14, 2026, 09:28 PM UTC

    Status: Resolved All impacted services have now fully recovered.

Read the full incident report →

Minor May 13, 2026

Issues accessing ChatGPT for logged-out users

Detected by Pingoru
May 13, 2026, 11:29 PM UTC
Resolved
May 13, 2026, 11:29 PM UTC
Duration
—
Affected: LoginLogin
Timeline · 3 updates
  1. investigating May 13, 2026, 11:05 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components Login (Full outage)

  2. monitoring May 13, 2026, 11:17 PM UTC

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

  3. resolved May 13, 2026, 11:29 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Login (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 →

Minor May 8, 2026

Elevated transcription failures affecting ChatGPT & Codex

Detected by Pingoru
May 08, 2026, 08:31 AM UTC
Resolved
May 08, 2026, 08:31 AM UTC
Duration
—
Affected: Codex WebCodex APICLIVS Code extensionVoice modeApp
Timeline · 6 updates
  1. identified May 07, 2026, 05:15 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 CLI (Degraded performance) App (Degraded performance) VS Code extension (Degraded performance) Codex API (Degraded performance) Voice mode (Degraded performance) Codex Web (Degraded performance)

  2. investigating May 07, 2026, 06:44 PM UTC

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

  3. investigating May 07, 2026, 08:17 PM UTC

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

  4. investigating May 07, 2026, 11:47 PM UTC

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

  5. monitoring May 08, 2026, 06:15 AM UTC

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

  6. resolved May 08, 2026, 08:31 AM UTC

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

Read the full incident report →

Minor May 7, 2026

Increased error rate with image generation in the API

Detected by Pingoru
May 07, 2026, 09:38 AM UTC
Resolved
May 07, 2026, 09:38 AM UTC
Duration
—
Affected: Images
Timeline · 2 updates
  1. monitoring May 07, 2026, 07:55 AM UTC

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

  2. resolved May 07, 2026, 09:38 AM UTC

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

Read the full incident report →

Minor May 5, 2026

Partial Disruption of ChatGPT Workspace Connector Write Actions

Detected by Pingoru
May 05, 2026, 05:00 PM UTC
Resolved
May 05, 2026, 05:00 PM UTC
Duration
—
Affected: Connectors/Apps
Timeline · 2 updates
  1. identified Apr 29, 2026, 09:59 PM UTC

    Status: Identified We have identified an issue where write actions for some ChatGPT workspace connectors were automatically disabled. We are actively working on restoring affected write actions. In the meantime, workspace admins can manually re-enable write permissions from the connector settings page (https://chatgpt.com/admin/ca > select connector > action control). Affected components Connectors/Apps (Degraded performance)

  2. resolved May 05, 2026, 05:00 PM UTC

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

Read the full incident report →

Minor May 4, 2026

Issue affecting some pages on the ChatGPT website

Detected by Pingoru
May 04, 2026, 05:10 PM UTC
Resolved
May 04, 2026, 05:10 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 04, 2026, 03:29 PM UTC

    Status: Investigating We’re investigating an issue causing the ChatGPT pricing and overview pages to be unavailable.

  2. identified May 04, 2026, 03:45 PM UTC

    Status: Identified We are still implementing the mitigation.

  3. monitoring May 04, 2026, 04:42 PM UTC

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

  4. resolved May 04, 2026, 05:10 PM UTC

    Status: Resolved All impacted services have now fully recovered.

Read the full incident report →

Minor May 1, 2026

Elevated error rate for Responses API

Detected by Pingoru
May 01, 2026, 03:38 PM UTC
Resolved
May 01, 2026, 03:38 PM UTC
Duration
—
Affected: Responses
Timeline · 3 updates
  1. investigating May 01, 2026, 02:25 PM UTC

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

  2. monitoring May 01, 2026, 03:04 PM UTC

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

  3. resolved May 01, 2026, 03:38 PM UTC

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

Read the full incident report →

Minor May 1, 2026

Elevated error rates for image generation

Detected by Pingoru
May 01, 2026, 02:53 PM UTC
Resolved
May 01, 2026, 02:53 PM UTC
Duration
—
Affected: ImagesImage Generation
Timeline · 3 updates
  1. identified May 01, 2026, 01:52 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 Images (Degraded performance) Image Generation (Degraded performance)

  2. monitoring May 01, 2026, 02:52 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Images (Degraded performance) Image Generation (Degraded performance)

  3. resolved May 01, 2026, 02:53 PM UTC

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

Read the full incident report →

Minor May 1, 2026

Elevated error rates affecting ChatGPT for some users in Europe

Detected by Pingoru
May 01, 2026, 04:02 AM UTC
Resolved
May 01, 2026, 04:02 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 01, 2026, 03:55 AM UTC

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

  2. monitoring May 01, 2026, 03:56 AM UTC

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

  3. resolved May 01, 2026, 04:02 AM UTC

    Status: Resolved All impacted services have now fully recovered.

Read the full incident report →