Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 2 — 104-day disruption

May 2, 04:38 AM → Aug 14, 07:00 AM · 104d 2h · medium

On May 2, 2026, an incident affecting ChatGPT was detected through elevated user-report volume. Users may have experienced issues with the service. The incident was resolved on August 14, 2026.

Peak reports
10
in 15 min
Total reports
133
during the incident
Duration
104d 2h
tracked by PulseWatch

Impact

Users reported a range of issues with ChatGPT during the incident. The most frequently reported problems included slow or unresponsive service, as well as issues related to AI API functionality and general API access. A total of 133 user reports were received, with no specific regional impact recorded.

Top reported issues

  • Slow / unresponsive112
  • AI API issues18
  • API issues3

Incident timeline

  1. May 2, 04:38 AM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 04:43 AM

    Status updated: major issue

  3. May 2, 04:53 AM

    Status updated: possible issue

  4. May 2, 04:58 AM

    Status updated: major issue

  5. May 2, 05:08 AM

    Status updated: possible issue

  6. May 2, 05:13 AM

    Status updated: major issue

  7. May 2, 05:23 AM

    Status updated: possible issue

  8. May 2, 05:28 AM

    Status updated: major issue

  9. May 2, 05:38 AM

    Status updated: possible issue

  10. May 2, 05:43 AM

    Status updated: major issue

  11. May 2, 05:53 AM

    Status updated: possible issue

  12. May 2, 05:58 AM

    Status updated: major issue

  13. May 2, 06:08 AM

    Status updated: possible issue

  14. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 04:38 AM

    ChatGPT status page acknowledged the incident.

    View official source
  2. Aug 14, 07:00 AM

    Slow / unresponsive clustered from 2 sources across 10 signals. Suppressed 9 redundant alerts and flagged flapping behavior.

Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash