Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 3 — 103d 3h disruption

May 3, 03:00 AM → Aug 14, 07:00 AM · 103d 3h · medium

An incident affecting ChatGPT was detected from elevated user-report volume, starting on May 3, 2026. The incident was resolved on August 14, 2026, after a disruption lasting approximately 103 days and 3 hours.

Peak reports
10
in 15 min
Total reports
133
during the incident
Duration
103d 3h
tracked by PulseWatch

Impact

During the incident, users reported a variety of issues, with the most frequent being slow or unresponsive service, accounting for 112 reports. There were also 18 reports related to AI API issues and 3 reports concerning general API issues. In total, 133 user reports were received. No specific top impacted regions were recorded during this period.

Top reported issues

  • Slow / unresponsive112
  • AI API issues18
  • API issues3

Incident timeline

  1. May 3, 03:00 AM

    PulseWatch detected elevated report volume (medium severity)

  2. May 3, 03:23 AM

    Status updated: possible issue

  3. May 3, 03:28 AM

    Status updated: major issue

  4. May 3, 03:38 AM

    Status updated: possible issue

  5. May 3, 03:43 AM

    Status updated: major issue

  6. May 3, 03:53 AM

    Status updated: possible issue

  7. May 3, 03:58 AM

    Status updated: major issue

  8. May 3, 04:08 AM

    Status updated: possible issue

  9. May 3, 04:13 AM

    Status updated: major issue

  10. May 3, 04:23 AM

    Status updated: possible issue

  11. May 3, 04:28 AM

    Status updated: major issue

  12. May 3, 04:38 AM

    Status updated: possible issue

  13. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 03:00 AM

    ChatGPT status page acknowledged the incident.

    View official source
  2. Aug 14, 07:00 AM

    Slow / unresponsive clustered from 2 sources across 10 signals. Suppressed 9 redundant alerts and flagged flapping behavior.

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