Skip to content
Back to GitHubIncident Postmortem
GitHub logo

GitHub

Tracked by PulseWatch

Auto-drafted postmortem

GitHub outage on April 30 "," 106d 2h disruption

Apr 30, 04:47 AM → Aug 14, 07:00 AM · 106d 2h · medium

GitHub experienced a service disruption beginning on April 30, 2026. This medium-severity incident lasted for approximately 106 days and 2 hours. The disruption was fully resolved on August 14, 2026.

Duration
106d 2h
tracked by PulseWatch

Impact

During the 106-day and 2-hour disruption, GitHub experienced a medium-severity service incident. This incident was detected through automated monitoring signals, including the vendor's status page and synthetic probes. No user-reported data was collected for this incident, meaning there were no direct user reports regarding specific features, regions, or issue types.

Incident timeline

  1. Apr 30, 04:47 AM

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

  2. Apr 30, 05:13 AM

    Status updated: possible issue

  3. Apr 30, 05:23 AM

    Status updated: major issue

  4. Apr 30, 05:38 AM

    Status updated: possible issue

  5. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

  1. Apr 30, 04:47 AM

    GitHub status page acknowledged the incident.

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

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