Provider incident title: “Degraded Git Operations over SSH”
Started
Friday, August 21, 2026
02:00 PM UTC
Duration
< 1 minute
total
Resolved
02:00 PM UTC
Aug 21, 2026
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.
Get alerted next time
Install Tickerr MCP — your agent auto-reports & routes around outages
When GitHub Copilot goes down again, your agent reports anonymously and instantly gets a fallback recommendation from the swarm.
GitHub Copilot is back online
View current status and uptime history
GitHub Copilot 30-day uptime: 100% based on Tickerr's independent monitoring checks.
This incident was sourced from GitHub Copilot's official Atlassian Statuspage. Tickerr ingests updates every 10 minutes to surface incidents as they are posted by the provider.
This incident lasted < 1 minute.
Tickerr monitors 90+ AI tools independently. View live GitHub Copilot status or all AI tool status.
Get alerted next time GitHub Copilot goes down
Tickerr monitors 90+ AI tools. We'll email you when an incident starts or resolves.
Weekly AI pricing & uptime digest
Price drops, new model releases, and incident summaries - every Monday. Free.
Also on Tickerr