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:15 AM → May 4, 07:49 AM · 33 minutes · high

A service disruption affected ChatGPT users, detected via user reports. The incident began at approximately 07:15 UTC and was resolved on May 4, 2026, at 07:49 UTC.

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

Impact

During the 33-minute disruption, users reported experiencing issues with ChatGPT. The most common reports indicated slow or unresponsive service, making up 12 of the 18 total reports received. There were also 6 reports concerning AI API functionality. No specific regional impact was identified during this incident, which was initially detected through these user reports.

Top reported issues

  • Slow / unresponsive12
  • AI API issues6

Incident timeline

  1. May 4, 07:15 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 07:30 AM

    Peak of 7 reports in 15 minutes (baseline 1.3)

  3. May 4, 07:43 AM

    Status updated: major issue

  4. May 4, 07:49 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 07:15 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