Skip to content
Back to OpenAIIncident Postmortem
OpenAI logo

OpenAI

Tracked by PulseWatch

Auto-drafted postmortem

OpenAI outage on May 4 extemdash 1h 33m disruption

May 4, 05:30 AM → May 4, 07:04 AM · 1h 33m · high

On May 4, 2026, a disruption to OpenAI services was detected via user reports. The incident began at approximately 05:30 UTC and was resolved by 07:04 UTC, lasting 1 hour and 33 minutes.

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

Impact

Users reported a high severity disruption to OpenAI services. The primary issues reported were slow or unresponsive service, accounting for 32 reports, and website downtime, with 12 reports. A total of 44 user reports were received during the incident, with a peak of 14 reports within a 15-minute period. No specific regional impact was recorded.

Top reported issues

  • Slow / unresponsive32
  • Website down12

Incident timeline

  1. May 4, 05:30 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 05:45 AM

    Peak of 8 reports in 15 minutes (baseline 4.0)

  3. May 4, 06:03 AM

    Status updated: possible issue

  4. May 4, 06:08 AM

    Status updated: major issue

  5. May 4, 06:13 AM

    Status updated: major issue

  6. May 4, 06:18 AM

    Status updated: possible issue

  7. May 4, 06:23 AM

    Status updated: major issue

  8. May 4, 06:28 AM

    Status updated: major issue

  9. May 4, 06:38 AM

    Status updated: possible issue

  10. May 4, 06:43 AM

    Status updated: possible issue

  11. May 4, 06:53 AM

    Status updated: possible issue

  12. May 4, 06:58 AM

    Status updated: possible issue

  13. May 4, 07:04 AM

    Report volume returned to baseline — incident resolved

Official updates

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