Skip to content
Back to GitHubIncident Postmortem
GitHub logo

GitHub

Tracked by PulseWatch

Auto-drafted postmortem

GitHub outage on April 30 106d 6h disruption

Apr 30, 12:46 AM → Aug 14, 07:00 AM · 106d 6h · high

On April 30, 2026, automated monitoring systems detected a high-severity disruption affecting GitHub services. This incident involved slow or unresponsive behavior. The issue was resolved on August 14, 2026.

Duration
106d 6h
tracked by PulseWatch

Impact

A high-severity disruption affected GitHub services for approximately 106 days and 6 hours, starting on April 30, 2026. During this period, automated signals indicated slow or unresponsive service behavior. 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, 12:46 AM

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

  2. Apr 30, 01:13 AM

    Status updated: possible issue

  3. Apr 30, 01:23 AM

    Status updated: major issue

  4. Apr 30, 01:38 AM

    Status updated: possible issue

  5. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

  1. Apr 30, 12:46 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