OpenAI Outage History

Started Jun 04, 2026, 07:12 PM UTC· resolved Jun 04, 2026, 07:52 PM UTC

1. identified Jun 04, 2026, 07:12 PM UTC

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

2. monitoring Jun 04, 2026, 07:36 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 04, 2026, 07:52 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 04, 2026, 02:57 AM UTC· resolved Jun 04, 2026, 04:37 AM UTC

1. identified Jun 04, 2026, 02:57 AM UTC

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

2. resolved Jun 04, 2026, 04:37 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 03, 2026, 04:58 AM UTC· resolved Jun 03, 2026, 11:09 AM UTC

1. investigating Jun 03, 2026, 04:58 AM UTC

   We are investigating the issue for the listed services.

2. investigating Jun 03, 2026, 05:11 AM UTC

   We are investigating the issue for the listed services.

3. investigating Jun 03, 2026, 05:12 AM UTC

   We are investigating the issue for the listed services.

4. investigating Jun 03, 2026, 05:22 AM UTC

   We are investigating the issue for the listed services.

5. investigating Jun 03, 2026, 05:42 AM UTC

   We are investigating the issue for the listed services.

6. investigating Jun 03, 2026, 06:16 AM UTC

   We are investigating the issue for the listed services.

7. investigating Jun 03, 2026, 06:34 AM UTC

   We are investigating the issue for the listed services.

8. investigating Jun 03, 2026, 06:50 AM UTC

   We are investigating the issue for the listed services.

9. investigating Jun 03, 2026, 07:11 AM UTC

   We have seen recovery on Codex, but there is continued low level impact on other services. We're continuing to work on mitigation.

10. monitoring Jun 03, 2026, 07:16 AM UTC

    We have applied the mitigation and are monitoring the recovery.

11. monitoring Jun 03, 2026, 07:55 AM UTC

    We have applied the mitigation and are monitoring the recovery.

12. monitoring Jun 03, 2026, 09:20 AM UTC

    We have applied the mitigation and are monitoring the recovery.

13. monitoring Jun 03, 2026, 10:21 AM UTC

    We have applied the mitigation and are monitoring the recovery.

14. resolved Jun 03, 2026, 11:09 AM UTC

    All impacted services have now fully recovered.

Read the full incident report →

Started Jun 02, 2026, 11:35 PM UTC· resolved Jun 03, 2026, 12:13 AM UTC

1. monitoring Jun 02, 2026, 11:35 PM UTC

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

2. resolved Jun 03, 2026, 12:13 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 02, 2026, 11:28 PM UTC· resolved Jun 03, 2026, 12:14 AM UTC

1. identified Jun 02, 2026, 11:28 PM UTC

   We are investigating elevated errors affecting some ChatGPT Pro users. Impacted users may see Thinking Failed when using the Pro model. We have identified the issue and are working to restore normal availability. We are seeing signs of recovery.

2. monitoring Jun 02, 2026, 11:36 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 03, 2026, 12:14 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 02, 2026, 12:04 PM UTC· resolved Jun 02, 2026, 01:16 PM UTC

1. investigating Jun 02, 2026, 12:04 PM UTC

   We have identified that Guest users are experiencing errors at an elevated rate when using ChatGPT, we are investigating internally.

2. monitoring Jun 02, 2026, 12:47 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 02, 2026, 01:16 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 01, 2026, 04:26 PM UTC· resolved Jun 01, 2026, 05:28 PM UTC

1. identified Jun 01, 2026, 04:26 PM UTC

   Limited capacity is causing ChatGPT availability to be reduced

2. monitoring Jun 01, 2026, 04:56 PM UTC

   ChatGPT success rates are back up to normal functionality

3. resolved Jun 01, 2026, 05:28 PM UTC

   The issue is resolved.

Read the full incident report →

Started May 29, 2026, 01:20 PM UTC· resolved May 29, 2026, 01:28 PM UTC

1. investigating May 29, 2026, 01:20 PM UTC

   We are investigating the issue for the listed services.

2. resolved May 29, 2026, 01:28 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 29, 2026, 03:18 AM UTC· resolved May 29, 2026, 04:58 AM UTC

1. investigating May 29, 2026, 03:18 AM UTC

   We are investigating the issue for the listed services.

2. monitoring May 29, 2026, 03:29 AM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved May 29, 2026, 04:58 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 29, 2026, 03:12 AM UTC· resolved May 29, 2026, 04:57 AM UTC

1. investigating May 29, 2026, 03:12 AM UTC

   We are investigating the issue for the listed services.

2. monitoring May 29, 2026, 03:28 AM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved May 29, 2026, 04:57 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 28, 2026, 08:46 PM UTC· resolved May 29, 2026, 01:29 AM UTC

1. investigating May 28, 2026, 08:46 PM UTC

   Some users may be unable to complete Business plan subscription checkouts on web and mobile web. We are investigating the issue for the listed services.

2. monitoring May 29, 2026, 12:09 AM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved May 29, 2026, 01:29 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 28, 2026, 05:27 AM UTC· resolved May 28, 2026, 05:27 AM UTC

1. resolved May 28, 2026, 05:27 AM UTC

   Resolved - Some users were unable to complete subscriptions on web and mobile. Affected users may have experienced the Subscribe button becoming unresponsive or encountered the error message submit_error_source:email during checkout.

Read the full incident report →

Started May 27, 2026, 05:57 PM UTC· resolved May 28, 2026, 06:59 AM UTC

1. identified May 27, 2026, 05:57 PM UTC

   We're investigating an issue causing Codex context compaction to be slower than expected.

2. investigating May 28, 2026, 12:14 AM UTC

   We are still investigating the issue for the listed services.

3. investigating May 28, 2026, 01:47 AM UTC

   We are still investigating the issue for the listed services.

4. identified May 28, 2026, 02:31 AM UTC

   We've identified a configuration error that caused Codex to be slow. We are working on implementing the mitigation at the moment.

5. monitoring May 28, 2026, 03:09 AM UTC

   We have applied the mitigation and are monitoring the recovery.

6. resolved May 28, 2026, 06:59 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 27, 2026, 04:24 PM UTC· resolved May 28, 2026, 03:59 AM UTC

1. investigating May 27, 2026, 04:24 PM UTC

   Android ChatGPT users may have trouble switching workspaces. We are investigating and will provide updates as more information becomes available.

2. resolved May 28, 2026, 03:59 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 27, 2026, 02:47 PM UTC· resolved May 27, 2026, 08:06 PM UTC

1. investigating May 27, 2026, 02:47 PM UTC

   We are investigating the issue for the listed services.

2. investigating May 27, 2026, 03:21 PM UTC

   We are investigating the issue for the listed services.

3. identified May 27, 2026, 03:45 PM UTC

   We are still implementing the mitigation.

4. monitoring May 27, 2026, 03:59 PM UTC

   We have applied the mitigation and are monitoring the recovery.

5. resolved May 27, 2026, 05:12 PM UTC

   All impacted services have now fully recovered.

6. monitoring May 27, 2026, 05:54 PM UTC

   We have received additional reports of elevated latency and errors after our previous recovery update. Mitigation remains in place, and we are monitoring recovery while we validate the remaining impact.

7. resolved May 27, 2026, 08:06 PM UTC

   The API issue has been Resolved.

Read the full incident report →

Started May 26, 2026, 08:27 PM UTC· resolved May 26, 2026, 08:30 PM UTC

1. identified May 26, 2026, 08:27 PM UTC

   We are aware of reports from users who are experiencing errors when attempting access Chat support the help center. For help, please email [email protected] "[email protected]": mailto:[email protected] We are working implementing the mitigation.

2. resolved May 26, 2026, 08:30 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 26, 2026, 01:59 PM UTC· resolved May 27, 2026, 06:01 AM UTC

1. investigating May 26, 2026, 01:59 PM UTC

   We are investigating the issue for the listed services.

2. identified May 26, 2026, 02:20 PM UTC

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

3. monitoring May 27, 2026, 05:31 AM UTC

   We have applied the mitigation and are monitoring the recovery.

4. resolved May 27, 2026, 04:16 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 22, 2026, 04:37 PM UTC· resolved May 23, 2026, 10:58 AM UTC

1. investigating May 22, 2026, 04:37 PM UTC

   We are investigating the issue for the listed services.

2. monitoring May 22, 2026, 07:16 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. monitoring May 22, 2026, 07:16 PM UTC

   We have applied the mitigation and are monitoring the recovery.

4. resolved May 23, 2026, 10:58 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 21, 2026, 10:05 PM UTC· resolved May 21, 2026, 11:22 PM UTC

1. identified May 21, 2026, 10:05 PM UTC

   We have identified that users are experiencing elevated latency and error rates for ChatGPT 5.5 Thinking. We are working on implementing a mitigation.

2. monitoring May 21, 2026, 10:25 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. monitoring May 21, 2026, 10:57 PM UTC

   We are continuing to monitor recovery.

4. resolved May 21, 2026, 11:22 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 21, 2026, 01:52 PM UTC· resolved May 21, 2026, 09:51 PM UTC

1. identified May 21, 2026, 01:52 PM UTC

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

2. monitoring May 21, 2026, 02:52 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved May 21, 2026, 03:23 PM UTC

   All impacted services have now fully recovered.

4. identified May 21, 2026, 08:17 PM UTC

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

5. monitoring May 21, 2026, 08:25 PM UTC

   We have applied the mitigation and are monitoring the recovery.

6. monitoring May 21, 2026, 08:44 PM UTC

   We are continuing to monitor recovery.

7. monitoring May 21, 2026, 09:02 PM UTC

   We are continuing to monitor the recovery.

8. monitoring May 21, 2026, 09:21 PM UTC

   We are continuing to monitor the recovery.

9. resolved May 21, 2026, 09:51 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 19, 2026, 11:32 PM UTC· resolved May 20, 2026, 12:37 AM UTC

1. identified May 19, 2026, 11:32 PM UTC

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

2. monitoring May 19, 2026, 11:38 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. monitoring May 19, 2026, 11:59 PM UTC

   We have applied the mitigation and are monitoring the recovery.

4. resolved May 20, 2026, 12:37 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 15, 2026, 04:11 PM UTC· resolved May 17, 2026, 12:15 AM UTC

1. investigating May 15, 2026, 04:11 PM UTC

   We are investigating the issue for reports of GPT 5.5 performing worse for some users.

2. monitoring May 16, 2026, 12:35 AM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved May 17, 2026, 12:15 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 14, 2026, 08:58 PM UTC· resolved May 14, 2026, 09:28 PM UTC

1. identified May 14, 2026, 08:58 PM UTC

   We have identified that users are experiencing elevated errors for Codex Cloud and Code Review. We are working on implementing a mitigation.

2. investigating May 14, 2026, 09:18 PM UTC

   We are investigating the issue for the listed services.

3. resolved May 14, 2026, 09:28 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 13, 2026, 11:05 PM UTC· resolved May 13, 2026, 11:29 PM UTC

1. investigating May 13, 2026, 11:05 PM UTC

   We are investigating the issue for the listed services.

2. monitoring May 13, 2026, 11:17 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved May 13, 2026, 11:29 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 13, 2026, 08:18 AM UTC· resolved May 13, 2026, 10:20 AM UTC

1. investigating May 13, 2026, 08:18 AM UTC

   We are currently experiencing elevated error rates for gpt-5.5.

2. identified May 13, 2026, 09:00 AM UTC

   High error rate on codex gpt 5.5 for free users. Degraded latency on gpt 5.5 for all codex users.

3. monitoring May 13, 2026, 09:34 AM UTC

   We have applied the mitigation and are monitoring the recovery.

4. resolved May 13, 2026, 10:20 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →