Skip to content
Back to OpenAIIncident Postmortem
OpenAI logo

OpenAI

Tracked by PulseWatch

Auto-drafted postmortem

OpenAI outage on May 2 \u2014 1h 42m disruption

May 2, 12:15 AM → May 2, 01:58 AM · 1h 42m · high

Users experienced issues with OpenAI services, including slow responses and API problems. This disruption was detected through user reports and third-party monitoring platforms. The incident began on May 2, 2026, at 00:15 UTC and was resolved at 01:58 UTC.

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

Impact

During the incident, users reported difficulties with OpenAI services, primarily experiencing slow or unresponsive behavior. A significant number of reports also indicated issues with API functionality, alongside some instances of the website being inaccessible. While 53 total reports were received, no specific regional impact was recorded during the 1 hour and 42 minute disruption.

Top reported issues

  • Slow / unresponsive32
  • API issues12
  • Website down9

Incident timeline

  1. May 2, 12:15 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 2, 12:45 AM

    Peak of 9 reports in 15 minutes (baseline 4.0)

  3. May 2, 01:58 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 12:15 AM

    OpenAI 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