Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 2 — 103d 16h disruption

May 2, 02:30 PM → Aug 14, 07:00 AM · 103d 16h · medium

On May 2, 2026, the ChatGPT service experienced an outage, detected through an elevated volume of user reports. The incident was resolved on August 14, 2026.

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

Impact

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

Top reported issues

  • Slow / unresponsive112
  • AI API issues18
  • API issues3

Incident timeline

  1. May 2, 02:30 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 02:53 PM

    Status updated: possible issue

  3. May 2, 02:58 PM

    Status updated: major issue

  4. May 2, 03:08 PM

    Status updated: possible issue

  5. May 2, 03:13 PM

    Status updated: major issue

  6. May 2, 03:23 PM

    Status updated: possible issue

  7. May 2, 03:28 PM

    Status updated: major issue

  8. May 2, 03:38 PM

    Status updated: possible issue

  9. May 2, 03:43 PM

    Status updated: major issue

  10. May 2, 03:53 PM

    Status updated: possible issue

  11. May 2, 03:58 PM

    Status updated: major issue

  12. May 2, 04:08 PM

    Status updated: possible issue

  13. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 02:30 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