Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 4 48-minute disruption

May 4, 03:00 AM → May 4, 03:49 AM · 48 minutes · high

ChatGPT experienced a service disruption on May 4, detected through user reports. The incident began at 03:00 UTC and was resolved by 03:49 UTC, lasting approximately 48 minutes.

Peak reports
14
in 15 min
Total reports
29
during the incident
Duration
48 minutes
tracked by PulseWatch

Impact

Users reported issues with ChatGPT, primarily experiencing slow or unresponsive service. A smaller number of reports indicated problems with AI API functionality. While no specific regional impact was recorded, the disruption was widely reported by users.

Top reported issues

  • Slow / unresponsive20
  • AI API issues9

Incident timeline

  1. May 4, 03:00 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 03:15 AM

    Peak of 11 reports in 15 minutes (baseline 1.3)

  3. May 4, 03:38 AM

    Status updated: possible issue

  4. May 4, 03:43 AM

    Status updated: major issue

  5. May 4, 03:49 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 03:00 AM

    ChatGPT status page acknowledged the incident.

    View official source
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