Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 2 — 103d 8h disruption

May 2, 10:00 PM → Aug 14, 07:00 AM · 103d 8h · medium

A service disruption affecting ChatGPT was detected due to an elevated volume of user reports. The incident began on May 2, 2026, and was resolved on August 14, 2026.

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

Impact

Users experienced issues with ChatGPT, primarily reporting slow or unresponsive service. A total of 133 user reports were received during the incident, with a peak of 14 reports within a 15-minute period. The most frequently reported issue types included slow/unresponsive service, AI API issues, and general API issues. No specific regional impact was recorded.

Top reported issues

  • Slow / unresponsive112
  • AI API issues18
  • API issues3

Incident timeline

  1. May 2, 10:00 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 10:23 PM

    Status updated: possible issue

  3. May 2, 10:28 PM

    Status updated: major issue

  4. May 2, 10:38 PM

    Status updated: possible issue

  5. May 2, 10:43 PM

    Status updated: major issue

  6. May 2, 10:53 PM

    Status updated: possible issue

  7. May 2, 10:58 PM

    Status updated: major issue

  8. May 2, 11:08 PM

    Status updated: possible issue

  9. May 2, 11:13 PM

    Status updated: major issue

  10. May 2, 11:23 PM

    Status updated: possible issue

  11. May 2, 11:28 PM

    Status updated: major issue

  12. May 2, 11:38 PM

    Status updated: possible issue

  13. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 10:00 PM

    ChatGPT status page acknowledged the incident.

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

    Slow / unresponsive clustered from 2 sources across 14 signals. Suppressed 13 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