GitHub Copilot · 76d ago
Disruption with some GitHub services
ResolvedYes — GitHub Copilot had a problem on July 24, 2026, and GitHub Copilot has since marked it resolved. GitHub Copilot's latest word: “On July 24th at 16:04 UTC, a loss of connectivity occurred in network paths in one of our three physical data center availability zones (AZs). This resulted in packet loss due to the remaining active paths becoming saturated. Our data centers use a leaf-spine switch fabric in each compute cage, and an aggregation layer interconnecting the spines from each cage within each AZ. The loss of connectivity affected links between one cage’s spine switches and the aggregation layer within that specific AZ. <br /><br />Workloads depending on compute resources in this cage became degraded due to packet loss, and exhibited intermittent errors: <br /><br />- Actions saw 10% of jobs fail during the impact window, and 5% of jobs succeeded but with delayed starts. <br />- 27% of GitHub issues interactions saw slow requests or timeouts. <br />- 4% of GitHub Copilot requests experienced errors, though most automatically retry. <br />- 4% of git push operations saw impacts during the affected window. <br />- Authentication requests saw increased latency during the affected window, but error rates, while elevated, were < 1% in all cases. <br /><br />We were able to mitigate the outage by re-routing affected connections to available fiber paths that were allocated for future capacity upgrades. Sufficient network capacity to eliminate packet loss was restored at 17:07, with most services showing full recovery by 17:16. All paths were restored and services healthy at 17:36. <br /><br />This incident affected 25% of available network interconnect capacity. Older cages utilize a 100Gbps network interface standard. To remove risk of reoccurrence, a planned upgrade to 400Gbps interfaces is being accelerated as much as possible, ensuring increased bandwidth available at all layers of the switch fabric for resiliency to path or device loss.”
Timeline
Started: 7/24/2026, 4:17:31 PM
Last update: 7/29/2026, 2:36:25 AM
Resolved: 7/24/2026, 5:36:50 PM
Affected: brv1bkgrwx7q, kr09ddfgbfsf, hhtssxt0f5v2, br0l2tvcx85d, vg70hn9s2tyj, pjmpxvq2cmr2
Updates
resolved
On July 24th at 16:04 UTC, a loss of connectivity occurred in network paths in one of our three physical data center availability zones (AZs). This resulted in packet loss due to the remaining active paths becoming saturated. Our data centers use a leaf-spine switch fabric in each compute cage, and an aggregation layer interconnecting the spines from each cage within each AZ. The loss of connectivity affected links between one cage’s spine switches and the aggregation layer within that specific AZ. <br /><br />Workloads depending on compute resources in this cage became degraded due to packet loss, and exhibited intermittent errors: <br /><br />- Actions saw 10% of jobs fail during the impact window, and 5% of jobs succeeded but with delayed starts. <br />- 27% of GitHub issues interactions saw slow requests or timeouts. <br />- 4% of GitHub Copilot requests experienced errors, though most automatically retry. <br />- 4% of git push operations saw impacts during the affected window. <br />- Authentication requests saw increased latency during the affected window, but error rates, while elevated, were < 1% in all cases. <br /><br />We were able to mitigate the outage by re-routing affected connections to available fiber paths that were allocated for future capacity upgrades. Sufficient network capacity to eliminate packet loss was restored at 17:07, with most services showing full recovery by 17:16. All paths were restored and services healthy at 17:36. <br /><br />This incident affected 25% of available network interconnect capacity. Older cages utilize a 100Gbps network interface standard. To remove risk of reoccurrence, a planned upgrade to 400Gbps interfaces is being accelerated as much as possible, ensuring increased bandwidth available at all layers of the switch fabric for resiliency to path or device loss.
7/24/2026, 5:36:50 PM
investigating
We are seeing recovery across all services
7/24/2026, 5:24:27 PM
investigating
The degradation affecting API Requests, Actions, Copilot, Issues, Pages and Pull Requests has been mitigated. We are monitoring to ensure stability.
7/24/2026, 5:16:44 PM
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
7/24/2026, 4:41:59 PM
investigating
We have applied a mitigation and are monitoring for recovery
7/24/2026, 4:40:27 PM
investigating
Actions is experiencing degraded availability. We are continuing to investigate.
7/24/2026, 4:28:37 PM
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
7/24/2026, 4:27:51 PM
investigating
Copilot is experiencing degraded performance. We are continuing to investigate.
7/24/2026, 4:26:47 PM
investigating
We are investigating timeouts to some GitHub services
7/24/2026, 4:22:37 PM
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
7/24/2026, 4:20:10 PM
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
7/24/2026, 4:19:39 PM
investigating
We are investigating reports of degraded performance for API Requests and Issues
7/24/2026, 4:17:31 PM
More GitHub Copilot incidents
- Incident with Actions, Pull Requests and Issues — resolved, 1d ago
- Incident with Git Operations, Pull Requests and Actions — resolved, 6d ago
- Incident with Git Operations, Issues, Actions and Pull Requests — resolved, 6d ago
- Several services are degraded — resolved, 7d ago
- Actions Job Delays — resolved, 12d ago
- Disruption with some GitHub services — resolved, 8d ago