Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 4 33-minute disruption

May 4, 07:01 AM → May 4, 07:34 AM · 33 minutes · high

ChatGPT experienced a high-severity service disruption, which was detected through user reports. The issue was resolved after 33 minutes of disruption.

Peak reports
10
in 15 min
Total reports
18
during the incident
Duration
33 minutes
tracked by PulseWatch

Impact

Users reported experiencing issues with ChatGPT functionality. The primary reported issues included slow or unresponsive service and problems with AI API interactions. A total of 18 user reports were received during the incident. No specific regional impact was recorded.

Top reported issues

  • Slow / unresponsive12
  • AI API issues6

Incident timeline

  1. May 4, 07:01 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 07:15 AM

    Peak of 7 reports in 15 minutes (baseline 1.3)

  3. May 4, 07:34 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 07:01 AM

    ChatGPT status page acknowledged the incident.

    View official source
  2. May 4, 07:34 AM

    Root cause: Underlying instability or performance issue with ChatGPT, as suggested by 'flapping behavior' and multiple correlated alerts.

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