Disruption with some GitHub services in the EU region
This summary is created by Generative AI and may differ from the actual content.
Overview
On June 6 2026, between 16:18 UTC and 17:01 UTC, GitHub users whose traffic was routed through the European infrastructure experienced elevated error rates for Git operations (cloning, fetching, downloading archives) and Package Registry accesses. Average failure rates were 0.95 % for Codeload requests and 9.2 % for Package Registry requests, peaking at 1.76 % and 27 % respectively. The incident was caused by a planned network circuit migration that broke connectivity at a point‑of‑presence, and the traffic‑drain process failed to fully divert traffic away from the affected site. Rolling back the network change restored connectivity, and services recovered by 17:01 UTC.
Impact
The incident affected Git operations and Package Registry services for users routed through the EU region, resulting in up to 27 % of Package Registry requests failing with server errors and up to 1.76 % of Codeload requests failing at peak. No further quantitative impact such as data loss or revenue impact was reported in the postmortem.
Trigger
A planned network circuit migration disrupted connectivity at one of GitHub’s European points of presence.
Detection
GitHub staff became aware of the issue through internal reports and status‑page updates indicating degraded performance for Git and Package Registry services, with investigation beginning around 16:53 UTC.
Resolution
The network change was rolled back, restoring normal connectivity to the affected point of presence. All services returned to normal operation by 17:01 UTC.
Root Cause
The migration of a network circuit caused a loss of connectivity at a point of presence, and the process intended to shift traffic away from that site did not operate as expected, allowing a portion of production traffic to continue being served by the affected location.