Is GitHub Copilot Down?

Mar 20 , 01:58 UTC Resolved - On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average error rate was ~53% and peaked at ~93% of requests to the service. During the second incident, the average error rate was ~99%% and peaked at ~100%% of requests with significant retry amplification. Both incidents were caused by the same underlying system authentication issue that prevented the service from connecting to its backing datastore. We mitigated each incident by rotating the affected credentials, which restored connectivity and returned error rates to normal. The mitigation time was 01:24. The second occurrence was due to an incomplete remediation of the first. We are implementing automated monitoring for credential lifecycle events and improving operational processes to reduce our time to detection and mitigation of issues like this one in the future. Mar 20 , 01:26 UTC Update - We are rolling out our mitigation and are seeing recovery. Mar 20 , 01:00 UTC Update - We are seeing widespread issues starting and viewing Copilot Agent sessions. We understand the cause and are working on remediation. Mar 20 , 00:58 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Mar 20 , 00:05 UTC Resolved - 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. Mar 20 , 00:05 UTC Update - We have reached stability with git operations through our changes deployed today. Mar 19 , 23:52 UTC Update - We are seeing early signs of improvement. We are working on one more small change to further improve traffic routing on the west coast. Mar 19 , 22:57 UTC Update - We have completed the rollout of our new network path and are monitoring its impact. Mar 19 , 21:59 UTC Update - We are beginning the rollout of our new network path. During this change, users will continue to see higher latency from the west coast. We will provide another update when the rollout is complete. Mar 19 , 18:27 UTC Update - We are working to enable a new network path in the west coast to reduce load and will monitor the impact on latency for Git Operations Mar 19 , 17:49 UTC Update - We are still seeing elevated latency for Git operations in the west coast and are continuing to investigate Mar 19 , 17:01 UTC Update - We are redirecting traffic back to our Seattle region and customers should see a decrease in latency for Git operations Mar 19 , 16:25 UTC Invest

Mar 19 , 14:32 UTC Resolved - On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average error rate was ~53% and peaked at ~93% of requests to the service. During the second incident, the average error rate was ~99%% and peaked at ~100%% of requests with significant retry amplification. Both incidents were caused by the same underlying system authentication issue that prevented the service from connecting to its backing datastore. We mitigated each incident by rotating the affected credentials, which restored connectivity and returned error rates to normal. The mitigation time was 01:24. The second occurrence was due to an incomplete remediation of the first. We are implementing automated monitoring for credential lifecycle events and improving operational processes to reduce our time to detection and mitigation of issues like this one in the future. Mar 19 , 14:06 UTC Update - Copilot is operating normally. Mar 19 , 14:02 UTC Update - We are investigating reports that Copilot Coding Agent session logs are not available in the UI. Mar 19 , 13:45 UTC Update - Copilot is experiencing degraded performance. We are continuing to investigate. Mar 19 , 13:44 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.