OpenAI incident

Issues with Increased Codex Usage Rate

Minor Resolved View vendor source →
Started
Mar 07, 2026, 01:00 AM UTC
Resolved
Mar 07, 2026, 01:00 AM UTC
Duration
Detected by Pingoru
Mar 07, 2026, 01:00 AM UTC

Affected components

Codex Web

Update timeline

  1. identified Mar 06, 2026, 06:35 PM UTC

    Status: Identified We have identified an issue causing Codex usage to be consumed faster than expected, which may cause some users to hit rate limits sooner than intended. We are working on implementing a mitigation. Affected components Codex Web (Degraded performance)

  2. identified Mar 06, 2026, 07:20 PM UTC

    Status: Identified We have identified an issue causing Codex usage to be consumed faster than expected, which may cause some users to hit rate limits sooner than intended. We are working on implementing a mitigation. Affected components Codex Web (Degraded performance)

  3. identified Mar 06, 2026, 10:08 PM UTC

    Status: Identified We have identified an issue causing Codex usage to be consumed faster than expected, which may cause some users to hit rate limits sooner than intended. We are working on implementing a mitigation. Affected components Codex Web (Degraded performance)

  4. resolved Mar 07, 2026, 01:00 AM 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