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:00 AM → Aug 14, 07:00 AM · 106d 6h · high

On April 30, 2026, GitHub experienced a service disruption. This incident was detected by automated monitoring systems. The service was fully restored on August 14, 2026.

Duration
106d 6h
tracked by PulseWatch

Impact

During the incident, GitHub experienced a high-severity disruption lasting 106 days and 6 hours. This disruption was identified through automated monitoring and vendor status page alerts. No user-reported data was collected for this incident, and therefore, specific user-visible impacts such as affected features, regions, or issue types cannot be detailed based on user reports.

Incident timeline

  1. Apr 30, 12:00 AM

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

  2. Apr 30, 12:38 AM

    Status updated: possible issue

  3. Apr 30, 12:53 AM

    Status updated: major issue

  4. Apr 30, 01:08 AM

    Status updated: possible issue

  5. Aug 14, 07:00 AM

    Signals cleared — incident resolved

Official updates

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