Skip to content
Back to GitHubIncident Postmortem
GitHub logo

GitHub

Tracked by PulseWatch

Auto-drafted postmortem

GitHub outage on April 29 — 106d 7h disruption

Apr 29, 11:30 PM → Aug 14, 07:00 AM · 106d 7h · high

On April 29, 2026, GitHub experienced a period of high severity service disruption. This incident, characterized by slow or unresponsive alerts, was detected by automated monitoring systems. The disruption was resolved on August 14, 2026.

Duration
106d 7h
tracked by PulseWatch

Impact

This incident affected GitHub services for a duration of 106 days and 7 hours, categorized as high severity. Automated monitoring systems detected slow or unresponsive alerts during this period. No user reports were collected for this incident, and therefore, no data on specific affected features, regions, or issue types is available.

Incident timeline

  1. Apr 29, 11:30 PM

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

  2. Apr 30, 12:08 AM

    Status updated: possible issue

  3. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

  1. Apr 29, 11:30 PM

    GitHub status page acknowledged the incident.

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

    Slow / unresponsive clustered from 2 sources across 14 signals. Suppressed 13 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