Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 1 — 2h 47m disruption

May 1, 01:30 PM → May 1, 04:18 PM · 2h 47m · high

On May 1, 2026, ChatGPT experienced a service disruption, which was detected through user reports. The incident began at 13:30 UTC and was fully resolved by 16:18 UTC on the same day.

Peak reports
10
in 15 min
Total reports
111
during the incident
Duration
2h 47m
tracked by PulseWatch

Impact

During the incident, users reported a high severity disruption to ChatGPT services. The primary issues reported by users included AI API issues and slow or unresponsive service. A total of 111 user reports were received, indicating widespread impact across various functionalities. No specific regional concentrations of reports were identified.

Top reported issues

  • AI API issues63
  • Slow / unresponsive48

Incident timeline

  1. May 1, 01:30 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 1, 02:30 PM

    Peak of 13 reports in 15 minutes (baseline 7.0)

  3. May 1, 04:18 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 1, 01:30 PM

    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