Is OpenAI down?

Last checked 9m ago
Current status
OpenAI is up

No incidents right now.

Official status page: https://status.openai.com · Polled every 5 minutes · 31 components tracked

OpenAI is operational right now. Last checked 9m ago; the most recent incident resolved 2d ago.

Real-time OpenAI status, recent outages, and incident history — pulled directly from OpenAI's official status page at https://status.openai.com every 5 minutes. Pingoru tracks 31 OpenAI services and has captured 90 incidents in the last 90 days (90.29% uptime). Get email, Slack, Discord, or webhook alerts the moment OpenAI reports a new incident — free for 5 monitors, no credit card.

Users who monitor OpenAI also follow these Development services: Bitbucket Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud Rollbar View all 6,000+ providers
OpenAI uptime 90.29% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jun 12, 2026, 12:47 AM UTC · Resolved Jun 12, 2026, 12:47 AM UTC
    LoginResponsesFine-tuningImagesBatchAudioModerationsSoraEmbeddingsChat Completions
    Timeline · 4 updates
    • 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)

    • 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)

    • 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)

    • 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)

    Latest: Status: Resolved All impacted services have now fully recovered. Affected components Chat Completions (Operational) Realtime (Operational) Files (Operational) Embeddings (Operation…

  2. Resolved
    Started Jun 11, 2026, 10:28 PM UTC · Resolved Jun 11, 2026, 10:28 PM UTC
    Codex WebCodex APICLIVS Code extensionApp
    Timeline · 3 updates
    • 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)

    • 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)

    • 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)

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

  3. Resolved
    Started Jun 11, 2026, 02:04 PM UTC · Resolved Jun 11, 2026, 02:04 PM UTC
    Conversations
    Timeline · 2 updates
    • 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)

    • resolved · Jun 11, 2026, 02:04 PM UTC

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

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

  4. Resolved
    Started Jun 08, 2026, 07:40 AM UTC · Resolved Jun 08, 2026, 07:40 AM UTC
    Conversations
    Timeline · 4 updates
    • 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)

    • resolved · Jun 07, 2026, 07:25 PM UTC

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

    • investigating · Jun 08, 2026, 07:21 AM UTC

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

    • resolved · Jun 08, 2026, 07:40 AM UTC

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

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

  5. Resolved
    Started Jun 07, 2026, 06:06 PM UTC · Resolved Jun 07, 2026, 06:06 PM UTC
    Conversations
    Timeline · 2 updates
    • identified · Jun 07, 2026, 03:08 PM UTC

      Status: Identified We have identified the issue for the listed services. We are currently working on a mitigation. Affected components Conversations (Degraded performance)

    • resolved · Jun 07, 2026, 06:06 PM UTC

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

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

See the full OpenAI outage history

85 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse OpenAI outage history →

Or sign up free to get alerts when OpenAI breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 90 incidents View full outage history →