Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 3 — 33-minute disruption

May 3, 09:45 PM → May 3, 10:19 PM · 33 minutes · high

ChatGPT experienced a service disruption on May 3, which was detected through user reports. The incident began at 21:45 UTC and was resolved after 33 minutes at 22:19 UTC.

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

Impact

During the incident, users reported experiencing issues with ChatGPT. The disruption was characterized by reports of slow or unresponsive service, accounting for 12 of the 18 total reports received. Additionally, 6 reports indicated problems with AI API functionality. No specific regional impact was recorded during this period.

Top reported issues

  • Slow / unresponsive12
  • AI API issues6

Incident timeline

  1. May 3, 09:45 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 10:00 PM

    Peak of 7 reports in 15 minutes (baseline 1.3)

  3. May 3, 10:13 PM

    Status updated: major issue

  4. May 3, 10:19 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 09:45 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