tickerr
Degraded PerformanceResolvedOfficial report

Git operations for users in the west coast are experiencing an increase in latency

Started

Thursday, March 19, 2026

04:25 PM UTC

Duration

7h 40m

total

Resolved

12:05 AM UTC

Friday, March 20, 2026

Incident update

On March 19, 2026 between 16:10 UTC and 00:05 UTC (March 20), Git operations (clone, fetch, push) from the US west coast experienced elevated latency and degraded throughput. Users reported clone speeds dropping from typical speeds to under 1 MiB/s in extreme cases. The root cause was network transport link saturation at our Seattle edge site, where a fiber cut affecting our backbone transport resulted in saturation and packet loss. We had a planned scale-up in progress for the site that was accelerated to resolve the backbone capacity pressure. We also brought online additional edge capacity in a cloud region and redirected some users there. Current scale with the upgraded network capacity is sufficient to prevent reoccurrence, as we upgraded from 800Gbps to 3.2Tbps total capacity on this path. We will continue to monitor network health and respond to any further issues.

GitHub Copilot is back online

View current status and uptime history

GitHub Copilot status →

Other GitHub Copilot incidents

Degraded Performance
Disruption with some GitHub services
Apr 14, 2026
Major Outage
Incident with Pages
Apr 13, 2026
Degraded Performance
Disruption with some GitHub services
Apr 13, 2026
Degraded Performance
Problems with third-party Claude and Codex Agent sessions not being listed in the agents tab dashboard
Apr 10, 2026
Major Outage
Disruption with some GitHub services
Apr 9, 2026

View all GitHub Copilot incident history →