Skip to content
Back to OpenAIIncident Postmortem
OpenAI logo

OpenAI

Tracked by PulseWatch

Auto-drafted postmortem

OpenAI outage on May 4 33-minute disruption

May 4, 02:15 AM → May 4, 02:49 AM · 33 minutes · high

An incident affecting OpenAI services was detected on May 4, 2026, starting at 02:15 UTC. The disruption was identified through user reports indicating service slowness and unresponsiveness. The incident was resolved at 02:49 UTC.

Peak reports
10
in 15 min
Total reports
12
during the incident
Duration
33 minutes
tracked by PulseWatch

Impact

Users experienced a period of service degradation, primarily reporting slow or unresponsive behavior across OpenAI services. This incident was initially brought to attention through user reports, with a total of 12 reports received during the 33-minute period. While no specific regions were predominantly impacted, the consistent nature of the "Slow / unresponsive" issue type suggests a general service disruption.

Top reported issues

  • Slow / unresponsive12

Incident timeline

  1. May 4, 02:15 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 02:30 AM

    Peak of 4 reports in 15 minutes (baseline 1.3)

  3. May 4, 02:43 AM

    Status updated: possible issue

  4. May 4, 02:49 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 02: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