OpenAI

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-21 15:34 UTC

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

2. monitoring 2026-10-21 15:47 UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved 2026-10-21 16:44 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

1. identified 2026-10-21 13:42 UTC

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

2. investigating 2026-10-21 13:51 UTC

   We are investigating the issue for the listed services.

3. monitoring 2026-10-21 16:46 UTC

   We have applied the mitigation and are monitoring the recovery.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-21 02:26 UTC

   We are investigating the issue for the listed services.

2. monitoring 2026-10-21 02:48 UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved 2026-10-21 03:28 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-19 13:31 UTC

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

2. resolved 2026-10-19 14:14 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 16:29 UTC

   We are investigating an issue affecting logins and signups across all ChatGPT mobile applications. We will provide updates as we learn more.

2. investigating 2026-10-15 16:35 UTC

   We are investigating widespread feature degradation, including issues affecting logins and signups in the ChatGPT iOS/Android apps. We will provide updates as we learn more.

3. monitoring 2026-10-15 17:13 UTC

   We have applied the mitigation and are monitoring the recovery.

4. resolved 2026-10-15 18:56 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-14 17:00 UTC

   We have identified an issue causing delays in publishing organization cost data through the Costs API. API and ChatGPT usage are not affected, and other reporting channels remain available. We are working to restore normal data freshness.

2. identified 2026-10-14 17:02 UTC

   We have identified an issue causing delays in publishing organization cost data through the Costs API. API and ChatGPT usage are not affected, and other reporting channels remain available. We are working to restore normal data freshness.

3. identified 2026-10-14 20:00 UTC

   We have identified an issue causing delays in publishing organization cost data through the Costs API. A fix is in progress and currently undergoing testing. API and ChatGPT usage are not affected, and other reporting channels remain available. We are continuing work to restore...

4. monitoring 2026-10-15 22:36 UTC

   We have deployed a fix and are monitoring recovery. Costs data in the Compliance API remains delayed while we process the backlog. We will provide further updates as processing catches up.

5. resolved 2026-10-16 10:44 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 10:18 UTC

   We are investigating limited availability when using gpt-image-2.5-flare and gpt-image-2.5-sunburst in the API.

2. monitoring 2026-10-14 10:40 UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved 2026-10-14 10:58 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-14 07:05 UTC

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

2. identified 2026-10-14 09:19 UTC

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

3. resolved 2026-10-14 09:53 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 08:10 UTC

   We are investigating the issue for the listed services.

2. investigating 2026-10-13 08:18 UTC

   Degraded performance on GPT 6.1 Sol Codex and Work mode

3. investigating 2026-10-13 08:22 UTC

   We are investigating the issue for the listed services.

4. monitoring 2026-10-13 09:30 UTC

   We have applied the mitigation and are monitoring the recovery.

5. resolved 2026-10-13 16:36 UTC

   We have resolved the issue causing degraded performance with GPT-6.1 Sol in Codex and ChatGPT Work.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-09 21:48 UTC

   We are investigating an issue affecting some ChatGPT workspace administrators’ ability to view and manage plugin availability and settings. Some users may also see plugins as unavailable. We will provide another update as soon as we have more information.

2. monitoring 2026-10-09 22:52 UTC

   We are seeing recovery in workspace administrators’ ability to view and manage plugin availability and settings. We are monitoring to ensure service remains stable.

3. resolved 2026-10-09 23:26 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-09 21:00 UTC

   We have identified an issue affecting the ChatGPT Android app where users may see “This content is unavailable in this version of the app” instead of certain content. A fix is rolling out gradually in the latest Android version. Users can use ChatGPT on the web while we work to...

2. resolved 2026-10-10 00:26 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-09 17:23 UTC

   We have identified an issue causing delays in publishing organization cost data through the Costs API. API and ChatGPT usage are not affected, and other reporting channels remain available. We are working to restore normal data freshness.

2. identified 2026-10-09 17:27 UTC

   We have identified an issue causing delays in publishing Costs data through the Compliance API. The API Platform organization costs endpoint and ChatGPT usage are not affected, and other reporting channels remain available. We are working to restore normal data freshness.

3. identified 2026-10-09 18:46 UTC

   Some customers may continue to experience delayed Costs data through the Compliance API. ChatGPT usage and API Platform requests are not affected, and other reporting channels remain available. We have identified the cause and are continuing work to restore normal data...

4. monitoring 2026-10-09 22:03 UTC

   We have implemented a mitigation, and delayed Costs data is now processing through the Compliance API. Some customers may continue to see incomplete Costs data while the backlog catches up. We expect this catch-up process to continue through Sunday, October 11. ChatGPT usage and...

5. resolved 2026-10-12 16:02 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-08 03:17 UTC

   We are investigating the issue for the listed services.

2. resolved 2026-10-08 04:51 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-07 23:42 UTC

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

2. monitoring 2026-10-07 23:48 UTC

   We have applied the mitigation and are monitoring the recovery and no longer seeing any errors.

3. resolved 2026-10-08 00:03 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-07 17:21 UTC

   We are investigating the issue for the listed services.

2. resolved 2026-10-07 18:23 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 16:31 UTC

   We are investigating the issue for the listed services.

2. monitoring 2026-10-07 17:30 UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved 2026-10-07 18:06 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 02:00 UTC

   We are investigating the issue. Version 26.1002.51308 is affected

2. identified 2026-10-07 05:54 UTC

   we have identified the issue, working on rolling back to the previous version.

3. identified 2026-10-07 09:28 UTC

   We have identified the issue. We have released an updated app version for Linux and macOS. We are actively working to roll out the fix for Windows.

4. identified 2026-10-07 11:06 UTC

   We are actively working on a fixed app version for Windows.

5. resolved 2026-10-07 11:53 UTC

   We have released an updated app version with the fix for Linux, macOS and Windows. Affected users should update to the latest version.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 22:52 UTC

   We are investigating the issue for workspace agents, users may not see the responses during the issue time.

2. identified 2026-10-07 01:52 UTC

   We are implementing the mitigation.

3. monitoring 2026-10-07 02:45 UTC

   We have applied the mitigation and are monitoring the recovery.

4. resolved 2026-10-07 03:00 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 17:15 UTC

   We are investigating issues for agents api and computer use.

2. resolved 2026-10-06 20:00 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 15:23 UTC

   We are investigating the issue for the listed services.

2. identified 2026-10-06 15:29 UTC

   We are implementing the mitigation.

3. resolved 2026-10-06 17:50 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 13:35 UTC

   We are investigating the issue for the listed services.

2. monitoring 2026-10-06 13:53 UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved 2026-10-06 14:40 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 02:41 UTC

   We are investigating the issue for the listed services.

2. monitoring 2026-10-06 02:44 UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved 2026-10-06 03:17 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 00:40 UTC

   We are investigating the issue for the listed services.

2. monitoring 2026-10-06 00:40 UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved 2026-10-06 01:35 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-05 17:58 UTC

   We have identified that users are experiencing elevated errors within Codex Cloud. We are working on implementing a mitigation.

2. monitoring 2026-10-05 18:07 UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved 2026-10-06 00:01 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-05 16:58 UTC

   We are investigating elevated error rates affecting some ChatGPT conversations. Error rates are improving, and our team is continuing to assess recovery. We will share further updates as they become available.

2. monitoring 2026-10-05 17:55 UTC

   We have mitigated the issue affecting ChatGPT conversations and are monitoring recovery.

3. resolved 2026-10-06 00:01 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-05 15:50 UTC

   We are investigating the issue for the listed services.

2. monitoring 2026-10-05 19:33 UTC

   We have applied the mitigation and are monitoring the recovery.

3. resolved 2026-10-05 21:07 UTC

   All impacted services have now fully recovered.

Excerpts are shortened. Read the full incident on OpenAI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 12:44 UTC

   We are investigating the issue for the listed services. Some users may be unable to save changes or reconnect to live editing sessions.

2. resolved 2026-10-05 13:04 UTC

   The issue affecting saving and live editing in Pages has been resolved

Excerpts are shortened. Read the full incident on OpenAI's status page.