ChatGPT outage on May 3 ","summary": "On May 3, ChatGPT experienced a service disruption. This incident was detected from an elevated volume of user reports. The service disruption was resolved on August 14.","impactDescription": "Users reported experiencing issues with ChatGPT, leading to a total of 133 reports during the incident. The most frequently reported issue types included slow or unresponsive service, accounting for 112 reports. Additionally, users reported 18 instances of AI API issues and 3 instances of general API issues. No specific regional impact was recorded during this period."}103d 6h disruption
May 3, 12:30 AM → Aug 14, 07:00 AM · 103d 6h · medium
On May 3, ChatGPT experienced a service disruption. This incident was detected from an elevated volume of user reports. The service disruption was resolved on August 14.
Impact
Users reported experiencing issues with ChatGPT, leading to a total of 133 reports during the incident. The most frequently reported issue types included slow or unresponsive service, accounting for 112 reports. Additionally, users reported 18 instances of AI API issues and 3 instances of general API issues. No specific regional impact was recorded during this period.
Top reported issues
- Slow / unresponsive112
- AI API issues18
- API issues3
Incident timeline
- May 3, 12:30 AM
PulseWatch detected elevated report volume (medium severity)
- May 3, 12:53 AM
Status updated: possible issue
- May 3, 12:58 AM
Status updated: major issue
- May 3, 01:08 AM
Status updated: possible issue
- May 3, 01:13 AM
Status updated: major issue
- May 3, 01:23 AM
Status updated: possible issue
- May 3, 01:28 AM
Status updated: major issue
- May 3, 01:38 AM
Status updated: possible issue
- May 3, 01:43 AM
Status updated: major issue
- May 3, 01:53 AM
Status updated: possible issue
- May 3, 01:58 AM
Status updated: major issue
- May 3, 02:08 AM
Status updated: possible issue
- Aug 14, 07:00 AM
Report volume returned to baseline — incident resolved
Official updates
- May 3, 12:30 AM
ChatGPT status page acknowledged the incident.
View official source - Aug 14, 07:00 AM
Slow / unresponsive clustered from 2 sources across 14 signals. Suppressed 13 redundant alerts and flagged flapping behavior.