GitHub Service Disruption: Two Incidents Affected Multiple Services on February 9, 2026
By
Nezteb
Lightly toasted, lightly seasoned, mostly correct.
Summary
GitHub experienced two periods of service degradation on February 9, 2026, affecting multiple services including GitHub.com, GitHub API, GitHub Actions, Git operations, and GitHub Copilot. The first incident lasted from 16:12 to 17:39 UTC, and the second from 18:53 to 20:09 UTC, totaling approximately 2 hours and 43 minutes of degraded service. Users encountered errors loading pages, failures when pushing or pulling code, and issues with various GitHub services during these incidents.
Key quotes
· 4 pulledOn February 9, 2026, GitHub experienced two related periods of degraded availability affecting GitHub.com, the GitHub API, GitHub Actions, Git operations, GitHub Copilot, and other services.
The first period occurred between 16:12 UTC and 17:39 UTC, and the second between 18:53 UTC and 20:09 UTC.
In total, users experienced approximately 2 hours and 43 minutes of degraded service across the two incidents.
During both incidents, users encountered errors loading pages on GitHub.com, failures when pushing or pulling code, and issues with various GitHub services.
You might also wanna read
GitHub Actions suffers three-hour outage with false 'account suspended' error
GitHub Actions experienced a major outage lasting over three hours, during which users saw an alarming but incorrect error message stating "
theregister.com·2d ago
GitHub patches critical remote code execution vulnerability in under six hours after AI-assisted discovery
GitHub patched a critical remote code execution vulnerability in under six hours last month. The flaw, discovered by Wiz Research using AI m
The Verge·1mo ago