GitHub outage on April 30 A 106-day disruption
Apr 30, 06:45 AM → Aug 14, 07:00 AM · 106d 0h · medium
A medium-severity service disruption affected GitHub, detected through automated monitoring signals. The incident began on April 30, 2026, and was resolved on August 14, 2026.
Impact
During the 106-day period of this medium-severity incident, GitHub experienced service disruption. The incident was identified through automated monitoring and vendor status updates. No user-reported data was collected or correlated with this event, meaning there were no direct user reports regarding specific features or regions affected. The impact was assessed based on the duration and severity of the automated signals.
Incident timeline
- Apr 30, 06:45 AM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
- Apr 30, 07:13 AM
Status updated: possible issue
- Apr 30, 07:53 AM
Status updated: major issue
- Apr 30, 08:08 AM
Status updated: possible issue
- Aug 14, 07:00 AM
Signals cleared — incident resolved
Official updates
- Apr 30, 06:45 AM
GitHub status page acknowledged the incident.
View official source - Aug 14, 07:00 AM
Slow / unresponsive clustered from 3 sources across 23 signals. Suppressed 22 redundant alerts and flagged flapping behavior.
- Aug 14, 07:00 AM
Root cause: Widespread slow/unresponsive issues on GitHub, potentially due to a core service problem or flapping behavior.