Skip to content
Back to GitHubIncident Postmortem
GitHub logo

GitHub

Tracked by PulseWatch

Auto-drafted postmortem

GitHub outage on April 30 — 106d 3h disruption

Apr 30, 03:00 AM → Aug 14, 07:00 AM · 106d 3h · medium

A medium-severity service disruption affected GitHub, detected through automated monitoring and vendor status page updates. The incident began on April 30, 2026, and was resolved on August 14, 2026.

Duration
106d 3h
tracked by PulseWatch

Impact

During the 106-day, 3-hour period from April 30, 2026, to August 14, 2026, GitHub experienced a medium-severity service disruption. This incident was identified through automated monitoring systems and correlated with the vendor's own status page. No user-reported data was collected for this incident, and therefore, specific user-visible impacts such as affected features, regions, or issue types were not recorded.

Incident timeline

  1. Apr 30, 03:00 AM

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

  2. Apr 30, 03:38 AM

    Status updated: possible issue

  3. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

  1. Apr 30, 03:00 AM

    GitHub 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