Skip to content
Back to OpenAIIncident Postmortem
OpenAI logo

OpenAI

Tracked by PulseWatch

Auto-drafted postmortem

OpenAI outage on April 30 — 106-day disruption

Apr 30, 02:00 AM → Aug 14, 07:00 AM · 106d 4h · medium

An incident affecting OpenAI services was detected on April 30, 2026, at 02:00 UTC. The issue was identified through automated monitoring signals. Services were fully restored on August 14, 2026, at 07:00 UTC.

Duration
106d 4h
tracked by PulseWatch

Impact

A medium-severity incident affecting OpenAI services was detected, lasting approximately 106 days and 4 hours. This disruption was identified through automated signals, including the vendor's status page and synthetic probes. During this period, no user-reported data was collected regarding specific features, regions, or issue types. The incident's impact was assessed based solely on the automated monitoring data.

Incident timeline

  1. Apr 30, 02:00 AM

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

  2. Apr 30, 02:23 AM

    Status updated: possible issue

  3. Apr 30, 02:43 AM

    Status updated: major issue

  4. Apr 30, 02:53 AM

    Status updated: possible issue

  5. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

  1. Apr 30, 02:00 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.

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