Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 1 — 2h 30m disruption

May 1, 01:37 PM → May 1, 04:08 PM · 2h 30m · high

ChatGPT experienced an outage on May 1st, impacting users with AI API issues and slow or unresponsive service. The incident began at 13:37 UTC and was fully resolved by 16:08 UTC.

Peak reports
16
in 15 min
Total reports
107
during the incident
Duration
2h 30m
tracked by PulseWatch

Impact

During this incident, users reported issues with the ChatGPT service, primarily related to AI API functionality and slow or unresponsive performance. These reports were detected and grouped by our monitoring systems. The disruption affected users globally, with no specific regions identified as being more impacted than others. The issue was resolved after approximately 2 hours and 30 minutes.

Top reported issues

  • AI API issues63
  • Slow / unresponsive44

Incident timeline

  1. May 1, 01:37 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:08 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 1, 01:37 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-lite