Official incident history

  1. Degraded experience with ChatGPT app connections using CIMD

    Started: · Duration: 50 min
    Provider updates (3)
    1. Investigating “We are investigating the issue for the listed services.”
    2. Monitoring “We have applied the mitigation and are monitoring the recovery.”
    3. Resolved “All impacted services have now fully recovered.”
    Resolved
  2. Help Center Chat Support Degraded

    Started: · Duration: 33 min
    Provider updates (3)
    1. Investigating “We’re currently experiencing degraded performance with the Help Center chat support experience. While we work to resolve the issue, we recommend contacting our Support team via email at [support@openai.com](mailto:support@openai.com "support@openai.com") for assistance. We apologize for the inconvenience and will provide updates as they become available.”
    2. Monitoring “We have applied the mitigation and are monitoring the recovery.”
    3. Resolved “All impacted services have now fully recovered.”
    Resolved
  3. Delays in customer support responses

    Started: · Duration: 137 min
    Provider updates (4)
    1. Investigating “We are investigating technical issues affecting our customer support systems. Customers may experience longer than usual response times. We are working to restore normal operations.”
    2. Identified “A fix is being implemented for the issue affecting our support systems. Customers may continue to experience delays in receiving support responses. We will provide further updates as recovery progresses.”
    3. Monitoring “We have applied the mitigation and are monitoring the recovery.”
    4. Resolved “All impacted services have now fully recovered.”
    Resolved
  4. New Ad Accounts failing to provision admins

    Started: · Duration: 271 min
    Provider updates (3)
    1. Identified “We have identified that new ad accounts are failing to assign their creator admin. We are investigating the issue.”
    2. Monitoring “We have applied the mitigation and are monitoring the recovery.”
    3. Resolved “All impacted services have now fully recovered.”
    Resolved
  5. Degraded Performance of Dots on Enterprise

    Started: · Duration: 124 min
    Provider updates (3)
    1. Investigating “Users are experiencing failures sending messages to dots.”
    2. Identified “Our teams have identified the issue and are actively implementing a mitigation. At this time the majority of impact is affecting enterprise customers.”
    3. Resolved “All impacted services have now fully recovered.”
    Resolved
  6. Elevated ChatGPT conversation and Responses API errors

    Started: · Duration: 392 min
    Provider updates (3)
    1. Investigating “This is impacting users in India, Japan, and Korea. We are investigating the issue for the listed services.”
    2. Monitoring “This is impacting users in India, Japan, and Korea. We have applied the mitigation and are monitoring the recovery.”
    3. Resolved “All impacted services have now fully recovered.”
    Resolved
  7. Authentication errors for some users

    Started: · Duration: 60 min
    Provider updates (2)
    1. Investigating “Some users near Illinois experienced authentication errors with the API, ChatGPT, and Codex.”
    2. Resolved “On October 20, from 9:35 to 10:35 a.m. PDT, some users near Illinois experienced authentication errors with the API, ChatGPT, and Codex. We rolled back a configuration change, and service was restored.”
    Resolved
  8. Elevated FedRAMP API error rates for Astra and Sol

    Started: · Duration: 353 min
    Provider updates (4)
    1. Identified “We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.”
    2. Investigating “We are investigating the issue for the listed services.”
    3. Monitoring “We have applied the mitigation and are monitoring the recovery.”
    4. Resolved “All impacted services have now fully recovered.”
    Resolved
  9. Elevated error rates for gpt-5.6-luna API requests

    Started: · Duration: 69 min
    Provider updates (3)
    1. Identified “We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.”
    2. Monitoring “We have applied the mitigation and are monitoring the recovery.”
    3. Resolved “All impacted services have now fully recovered.”
    Resolved
  10. Degraded performance in ChatGPT, Codex, and APIs

    Started: · Duration: 62 min
    Provider updates (3)
    1. Investigating “We are investigating the issue for the listed services.”
    2. Monitoring “We have applied the mitigation and are monitoring the recovery.”
    3. Resolved “All impacted services have now fully recovered.”
    Resolved
  11. File Download errors

    Started: · Duration: 42 min
    Provider updates (2)
    1. Identified “We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.”
    2. Resolved “All impacted services have now fully recovered.”
    Resolved
  12. Delayed Costs data in the Compliance API

    Started: · Duration: 2504 min
    Provider updates (3)
    1. Identified “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. Monitoring “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.”
    3. Resolved “All impacted services have now fully recovered.”
    Resolved
  13. Widespread feature degradation

    Started: · Duration: 147 min
    Provider updates (3)
    1. Investigating “We are investigating an issue affecting logins and signups across all ChatGPT mobile applications. We will provide updates as we learn more.”
    2. Monitoring “We have applied the mitigation and are monitoring the recovery.”
    3. Resolved “All impacted services have now fully recovered.”
    Resolved
  14. Limited availability on gpt-image-2.5-flare and gpt-image-2.5-sunburst

    Started: · Duration: 40 min
    Provider updates (3)
    1. Investigating “We are investigating limited availability when using gpt-image-2.5-flare and gpt-image-2.5-sunburst in the API.”
    2. Monitoring “We have applied the mitigation and are monitoring the recovery.”
    3. Resolved “All impacted services have now fully recovered.”
    Resolved
  15. Degraded performance in Codex and ChatGPT Work

    Started: · Duration: 167 min
    Provider updates (2)
    1. Identified “We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.”
    2. Resolved “All impacted services have now fully recovered.”
    Resolved
  16. Degraded performance in GPT-6.1 Sol Codex and Work mode

    Started: · Duration: 507 min
    Provider updates (3)
    1. Investigating “We are investigating the issue for the listed services.”
    2. Monitoring “We have applied the mitigation and are monitoring the recovery.”
    3. Resolved “We have resolved the issue causing degraded performance with GPT-6.1 Sol in Codex and ChatGPT Work.”
    Resolved
  17. Delayed Costs data in the Compliance API

    Started: · Duration: 4239 min
    Provider updates (3)
    1. Identified “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. Monitoring “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 API Platform requests remain unaffected. We are monitoring recovery.”
    3. Resolved “All impacted services have now fully recovered.”
    Resolved
  18. Some ChatGPT content may be unavailable on Android

    Started: · Duration: 206 min
    Provider updates (2)
    1. Identified “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 restore the experience for older app versions.”
    2. Resolved “All impacted services have now fully recovered.”
    Resolved
  19. Workspace admins may be unable to manage plugins

    Started: · Duration: 98 min
    Provider updates (3)
    1. Investigating “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 “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 “All impacted services have now fully recovered.”
    Resolved
  20. Some APAC users are seeing errors in ChatGPT Work, conversations, and GPTs.

    Started: · Duration: 94 min
    Provider updates (2)
    1. Investigating “We are investigating the issue for the listed services.”
    2. Resolved “All impacted services have now fully recovered.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Official
OpenAI Status ↗ · All Systems Operational · Oct 25, 01:36 AM UTC
Korantix
HTTP 403 · 873 ms · Oct 25, 01:34 AM UTC

Why this assessment

  • Provider reports no active incident.
  • Korantix reached the endpoint (HTTP 403, 873 ms). This only shows that the endpoint answered.
  • 873 ms is within this service's usual range (median 466 ms, p95 680 ms over 656 checks).

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Official4 min agoYes — recent
Korantix6 min agoYes — recent

Technical details

Affected components (provider)

The provider lists no degraded components.

Official status page ↗