Skip to content
Back to OpenAIIncident Postmortem
OpenAI logo

OpenAI

Tracked by PulseWatch

Auto-drafted postmortem

OpenAI outage on May 2 103d 18h disruption

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

An outage affecting OpenAI services was detected by automated monitoring. The incident began on May 2, 2026, at 12:30 UTC. Services were fully restored on August 14, 2026, at 07:00 UTC.

Duration
103d 18h
tracked by PulseWatch

Impact

This incident, lasting 103 days and 18 hours, was categorized as high severity for OpenAI services. It was detected through automated signals, including the vendor's own status page and synthetic probes. No user reports were collected for this incident, and therefore no data on specific affected features, regions, or issue types is available from user feedback.

Incident timeline

  1. May 2, 12:30 PM

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

  2. May 2, 01:03 PM

    Status updated: possible issue

  3. May 2, 01:08 PM

    Status updated: major issue

  4. May 2, 01:23 PM

    Status updated: possible issue

  5. May 2, 01:38 PM

    Status updated: major issue

  6. May 2, 01:48 PM

    Status updated: possible issue

  7. May 2, 01:53 PM

    Status updated: major issue

  8. May 2, 02:03 PM

    Status updated: possible issue

  9. May 2, 02:08 PM

    Status updated: major issue

  10. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

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