Skip to content
Back to OpenAIIncident Postmortem
OpenAI logo

OpenAI

Tracked by PulseWatch

Auto-drafted postmortem

OpenAI outage on May 2 A 103d 17h disruption

May 2, 01:45 PM → Aug 14, 07:00 AM · 103d 17h · high

A high-severity disruption affecting OpenAI services was detected by automated monitoring systems. The incident began on May 2, 2026. Services were fully restored on August 14, 2026.

Duration
103d 17h
tracked by PulseWatch

Impact

This high-severity incident affected OpenAI services for approximately 103 days and 17 hours. During this period, automated signals indicated a disruption to service availability. No user-reported data, including specific issue types or impacted regions, was collected for this incident.

Incident timeline

  1. May 2, 01:45 PM

    PulseWatch detected the incident from automated vendor and probe signals (high severity)

  2. May 2, 02:13 PM

    Status updated: major issue

  3. May 2, 02:18 PM

    Status updated: possible issue

  4. May 2, 02:23 PM

    Status updated: major issue

  5. May 2, 02:33 PM

    Status updated: possible issue

  6. May 2, 02:38 PM

    Status updated: major issue

  7. May 2, 02:48 PM

    Status updated: possible issue

  8. May 2, 02:53 PM

    Status updated: major issue

  9. May 2, 03:03 PM

    Status updated: possible issue

  10. May 2, 03:08 PM

    Status updated: major issue

  11. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

  1. May 2, 01:45 PM

    OpenAI status page acknowledged the incident.

    View official source
  2. Aug 14, 07:00 AM

    Slow / unresponsive clustered from 2 sources across 18 signals. Suppressed 17 redundant alerts and flagged flapping behavior.

Draft auto-generated by PulseWatch when the incident resolved. Based on the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash