ChatGPT Outage History

Started Jun 11, 2026, 01:03 PM UTC· resolved Jun 11, 2026, 02:04 PM UTC

1. identified Jun 11, 2026, 01:03 PM UTC

   We have identified that some ChatGPT Free and Go users are experiencing elevated errors when using conversations. We are working to implement a mitigation.

2. resolved Jun 11, 2026, 02:04 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 07, 2026, 07:19 PM UTC· resolved Jun 08, 2026, 07:40 AM UTC

1. identified Jun 07, 2026, 07:19 PM UTC

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

2. resolved Jun 07, 2026, 07:25 PM UTC

   All impacted services have now fully recovered.

3. investigating Jun 08, 2026, 07:21 AM UTC

   We are investigating the issue for the listed services.

4. resolved Jun 08, 2026, 07:40 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 05, 2026, 05:59 PM UTC· resolved Jun 05, 2026, 07:04 PM UTC

1. identified Jun 05, 2026, 05:59 PM UTC

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

2. investigating Jun 05, 2026, 06:04 PM UTC

   We are investigating the issue for the listed services.

3. monitoring Jun 05, 2026, 07:04 PM UTC

   We have applied the mitigation and are monitoring the recovery.

4. resolved Jun 05, 2026, 07:04 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 05, 2026, 02:48 PM UTC· resolved Jun 05, 2026, 03:58 PM UTC

1. investigating Jun 05, 2026, 02:48 PM UTC

   We are investigating the issue for the listed services.

2. monitoring Jun 05, 2026, 03:24 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 05, 2026, 03:58 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 05, 2026, 02:11 PM UTC· resolved Jun 05, 2026, 03:37 PM UTC

1. investigating Jun 05, 2026, 02:11 PM UTC

   We are investigating the issue for the listed services.

2. identified Jun 05, 2026, 02:36 PM UTC

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

3. monitoring Jun 05, 2026, 03:28 PM UTC

   We have applied the mitigation and are monitoring the recovery.

4. resolved Jun 05, 2026, 03:37 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 05, 2026, 01:26 PM UTC· resolved Jun 06, 2026, 06:16 AM UTC

1. investigating Jun 05, 2026, 01:26 PM UTC

   We are investigating the issue for the listed services.

2. identified Jun 05, 2026, 02:20 PM UTC

   We have identified the issue impacting account access for some users, and we are working on a fix.

3. identified Jun 05, 2026, 02:52 PM UTC

   We are still implementing the mitigation.

4. identified Jun 05, 2026, 03:19 PM UTC

   An issue caused some user accounts to be incorrectly suspended. We’re restoring account access and working through related subscription and credit impacts for affected users.

5. resolved Jun 05, 2026, 04:09 PM UTC

   All impacted services have now fully recovered.

6. monitoring Jun 05, 2026, 07:09 PM UTC

   We’ve restored account access for users. The team is working through related subscription and credit impacts for affected users.

7. monitoring Jun 05, 2026, 07:47 PM UTC

   The team is still working through related subscription and credit impacts for affected users. Impacted users will be receiving an email shortly.

8. monitoring Jun 05, 2026, 08:53 PM UTC

   All users impacted should have received an email with more information. The team is monitoring for additional changes.

9. monitoring Jun 05, 2026, 09:19 PM UTC

   The team is uncovering some additional impacted users and is still working through related subscription and credit impacts for affected users. Impacted users will be receiving an email shortly.

10. resolved Jun 06, 2026, 06:16 AM UTC

    Incorrectly suspended users have been restored access and received an email about their account and subscription information, if relevant. Impacted services have 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: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, 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, 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 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 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 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 11, 2026, 01:23 AM UTC· resolved May 11, 2026, 05:35 AM UTC

1. investigating May 11, 2026, 01:23 AM UTC

   We are investigating the issue for the listed services.

2. monitoring May 11, 2026, 03:23 AM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved May 11, 2026, 05:35 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 07, 2026, 05:15 PM UTC· resolved May 08, 2026, 08:31 AM UTC

1. identified May 07, 2026, 05:15 PM UTC

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

2. investigating May 07, 2026, 06:44 PM UTC

   We are investigating the issue for the listed services.

3. investigating May 07, 2026, 08:17 PM UTC

   We are investigating the issue for the listed services.

4. investigating May 07, 2026, 11:47 PM UTC

   We are investigating the issue for the listed services.

5. monitoring May 08, 2026, 06:15 AM UTC

   We have applied the mitigation and are monitoring the recovery.

6. resolved May 08, 2026, 08:31 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started May 01, 2026, 01:52 PM UTC· resolved May 01, 2026, 02:53 PM UTC

1. identified May 01, 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 01, 2026, 02:52 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved May 01, 2026, 02:53 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Apr 29, 2026, 09:59 PM UTC· resolved May 05, 2026, 05:00 PM UTC

1. identified Apr 29, 2026, 09:59 PM UTC

   We have identified an issue where write actions for some ChatGPT workspace connectors were automatically disabled. We are actively working on restoring affected write actions. In the meantime, workspace admins can manually re-enable write permissions from the connector settings page (https://chatgpt.com/admin/ca > select connector > action control).

2. resolved May 05, 2026, 05:00 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Apr 29, 2026, 09:01 PM UTC· resolved Apr 29, 2026, 10:24 PM UTC

1. identified Apr 29, 2026, 09:01 PM UTC

   We have identified that ChatGPT Go users are experiencing elevated errors. We are working on implementing a mitigation.

2. identified Apr 29, 2026, 09:25 PM UTC

   We have identified elevated error rates impacting ChatGPT Go (5.3 Thinking). Other ChatGPT Go models are not affected at this time. The team is actively working on a mitigation.

3. monitoring Apr 29, 2026, 09:59 PM UTC

   We have applied the mitigation and are monitoring the recovery.

4. resolved Apr 29, 2026, 10:24 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →