Skip to content
Back to GitHubIncident Postmortem
GitHub logo

GitHub

Tracked by PulseWatch

Auto-drafted postmortem

GitHub outage on April 30 106d 5h disruption

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

An outage affecting GitHub was detected by PulseWatch, a third-party monitoring platform. The incident began on April 30, 2026, at 01:52 UTC. Service was fully restored on August 14, 2026, at 07:00 UTC.

Duration
106d 5h
tracked by PulseWatch

Impact

This incident affected GitHub for a duration of 106 days and 5 hours, categorized as a medium severity event. The outage was identified through automated signals, including the vendor's status page and synthetic probes. No user-reported data was collected for this incident, and therefore no information regarding specific affected features, regions, or issue types is available from user reports.

Incident timeline

  1. Apr 30, 01:52 AM

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

  2. Apr 30, 02:23 AM

    Status updated: major issue

  3. Apr 30, 02:38 AM

    Status updated: possible issue

  4. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

  1. Apr 30, 01:52 AM

    GitHub status page acknowledged the incident.

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

    Slow / unresponsive clustered from 3 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