Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 1 — 32-minute disruption

May 1, 04:00 PM → May 1, 04:33 PM · 32 minutes · high

On May 1, 2026, ChatGPT experienced a service disruption, which was detected through user reports. The incident began at approximately 16:00 UTC and primarily manifested as slow or unresponsive service. The issue was resolved by 16:33 UTC, restoring full functionality.

Peak reports
10
in 15 min
Total reports
14
during the incident
Duration
32 minutes
tracked by PulseWatch

Impact

Users reported experiencing slow or unresponsive service during the incident. A total of 14 reports were received, with a peak of 10 reports within a 15-minute period. The primary issue types reported were 'Slow / unresponsive' (8 reports) and 'AI API issues' (6 reports). No specific regional impact was recorded. The disruption was initially identified through these user reports.

Top reported issues

  • Slow / unresponsive8
  • AI API issues6

Incident timeline

  1. May 1, 04:00 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 1, 04:15 PM

    Peak of 7 reports in 15 minutes (baseline 7.0)

  3. May 1, 04:33 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 1, 04:00 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