OpenAI incident

Codex unresponsive

Minor Resolved View vendor source →
Started
Mar 11, 2026, 04:17 PM UTC
Resolved
Mar 11, 2026, 04:17 PM UTC
Duration
—
Detected by Pingoru
Mar 11, 2026, 04:17 PM UTC

Affected components

Codex Web

Update timeline

  1. investigating Mar 09, 2026, 03:09 PM UTC

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

  2. identified Mar 09, 2026, 05:44 PM 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)

  3. monitoring Mar 09, 2026, 08:45 PM UTC

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

  4. resolved Mar 09, 2026, 10:30 PM UTC

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

  5. identified Mar 10, 2026, 09:03 AM UTC

    Status: Identified We are investigating renewed user reports of this issue. We have identified a likely root cause and are actively implementing mitigations to reduce impact while we work on a full fix. Affected components Codex Web (Degraded performance)

  6. resolved Mar 10, 2026, 11:39 AM UTC

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

  7. identified Mar 10, 2026, 12:56 PM UTC

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

  8. identified Mar 10, 2026, 02:22 PM UTC

    Status: Identified We are still working on implementing a mitigation. Affected components Codex Web (Degraded performance)

  9. identified Mar 10, 2026, 04:04 PM UTC

    Status: Identified We are observing improvements while we continue to implement a mitigation. Affected components Codex Web (Degraded performance)

  10. identified Mar 10, 2026, 06:41 PM UTC

    Status: Identified We are still working on implementing a mitigation. Affected components Codex Web (Degraded performance)

  11. identified Mar 10, 2026, 09:37 PM UTC

    Status: Identified We are still working on implementing a mitigation. Affected components Codex Web (Degraded performance)

  12. identified Mar 10, 2026, 11:16 PM UTC

    Status: Identified We are still working on implementing a mitigation. Affected components Codex Web (Degraded performance)

  13. identified Mar 11, 2026, 02:50 AM UTC

    Status: Identified We are still working on implementing a mitigation. Affected components Codex Web (Degraded performance)

  14. monitoring Mar 11, 2026, 05:31 AM UTC

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

  15. resolved Mar 11, 2026, 04:17 PM UTC

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

Looking to track OpenAI downtime and outages?

Pingoru polls OpenAI's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when OpenAI reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track OpenAI alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring OpenAI for free

5 free monitors · No credit card required