Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 2 — 103d 23h disruption

May 2, 07:01 AM → Aug 14, 07:00 AM · 103d 23h · medium

A service disruption affecting ChatGPT was detected on May 2, 2026, due to an elevated volume of user reports. The incident was correlated across official/vendor signals. Service functionality was fully restored on August 14, 2026.

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

Impact

The incident was detected through an elevated volume of user reports, with a peak of 10 reports within a 15-minute period and a total of 133 reports received during the disruption. Users primarily reported issues related to the service being slow or unresponsive, accounting for 112 reports. Additionally, 18 reports cited AI API issues, and 3 reports mentioned general API issues. No specific top impacted regions were recorded during this period.

Top reported issues

  • Slow / unresponsive112
  • AI API issues18
  • API issues3

Incident timeline

  1. May 2, 07:01 AM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 07:23 AM

    Status updated: possible issue

  3. May 2, 07:28 AM

    Status updated: major issue

  4. May 2, 07:38 AM

    Status updated: possible issue

  5. May 2, 07:43 AM

    Status updated: major issue

  6. May 2, 07:53 AM

    Status updated: possible issue

  7. May 2, 07:58 AM

    Status updated: major issue

  8. May 2, 08:08 AM

    Status updated: possible issue

  9. May 2, 08:13 AM

    Status updated: major issue

  10. May 2, 08:23 AM

    Status updated: possible issue

  11. May 2, 08:28 AM

    Status updated: major issue

  12. May 2, 08:38 AM

    Status updated: possible issue

  13. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 07:01 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.

  3. Aug 14, 07:00 AM

    Root cause: Transient performance degradation with 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