Skip to content
Back to ChatGPTIncident Postmortem
ChatGPT logo

ChatGPT

Tracked by PulseWatch

Auto-drafted postmortem

ChatGPT outage on May 3 — 102d 12h disruption

May 3, 06:50 PM → Aug 14, 07:00 AM · 102d 12h · medium

An incident affecting the ChatGPT service was detected due to an elevated volume of user reports. The issue began on May 3, 2026, at 18:50 UTC and was fully resolved on August 14, 2026, at 07:00 UTC.

Peak reports
11
in 15 min
Total reports
133
during the incident
Duration
102d 12h
tracked by PulseWatch

Impact

Users experienced a medium-severity disruption to the ChatGPT service. The incident was characterized by 133 total user reports, with a peak of 11 reports within a 15-minute period. The primary reported issues included slow or unresponsive service, accounting for 112 reports, followed by AI API issues (18 reports) and general API issues (3 reports). No specific regional impact was recorded during this period.

Top reported issues

  • Slow / unresponsive112
  • AI API issues18
  • API issues3

Incident timeline

  1. May 3, 06:50 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 4, 12:23 AM

    Status updated: possible issue

  3. May 4, 12:28 AM

    Status updated: major issue

  4. May 4, 12:38 AM

    Status updated: possible issue

  5. May 4, 01:28 AM

    Status updated: major issue

  6. May 4, 01:38 AM

    Status updated: possible issue

  7. May 4, 01:58 AM

    Status updated: major issue

  8. May 4, 02:08 AM

    Status updated: possible issue

  9. May 4, 02:28 AM

    Status updated: major issue

  10. May 4, 02:38 AM

    Status updated: possible issue

  11. May 4, 02:58 AM

    Status updated: major issue

  12. May 4, 03:08 AM

    Status updated: possible issue

  13. May 4, 03:28 AM

    Status updated: major issue

  14. May 4, 03:53 AM

    Status updated: possible issue

  15. May 4, 03:58 AM

    Status updated: major issue

  16. May 4, 04:08 AM

    Status updated: possible issue

  17. May 4, 04:28 AM

    Status updated: major issue

  18. May 4, 04:38 AM

    Status updated: possible issue

  19. May 4, 04:58 AM

    Status updated: major issue

  20. May 4, 05:08 AM

    Status updated: possible issue

  21. May 4, 05:28 AM

    Status updated: major issue

  22. May 4, 05:38 AM

    Status updated: possible issue

  23. May 4, 06:28 AM

    Status updated: major issue

  24. May 4, 06:38 AM

    Status updated: possible issue

  25. May 4, 06:58 AM

    Status updated: major issue

  26. May 4, 07:08 AM

    Status updated: possible issue

  27. May 4, 07:28 AM

    Status updated: major issue

  28. May 4, 07:38 AM

    Status updated: possible issue

  29. May 4, 07:58 AM

    Status updated: major issue

  30. May 4, 08:08 AM

    Status updated: possible issue

  31. May 4, 08:58 AM

    Status updated: major issue

  32. May 4, 09:08 AM

    Status updated: possible issue

  33. May 4, 09:28 AM

    Status updated: major issue

  34. May 4, 09:38 AM

    Status updated: possible issue

  35. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 06:50 PM

    ChatGPT status page acknowledged the incident.

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

    API issues clustered from 2 sources across 11 signals. Suppressed 10 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