Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 4  35-minute disruption

May 4, 12:43 AM → May 4, 01:19 AM · 35 minutes · high

On May 4, 2026, ChatGPT experienced a high-severity service disruption, first detected through user reports. The incident began at 00:43 UTC and was resolved at 01:19 UTC, resulting in approximately 35 minutes of service impact.

Peak reports
14
in 15 min
Total reports
22
during the incident
Duration
35 minutes
tracked by PulseWatch

Impact

Users reported issues with ChatGPT functionality during the incident. A total of 22 reports were received, with a peak of 14 reports in a 15-minute period. The most frequently reported issue types included slow or unresponsive service, accounting for 16 reports, and AI API issues, with 6 reports. No specific regional impact was recorded during this period.

Top reported issues

  • Slow / unresponsive16
  • AI API issues6

Incident timeline

  1. May 4, 12:43 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 12:45 AM

    Peak of 7 reports in 15 minutes (baseline 1.3)

  3. May 4, 01:13 AM

    Status updated: major issue

  4. May 4, 01:19 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 12:43 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