已歸檔的官方INCIDENT

Degraded Git Operations over SSH

GitHub · 最近儲存的提供方狀態：resolved

官方來源文字以原始語言顯示。

這是歷史證據。

最近儲存的事件狀態不是當前服務狀態。來源列表可能不完整，事件從來源消失不確認恢復。請開啟當前報告或官方來源檢視較新證據。

已儲存事件詳情

The provider's end time precedes its start time. These reported timestamps do not establish a valid event duration.

提供方在此已儲存修訂中明確列出沒有受影響元件。

這些關聯描述此事件的報告範圍。不能確認當前元件可用性或已核實依賴關係。

記錄建立時間未必是故障開始時間。未報告的時間保持不可用。我們不根據收集時間計算故障時長。

最新優先。最多顯示最近 20 份已儲存內容修訂中的 100 條不同更新。同一提供方時間的文字修訂單獨保留。

resolved21 Aug 2026, 14:00:00 UTC
On August 21, 2026, between 14:00 and 14:07 UTC, dotcom Git operations over SSH were degraded. Successful Git operations over SSH fell by more than 95% for during the peak impact window, making clone, fetch, or push over SSH effectively unavailable to most users for approximately four minutes. Git operations over HTTPS were not affected. The incident was caused by a software defect in our load-balancing infrastructure that was triggered by a configuration change. The defect only occurred when connections passed through multiple layers of load balancers running the new configuration, which meant it was not detected during canary testing. We mitigated the incident by rolling back the configuration change. We are adding regression coverage for multi-layer load-balancer configurations and improving monitoring and alerting for Git operations over SSH to reduce our time to detection and mitigation of similar issues in the future.
在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到