Skip to content
Back to OpenAIIncident Postmortem
OpenAI logo

OpenAI

Tracked by PulseWatch

Auto-drafted postmortem

OpenAI outage on May 3 — 1h 33m disruption

May 3, 10:01 PM → May 3, 11:34 PM · 1h 33m · high

Users experienced issues with OpenAI services, primarily reporting slow or unresponsive behavior. This outage was detected through user reports and began on May 3, 2026, at 22:01 UTC. Services were fully restored by 23:34 UTC.

Peak reports
18
in 15 min
Total reports
48
during the incident
Duration
1h 33m
tracked by PulseWatch

Impact

During the incident, users primarily reported experiencing slow or unresponsive behavior when interacting with OpenAI services. A total of 48 user reports were received, with a peak of 18 reports within a 15-minute period. These reports consistently indicated performance degradation across the service. No specific regional impact was identified or reported during the outage. The issues were widespread, affecting general service responsiveness.

Top reported issues

  • Slow / unresponsive48

Incident timeline

  1. May 3, 10:01 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 10:15 PM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  3. May 3, 10:33 PM

    Status updated: possible issue

  4. May 3, 10:38 PM

    Status updated: major issue

  5. May 3, 10:43 PM

    Status updated: major issue

  6. May 3, 10:53 PM

    Status updated: major issue

  7. May 3, 10:58 PM

    Status updated: major issue

  8. May 3, 11:03 PM

    Status updated: possible issue

  9. May 3, 11:08 PM

    Status updated: major issue

  10. May 3, 11:13 PM

    Status updated: major issue

  11. May 3, 11:23 PM

    Status updated: possible issue

  12. May 3, 11:28 PM

    Status updated: possible issue

  13. May 3, 11:34 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 10:01 PM

    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