Skip to content
Back to OpenAIIncident Postmortem
OpenAI logo

OpenAI

Tracked by PulseWatch

Auto-drafted postmortem

OpenAI outage on May 2 103d 13h disruption

May 2, 05:30 PM → Aug 14, 07:00 AM · 103d 13h · high

An incident affecting OpenAI services was detected by automated monitoring. This high-severity incident began on May 2, 2026, and was resolved on August 14, 2026.

Duration
103d 13h
tracked by PulseWatch

Impact

During the 103-day and 13-hour period from May 2, 2026, to August 14, 2026, OpenAI services experienced a high-severity incident. This disruption was identified through automated signals, including the vendor's status page and synthetic probes. No user-reported data was collected for this incident, meaning there were no records of specific user-reported issues, affected regions, or report volumes. The impact was assessed based solely on the automated monitoring data.

Incident timeline

  1. May 2, 05:30 PM

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

  2. May 2, 05:53 PM

    Status updated: major issue

  3. May 2, 06:03 PM

    Status updated: possible issue

  4. May 2, 06:08 PM

    Status updated: major issue

  5. May 2, 06:18 PM

    Status updated: possible issue

  6. May 2, 06:23 PM

    Status updated: major issue

  7. May 2, 06:33 PM

    Status updated: possible issue

  8. May 2, 06:38 PM

    Status updated: major issue

  9. May 2, 06:48 PM

    Status updated: possible issue

  10. May 2, 06:53 PM

    Status updated: major issue

  11. May 2, 07:03 PM

    Status updated: possible issue

  12. May 2, 07:08 PM

    Status updated: major issue

  13. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

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