Part of OpenAI

Is OpenAI API down?

Last checked —
Current status
OpenAI API is up

No incidents right now.

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

OpenAI API is operational right now. Last checked —; the most recent incident resolved 4d ago.

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

Users who monitor OpenAI API also follow these AI services: Tungsten Automation EMEA DeepSeek Together AI Hugging Face Laserfiche Observe.AI Quest Retell AI Braintrust Cerebras View all 6,000+ providers
OpenAI API uptime 92.96% uptime · past 90 days
Mon Wed Fri
FebMarAprMay
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started May 13, 2026, 10:20 AM UTC · Resolved May 13, 2026, 10:20 AM UTC
    Codex WebCodex APICLIVS Code extensionApp
    Timeline · 4 updates
    • 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)

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

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

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

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

  2. Resolved
    Started May 13, 2026, 09:23 AM UTC · Resolved May 13, 2026, 09:23 AM UTC
    Audio
    Timeline · 3 updates
    • investigating · May 13, 2026, 06:28 AM UTC

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

    • investigating · May 13, 2026, 06:37 AM UTC

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

    • resolved · May 13, 2026, 09:23 AM UTC

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

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

  3. Resolved
    Started May 11, 2026, 05:59 PM UTC · Resolved May 11, 2026, 05:59 PM UTC
    ResponsesChat Completions
    Timeline · 4 updates
    • 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)

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

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

    • resolved · May 11, 2026, 05:59 PM UTC

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

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

  4. Resolved
    Started May 11, 2026, 05:35 AM UTC · Resolved May 11, 2026, 05:35 AM UTC
    Codex WebFile uploads
    Timeline · 3 updates
    • 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)

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

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

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

  5. Resolved
    Started May 09, 2026, 12:08 AM UTC · Resolved May 09, 2026, 12:08 AM UTC
    Responses
    Timeline · 2 updates
    • 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)

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

    Latest: 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 err…

See the full OpenAI API outage history

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

Browse OpenAI API outage history →

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

Outage history

Past 90 days · 35 incidents View full outage history →