Skip to content
Back to OpenAIIncident Postmortem
OpenAI logo

OpenAI

Tracked by PulseWatch

Auto-drafted postmortem

OpenAI outage on April 29 — 106d 7h disruption

Apr 29, 11:30 PM → Aug 14, 07:00 AM · 106d 7h · high

An incident affecting OpenAI services was detected on April 29, 2026, at 23:30 UTC. The issue was resolved on August 14, 2026, at 07:00 UTC.

Duration
106d 7h
tracked by PulseWatch

Impact

This high-severity incident affected OpenAI services for approximately 106 days and 7 hours. Detection was based solely on automated signals from the vendor's status page and synthetic probes. No user-reported data was collected for this incident, meaning no specific features, regions, or issue types were identified as being impacted by user reports.

Incident timeline

  1. Apr 29, 11:30 PM

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

  2. Apr 29, 11:53 PM

    Status updated: possible issue

  3. Apr 30, 12:23 AM

    Status updated: major issue

  4. Apr 30, 12:33 AM

    Status updated: possible issue

  5. Apr 30, 12:38 AM

    Status updated: major issue

  6. Apr 30, 12:48 AM

    Status updated: possible issue

  7. Apr 30, 12:53 AM

    Status updated: major issue

  8. Apr 30, 01:03 AM

    Status updated: possible issue

  9. Apr 30, 01:08 AM

    Status updated: major issue

  10. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

  1. Apr 29, 11: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