Skip to content
Back to GitHubIncident Postmortem
GitHub logo

GitHub

Tracked by PulseWatch

Auto-drafted postmortem

GitHub outage on April 30 106-day 5-hour disruption

Apr 30, 01:15 AM → Aug 14, 07:00 AM · 106d 5h · medium

A service disruption affecting GitHub was detected by automated monitoring. The incident, which was classified as medium severity, lasted approximately 106 days and 5 hours. It was resolved on August 14, 2026.

Duration
106d 5h
tracked by PulseWatch

Impact

During the incident, GitHub experienced a medium-severity service disruption. This disruption lasted for approximately 106 days and 5 hours. No user-reported data, including specific affected features, regions, or issue types, was collected for this incident. The impact was assessed based on automated signals and the duration of the event.

Incident timeline

  1. Apr 30, 01:15 AM

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

  2. Apr 30, 01:43 AM

    Status updated: possible issue

  3. Apr 30, 01:53 AM

    Status updated: major issue

  4. Apr 30, 02:08 AM

    Status updated: possible issue

  5. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

  1. Apr 30, 01:15 AM

    GitHub status page acknowledged the incident.

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

    Website down clustered from 2 sources across 12 signals. Suppressed 11 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