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 June 17, 2026

Errors with conversations on Android and iOS devices

Detected by Pingoru
Jun 17, 2026, 06:23 PM UTC
Resolved
Jun 17, 2026, 06:23 PM UTC
Duration
—
Affected: Conversations
Timeline · 3 updates
  1. identified Jun 17, 2026, 05:20 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 Conversations (Partial outage)

  2. monitoring Jun 17, 2026, 05:44 PM UTC

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

  3. resolved Jun 17, 2026, 06:23 PM UTC

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

OAuth Account Creation / Login Error

Detected by Pingoru
Jun 15, 2026, 08:12 PM UTC
Resolved
Jun 15, 2026, 08:12 PM UTC
Duration
—
Affected: Login
Timeline · 2 updates
  1. identified Jun 15, 2026, 06:05 PM UTC

    Status: Identified We have identified that users are experiencing an error when attempting to create an account using Google OAuth for the impacted services. We are working on implementing a mitigation. Affected components Login (Degraded performance) Login (Degraded performance)

  2. resolved Jun 15, 2026, 08:12 PM UTC

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

Disruption in service availabilty for Free and Go users

Detected by Pingoru
Jun 11, 2026, 02:04 PM UTC
Resolved
Jun 11, 2026, 02:04 PM UTC
Duration
—
Affected: Conversations
Timeline · 2 updates
  1. identified Jun 11, 2026, 01:03 PM UTC

    Status: Identified We have identified that some ChatGPT Free and Go users are experiencing elevated errors when using conversations. We are working to implement a mitigation. Affected components Conversations (Degraded performance)

  2. resolved Jun 11, 2026, 02:04 PM UTC

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

Read the full incident report →

Minor June 8, 2026

Disruption in service availabilty for Go users

Detected by Pingoru
Jun 08, 2026, 07:40 AM UTC
Resolved
Jun 08, 2026, 07:40 AM UTC
Duration
—
Affected: Conversations
Timeline · 4 updates
  1. identified Jun 07, 2026, 07:19 PM UTC

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

  2. resolved Jun 07, 2026, 07:25 PM UTC

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

  3. investigating Jun 08, 2026, 07:21 AM UTC

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

  4. resolved Jun 08, 2026, 07:40 AM UTC

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

Read the full incident report →

Minor June 5, 2026

Voice mode availability impacted

Detected by Pingoru
Jun 05, 2026, 07:04 PM UTC
Resolved
Jun 05, 2026, 07:04 PM UTC
Duration
—
Affected: Voice mode
Timeline · 4 updates
  1. identified Jun 05, 2026, 05:59 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 Voice mode (Degraded performance)

  2. investigating Jun 05, 2026, 06:04 PM UTC

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

  3. monitoring Jun 05, 2026, 07:04 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Voice mode (Operational)

  4. resolved Jun 05, 2026, 07:04 PM UTC

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

Read the full incident report →

Minor June 5, 2026

Users unable to sign in using Microsoft personal accounts

Detected by Pingoru
Jun 05, 2026, 03:58 PM UTC
Resolved
Jun 05, 2026, 03:58 PM UTC
Duration
—
Affected: LoginLogin
Timeline · 3 updates
  1. investigating Jun 05, 2026, 02:48 PM UTC

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

  2. monitoring Jun 05, 2026, 03:24 PM UTC

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

  3. resolved Jun 05, 2026, 03:58 PM UTC

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

Read the full incident report →

Minor June 5, 2026

Elevated error rates for Free users in conversations

Detected by Pingoru
Jun 05, 2026, 03:37 PM UTC
Resolved
Jun 05, 2026, 03:37 PM UTC
Duration
—
Affected: Conversations
Timeline · 4 updates
  1. investigating Jun 05, 2026, 02:11 PM UTC

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

  2. identified Jun 05, 2026, 02:36 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 Conversations (Degraded performance)

  3. monitoring Jun 05, 2026, 03:28 PM UTC

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

  4. resolved Jun 05, 2026, 03:37 PM UTC

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

Read the full incident report →

Minor June 4, 2026

Image API requests failing with 401s

Detected by Pingoru
Jun 04, 2026, 07:52 PM UTC
Resolved
Jun 04, 2026, 07:52 PM UTC
Duration
—
Affected: Images
Timeline · 3 updates
  1. identified Jun 04, 2026, 07:12 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)

  2. monitoring Jun 04, 2026, 07:36 PM UTC

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

  3. resolved Jun 04, 2026, 07:52 PM UTC

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

Elevated errors for ChatGPT Pro

Detected by Pingoru
Jun 03, 2026, 12:14 AM UTC
Resolved
Jun 03, 2026, 12:14 AM UTC
Duration
—
Affected: LoginChatGPT AtlasFile uploadsConversationsAgentVoice modeConnectors/AppsCompliance APIDeep ResearchSearchGPTsImage GenerationLogin
Timeline · 3 updates
  1. identified Jun 02, 2026, 11:28 PM UTC

    Status: Identified We are investigating elevated errors affecting some ChatGPT Pro users. Impacted users may see Thinking Failed when using the Pro model. We have identified the issue and are working to restore normal availability. We are seeing signs of recovery. Affected components Connectors/Apps (Degraded performance) ChatGPT Atlas (Degraded performance) Login (Degraded performance) File uploads (Degraded performance) Search (Degraded performance) Image Generation (Degraded performance) GPTs (Degraded performance) Deep Research (Degraded performance) Voice mode (Degraded performance) Conversations (Degraded performance) Compliance API (Degraded performance) Agent (Degraded performance)

  2. monitoring Jun 02, 2026, 11:36 PM UTC

    Status: Monitoring We have applied the mitigation and are monitoring the recovery. Affected components Conversations (Degraded performance) Compliance API (Degraded performance) Image Generation (Degraded performance) Deep Research (Degraded performance) Voice mode (Degraded performance) Search (Degraded performance) GPTs (Degraded performance) Agent (Degraded performance) Connectors/Apps (Degraded performance) ChatGPT Atlas (Degraded performance) Login (Degraded performance) File uploads (Degraded performance)

  3. resolved Jun 03, 2026, 12:14 AM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components Search (Operational) Conversations (Operational) Agent (Operational) Deep Research (Operational) Connectors/Apps (Operational) Login (Operational) File uploads (Operational) Compliance API (Operational) Image Generation (Operational) GPTs (Operational) ChatGPT Atlas (Operational) Voice mode (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 June 2, 2026

Guest users are experiencing elevated error rate when using ChatGPT conversations.

Detected by Pingoru
Jun 02, 2026, 01:16 PM UTC
Resolved
Jun 02, 2026, 01:16 PM UTC
Duration
—
Affected: Conversations
Timeline · 3 updates
  1. investigating Jun 02, 2026, 12:04 PM UTC

    Status: Investigating We have identified that Guest users are experiencing errors at an elevated rate when using ChatGPT, we are investigating internally. Affected components Conversations (Degraded performance)

  2. monitoring Jun 02, 2026, 12:47 PM UTC

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

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

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

Read the full incident report →

Minor June 1, 2026

Decreased ChatGPT availability for Free users

Detected by Pingoru
Jun 01, 2026, 05:28 PM UTC
Resolved
Jun 01, 2026, 05:28 PM UTC
Duration
—
Affected: Conversations
Timeline · 3 updates
  1. identified Jun 01, 2026, 04:26 PM UTC

    Status: Identified Limited capacity is causing ChatGPT availability to be reduced Affected components Conversations (Partial outage)

  2. monitoring Jun 01, 2026, 04:56 PM UTC

    Status: Monitoring ChatGPT success rates are back up to normal functionality Affected components Conversations (Partial outage)

  3. resolved Jun 01, 2026, 05:28 PM UTC

    Status: Resolved The issue is resolved. Affected components Conversations (Operational)

Read the full incident report →

Minor May 29, 2026

Users May Experience Issues Accessing ChatGPT

Detected by Pingoru
May 29, 2026, 01:28 PM UTC
Resolved
May 29, 2026, 01:28 PM UTC
Duration
—
Affected: LoginChatGPT AtlasFile uploadsConversationsAgentVoice modeConnectors/AppsCompliance APIDeep ResearchSearchGPTsImage GenerationLogin
Timeline · 2 updates
  1. investigating May 29, 2026, 01:20 PM UTC

    Status: Investigating We are investigating the issue for the listed services. Affected components ChatGPT Atlas (Degraded performance) Login (Degraded performance) Voice mode (Degraded performance) Image Generation (Degraded performance) Agent (Degraded performance) Deep Research (Degraded performance) Connectors/Apps (Degraded performance) File uploads (Degraded performance) Search (Degraded performance) Conversations (Degraded performance) Compliance API (Degraded performance) GPTs (Degraded performance)

  2. resolved May 29, 2026, 01:28 PM UTC

    Status: Resolved All impacted services have now fully recovered. Affected components ChatGPT Atlas (Operational) Login (Operational) Compliance API (Operational) Image Generation (Operational) GPTs (Operational) Agent (Operational) File uploads (Operational) Voice mode (Operational) Search (Operational) Conversations (Operational) Deep Research (Operational) Connectors/Apps (Operational)

Read the full incident report →

Minor May 29, 2026

Users may encounter issues with conversations

Detected by Pingoru
May 29, 2026, 04:58 AM UTC
Resolved
May 29, 2026, 04:58 AM UTC
Duration
—
Affected: Conversations
Timeline · 3 updates
  1. investigating May 29, 2026, 03:18 AM UTC

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

  2. monitoring May 29, 2026, 03:29 AM UTC

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

  3. resolved May 29, 2026, 04:58 AM UTC

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

Read the full incident report →

Minor May 29, 2026

Users may encounter issues logging in or creating an account

Detected by Pingoru
May 29, 2026, 04:57 AM UTC
Resolved
May 29, 2026, 04:57 AM UTC
Duration
—
Affected: LoginLogin
Timeline · 3 updates
  1. investigating May 29, 2026, 03:12 AM UTC

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

  2. monitoring May 29, 2026, 03:28 AM UTC

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

  3. resolved May 29, 2026, 04:57 AM UTC

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

Read the full incident report →

Minor May 29, 2026

Business plan subscription checkout issues on web and mobile web

Detected by Pingoru
May 29, 2026, 01:29 AM UTC
Resolved
May 29, 2026, 01:29 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 28, 2026, 08:46 PM UTC

    Status: Investigating Some users may be unable to complete Business plan subscription checkouts on web and mobile web. We are investigating the issue for the listed services.

  2. monitoring May 29, 2026, 12:09 AM UTC

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

  3. resolved May 29, 2026, 01:29 AM UTC

    Status: Resolved All impacted services have now fully recovered.

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 →