Disruption with some GitHub services

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

Git Operations is experiencing degraded performance. We are continuing to investigate.

Git Operations is experiencing degraded performance. We are continuing to investigate.

Git Operations is experiencing degraded performance. We are continuing to investigate.

Git Operations is experiencing degraded performance. We are continuing to investigate.

Git Operations is experiencing degraded performance. We are continuing to investigate.

Git Operations is experiencing degraded performance. We are continuing to investigate.

Git Operations is experiencing degraded performance. We are continuing to investigate.

Git Operations is experiencing degraded performance. We are continuing to investigate.

Git Operations is experiencing degraded performance. We are continuing to investigate.

Git Operations is experiencing degraded performance. We are continuing to investigate.

Git Operations is experiencing degraded performance. We are continuing to investigate.

We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

We are continuing to investigate degraded performance for git operations from the US West Coast.

We are continuing to investigate degraded performance for git operations from the US West Coast.

We are continuing to investigate degraded performance for git operations from the US West Coast.

We are continuing to investigate degraded performance for git operations from the US West Coast.

We are continuing to investigate degraded performance for git operations from the US West Coast.

We are continuing to investigate degraded performance for git operations from the US West Coast.

We are continuing to investigate degraded performance for git operations from the US West Coast.

We are continuing to investigate degraded performance for git operations from the US West Coast.

We are continuing to investigate degraded performance for git operations from the US West Coast.

We are continuing to investigate degraded performance for git operations from the US West Coast.

We are continuing to investigate degraded performance for git operations from the US West Coast.

We continue to investigate degraded performance for git operations from the US West Coast.

We continue to investigate degraded performance for git operations from the US West Coast.

We continue to investigate degraded performance for git operations from the US West Coast.

We continue to investigate degraded performance for git operations from the US West Coast.

We continue to investigate degraded performance for git operations from the US West Coast.

We continue to investigate degraded performance for git operations from the US West Coast.

We continue to investigate degraded performance for git operations from the US West Coast.

We continue to investigate degraded performance for git operations from the US West Coast.

We continue to investigate degraded performance for git operations from the US West Coast.

We continue to investigate degraded performance for git operations from the US West Coast.

We continue to investigate degraded performance for git operations from the US West Coast.

We continue to investigate the slow performance of Git Operations affecting the US West Coast.

We continue to investigate the slow performance of Git Operations affecting the US West Coast.

We continue to investigate the slow performance of Git Operations affecting the US West Coast.

We continue to investigate the slow performance of Git Operations affecting the US West Coast.

We continue to investigate the slow performance of Git Operations affecting the US West Coast.

We continue to investigate the slow performance of Git Operations affecting the US West Coast.

We continue to investigate the slow performance of Git Operations affecting the US West Coast.

We continue to investigate the slow performance of Git Operations affecting the US West Coast.

We continue to investigate the slow performance of Git Operations affecting the US West Coast.

We continue to investigate the slow performance of Git Operations affecting the US West Coast.

We continue to investigate the slow performance of Git Operations affecting the US West Coast.

We are seeing recovery in git operations for customers on the West Coast of the US.

We are seeing recovery in git operations for customers on the West Coast of the US.

We are seeing recovery in git operations for customers on the West Coast of the US.

We are seeing recovery in git operations for customers on the West Coast of the US.

We are seeing recovery in git operations for customers on the West Coast of the US.

We are seeing recovery in git operations for customers on the West Coast of the US.

We are seeing recovery in git operations for customers on the West Coast of the US.

We are seeing recovery in git operations for customers on the West Coast of the US.

We are seeing recovery in git operations for customers on the West Coast of the US.

We are seeing recovery in git operations for customers on the West Coast of the US.

We are seeing recovery in git operations for customers on the West Coast of the US.

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.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

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.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

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.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

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.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

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.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

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.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

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.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

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.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

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.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

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.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

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.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7