Codex unresponsive

Update timeline

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

   We are investigating the issue for the listed services.

2. identified Mar 09, 2026, 05:44 PM UTC

   We have identified that users are experiencing elevated latency for the impacted services. We are working on implementing a mitigation.

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

   We have applied the mitigation and are monitoring the recovery.

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

   All impacted services have now fully recovered.

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

   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.

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

   All impacted services have now fully recovered.

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

   We have identified that some users are still experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

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

   We are still working on implementing a mitigation.

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

   We are observing improvements while we continue to implement a mitigation.

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

    We are still working on implementing a mitigation.

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

    We are still working on implementing a mitigation.

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

    We are still working on implementing a mitigation.

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

    We are still working on implementing a mitigation.

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

    We have applied the mitigation and are monitoring the recovery.

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

    All impacted services have now fully recovered.