noneresolved

GitHub outage on 2026-08-21: Degraded Git Operations over SSH

Started
Resolved
Duration
0m

Latest update from GitHub

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.

GitHub's own report for this incident

Was your service affected by this GitHub outage?

PingView checks your endpoints every minute from four regions and keeps screenshot evidence, so you can tell a vendor outage apart from your own regression.

Start monitoring free

Other GitHub incidents

See the full GitHub outage history