GitHub incident
Increased Latency and Failures for SSH Git Operations
GitHub experienced a minor incident on May 5, 2026 affecting Git Operations, lasting 1h 46m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 05, 2026, 04:49 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- monitoring May 05, 2026, 04:54 PM UTC
Between approximately 14:00 and 16:10 UTC, customers using SSH-based Git operations may have experienced elevated latency and failures. HTTP-based operations were not impacted. We've identified a suspected root cause and are working to implement a mitigation to prevent further impact.
- investigating May 05, 2026, 05:23 PM UTC
Git Operations is experiencing degraded performance. We are continuing to investigate.
- investigating May 05, 2026, 05:26 PM UTC
We're continuing to work on preventing further impact from the earlier issue. No SSH-based impact is expected at this time. We'll post new updates if impact recurs or once our mitigation is in place.
- monitoring May 05, 2026, 06:25 PM UTC
The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
- monitoring May 05, 2026, 06:35 PM UTC
We've completed our mitigation to prevent further impact. At this time the incident is considered resolved.
- resolved May 05, 2026, 06:35 PM UTC
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.