← Back to GitHub History
none✓ Resolved

Degraded Git Operations over SSH

GitHub•
Status
resolved
Duration
Duration unavailable
Updates
1
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
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.

📊 TECHNICAL DETAILS

Internal ID
f6b3e630-4105-4a3b-a0c1-34261b5e1c19
External ID
wms44hv62t3p
🕐 Started
🔄 Last Updated
✓ Resolved
NONE
Impact Level
Duration unavailable
Total Duration
1
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed