Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 3  1h 3m disruption

May 3, 07:15 PM → May 3, 08:19 PM · 1h 3m · high

On May 3, 2026, ChatGPT experienced a service disruption, which was detected through user reports. The incident began at approximately 7:15 PM UTC and was resolved by 8:19 PM UTC on the same day.

Peak reports
14
in 15 min
Total reports
40
during the incident
Duration
1h 3m
tracked by PulseWatch

Impact

Users reported experiencing issues with ChatGPT functionality. The primary reported issues included slow or unresponsive service, as well as problems with AI API access and general API functionality. A total of 40 user reports were received during the incident, with a peak of 14 reports within a 15-minute period. No specific regional impacts were recorded.

Top reported issues

  • Slow / unresponsive24
  • AI API issues12
  • API issues4

Incident timeline

  1. May 3, 07:15 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 07:30 PM

    Peak of 11 reports in 15 minutes (baseline 1.3)

  3. May 3, 07:43 PM

    Status updated: major issue

  4. May 3, 07:53 PM

    Status updated: possible issue

  5. May 3, 07:58 PM

    Status updated: major issue

  6. May 3, 08:08 PM

    Status updated: possible issue

  7. May 3, 08:13 PM

    Status updated: major issue

  8. May 3, 08:19 PM

    Report volume returned to baseline — incident resolved

Official updates

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