Between approximately 14:00 and 16:10 UTC on May 5, 2026, SSH-based Git operations experienced elevated latency and intermittent failures. On average, the error rate was 0.46% and peaked at 0.6% of SSH write requests. HTTP-based Git operations, including web UI and HTTPS clones, were not affected.
The impact was caused by reduced SSH capacity at one of our data center sites. During a period of high traffic, the remaining hosts became overloaded, leading to connection exhaustion and some failures for SSH-based operations.
Additional capacity was provisioned to expand SSH capacity and resolve the incident. The expanded capacity was fully online by 18:18 UTC.
To reduce the likelihood of similar incidents, we will implement faster scaling solutions for SSH infrastructure and improved alerting for host availability and capacity thresholds.
Posted May 05, 2026 - 18:35 UTC
We've completed our mitigation to prevent further impact. At this time the incident is considered resolved.
Posted May 05, 2026 - 18:35 UTC
The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
Posted May 05, 2026 - 18:25 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.
Posted May 05, 2026 - 17:26 UTC
Git Operations is experiencing degraded performance. We are continuing to investigate.
Posted May 05, 2026 - 17:23 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.
Posted May 05, 2026 - 16:54 UTC
We are investigating reports of impacted performance for some GitHub services.
Posted May 05, 2026 - 16:49 UTC
This incident affected: Git Operations.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。