Skip to content
Back to OpenAIIncident Postmortem
OpenAI logo

OpenAI

Tracked by PulseWatch

Auto-drafted postmortem

OpenAI outage on May 4 — 1h 18m disruption

May 4, 07:45 AM → May 4, 09:04 AM · 1h 18m · high

On May 4, 2026, the OpenAI service experienced a period of disruption, as indicated by user reports. The incident began at approximately 07:45 UTC and was resolved by 09:04 UTC.

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

Impact

Users reported experiencing slow and unresponsive behavior across the OpenAI service. This disruption was detected through a total of 36 user reports, with a peak of 18 reports within a 15-minute period. All reported issues were related to the service being slow or unresponsive. No specific regional impacts were recorded during this incident.

Top reported issues

  • Slow / unresponsive36

Incident timeline

  1. May 4, 07:45 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 08:00 AM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  3. May 4, 08:13 AM

    Status updated: major issue

  4. May 4, 08:18 AM

    Status updated: possible issue

  5. May 4, 08:23 AM

    Status updated: major issue

  6. May 4, 08:28 AM

    Status updated: major issue

  7. May 4, 08:33 AM

    Status updated: possible issue

  8. May 4, 08:38 AM

    Status updated: major issue

  9. May 4, 08:43 AM

    Status updated: major issue

  10. May 4, 08:53 AM

    Status updated: possible issue

  11. May 4, 08:58 AM

    Status updated: possible issue

  12. May 4, 09:04 AM

    Report volume returned to baseline — incident resolved

Official updates

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