Skip to content
Back to OpenAIIncident Postmortem
OpenAI logo

OpenAI

Tracked by PulseWatch

Auto-drafted postmortem

OpenAI outage on May 2 104-day disruption

May 2, 06:30 AM → Aug 14, 07:00 AM · 104d 0h · medium

An incident affecting OpenAI services was detected on May 2, 2026. The issue resulted in a medium severity disruption. Services were fully restored on August 14, 2026.

Duration
104d 0h
tracked by PulseWatch

Impact

During the 104-day incident, OpenAI services experienced a medium severity disruption. This incident was detected through automated signals, including the vendor's own status page and synthetic probes. No user-reported data was collected for this incident, and therefore no specific user-reported issue types or affected regions were recorded. The impact was assessed based on the duration and severity of the service disruption.

Incident timeline

  1. May 2, 06:30 AM

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

  2. May 2, 06:53 AM

    Status updated: possible issue

  3. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

  1. May 2, 06:30 AM

    OpenAI status page acknowledged the incident.

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

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

  3. Aug 14, 07:00 AM

    Root cause: Transient performance degradation with 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