OpenAI Outage History

Started Jul 09, 2026, 07:44 PM UTC· resolved Jul 09, 2026, 08:42 PM UTC

1. investigating Jul 09, 2026, 07:44 PM UTC

   We are investigating an issue causing users to receive “Selected model is at capacity. Please try a different model.” errors across multiple models. We are working to identify the cause and restore normal service.

2. resolved Jul 09, 2026, 08:42 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jul 07, 2026, 11:29 AM UTC· resolved Jul 07, 2026, 04:12 PM UTC

1. investigating Jul 07, 2026, 11:29 AM UTC

   We are investigating elevated errors affecting image generation in ChatGPT. Some users may be unable to generate images.

2. identified Jul 07, 2026, 12:17 PM UTC

   We have identified the issue and are implementing a mitigation. Some users may continue to experience errors with image generation in ChatGPT while we implement the mitigation.

3. monitoring Jul 07, 2026, 02:40 PM UTC

   We have implemented a mitigation and are seeing error rates return to normal levels. We are monitoring the recovery, and some users may continue to experience errors with image generation in ChatGPT.

4. resolved Jul 07, 2026, 04:12 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 29, 2026, 07:00 AM UTC· resolved Jul 11, 2026, 02:11 AM UTC

1. investigating Jun 29, 2026, 07:00 AM UTC

   Core functionality has been restored but we are aware of known and ongoing issues in FedRAMP workspaces with Codex, workspace analytics, conversation search, searching for custom GPTs, ChatGPT user invites, and the Compliance Logs Platform download endpoint. We are working to resolve these issues and will share further updates we have more information available.

2. resolved Jul 11, 2026, 02:11 AM UTC

   Core functionality in FedRAMP workspaces has been restored, and the broader incident is resolved.

Read the full incident report →

Started Jun 27, 2026, 10:00 PM UTC· resolved Jun 28, 2026, 03:29 AM UTC

1. investigating Jun 27, 2026, 10:00 PM UTC

   We are investigating an issue affecting some users of the ChatGPT Windows desktop app on Windows. Affected users may see chat history or conversations fail to load, missing sidebar icons, or login/sign-up controls that do not respond. ChatGPT on web and mobile remains available as a workaround. We will share updates as we learn more.

2. resolved Jun 28, 2026, 03:29 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 26, 2026, 05:04 PM UTC· resolved Jun 29, 2026, 05:06 PM UTC

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

   We are investigating reports that Codex usage limits are being consumed faster than expected.

2. monitoring Jun 26, 2026, 11:24 PM UTC

   We have identified that some reports of Codex usage limits depleting faster than expected are related to our abuse and fraud prevention systems incorrectly rate limiting certain accounts. The impact appears limited, and we have not observed broader degradation to Codex usage. We are continuing to monitor the situation.

3. resolved Jun 29, 2026, 05:06 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 25, 2026, 04:02 PM UTC· resolved Jun 26, 2026, 02:18 AM UTC

1. identified Jun 25, 2026, 04:02 PM UTC

   A small number of Users have incorrectly cancelled subscription.

2. resolved Jun 26, 2026, 02:18 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 25, 2026, 05:51 AM UTC· resolved Jun 25, 2026, 11:03 AM UTC

1. investigating Jun 25, 2026, 05:51 AM UTC

   We are investigating the issue for the listed services.

2. monitoring Jun 25, 2026, 08:02 AM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 25, 2026, 11:03 AM UTC

   This is now resolved.

4. resolved Jun 25, 2026, 11:03 AM UTC

   This is now resolved

Read the full incident report →

Started Jun 24, 2026, 05:59 AM UTC· resolved Jun 24, 2026, 06:07 AM UTC

1. monitoring Jun 24, 2026, 05:59 AM UTC

   We have applied the mitigation and are monitoring the recovery.

2. resolved Jun 24, 2026, 06:07 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 23, 2026, 02:24 PM UTC· resolved Jun 23, 2026, 04:38 PM UTC

1. investigating Jun 23, 2026, 02:24 PM UTC

   We are investigating the issue for the listed services.

2. investigating Jun 23, 2026, 03:11 PM UTC

   We are investigating the issue for the listed services.

3. monitoring Jun 23, 2026, 03:47 PM UTC

   We have applied the mitigation and are monitoring the recovery.

4. resolved Jun 23, 2026, 04:38 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 19, 2026, 03:39 AM UTC· resolved Jun 19, 2026, 05:23 AM UTC

1. investigating Jun 19, 2026, 03:39 AM UTC

   We have identified an issue causing some users to be unable to access ChatGPT on chatgpt.com "chatgpt.com": http://chatgpt.com. We are working on implementing a mitigation. In the meantime, please try clearing the cache.

2. monitoring Jun 19, 2026, 05:11 AM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 19, 2026, 05:23 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 18, 2026, 08:55 AM UTC· resolved Jun 18, 2026, 11:55 AM UTC

1. investigating Jun 18, 2026, 08:55 AM UTC

   We are investigating the issue for the listed services.

2. monitoring Jun 18, 2026, 09:59 AM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 18, 2026, 11:55 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 18, 2026, 03:26 AM UTC· resolved Jun 18, 2026, 03:55 AM UTC

1. investigating Jun 18, 2026, 03:26 AM UTC

   We are investigating the issue for the listed services.

2. monitoring Jun 18, 2026, 03:43 AM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 18, 2026, 03:55 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 17, 2026, 05:20 PM UTC· resolved Jun 17, 2026, 06:23 PM UTC

1. identified Jun 17, 2026, 05:20 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 17, 2026, 05:44 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 17, 2026, 06:23 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 16, 2026, 10:32 AM UTC· resolved Jun 16, 2026, 01:48 PM UTC

1. identified Jun 16, 2026, 10:32 AM UTC

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

2. monitoring Jun 16, 2026, 01:32 PM UTC

   We have applied the mitigation and are monitoring the recovery.

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

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 16, 2026, 12:07 AM UTC· resolved Jun 16, 2026, 12:55 AM UTC

1. investigating Jun 16, 2026, 12:07 AM UTC

   We are investigating the issue for the listed services.

2. resolved Jun 16, 2026, 12:55 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 15, 2026, 09:23 PM UTC· resolved Jun 26, 2026, 11:07 PM UTC

1. identified Jun 15, 2026, 09:23 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 15, 2026, 10:16 PM UTC

   We are investigating the issue for the listed services.

3. investigating Jun 17, 2026, 01:24 AM UTC

   We are still investigating the issue for the listed services.

4. investigating Jun 18, 2026, 07:41 PM UTC

   We are still investigating the issue for the listed services.

5. resolved Jun 26, 2026, 11:07 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 15, 2026, 06:05 PM UTC· resolved Jun 15, 2026, 08:12 PM UTC

1. identified Jun 15, 2026, 06:05 PM UTC

   We have identified that users are experiencing an error when attempting to create an account using Google OAuth for the impacted services. We are working on implementing a mitigation.

2. resolved Jun 15, 2026, 08:12 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 11, 2026, 10:22 PM UTC· resolved Jun 12, 2026, 12:47 AM UTC

1. identified Jun 11, 2026, 10:22 PM UTC

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

2. investigating Jun 11, 2026, 10:59 PM UTC

   We are continuing to investigate the issue regarding elevated 431 errors and are working on the mitigation.

3. monitoring Jun 11, 2026, 11:25 PM UTC

   We have applied the mitigation and are monitoring the recovery.

4. resolved Jun 12, 2026, 12:47 AM UTC

   All impacted services have now fully recovered.

Read the full incident report →

Started Jun 11, 2026, 08:59 PM UTC· resolved Jun 11, 2026, 10:28 PM UTC

1. identified Jun 11, 2026, 08:59 PM UTC

   We have identified that users are experiencing elevated errors when using GPT 5.5 in Codex. We are working on implementing a mitigation.

2. monitoring Jun 11, 2026, 09:33 PM UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved Jun 11, 2026, 10:28 PM UTC

   All impacted services have now fully recovered.

Read the full incident report →

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 →