Disruption with some GitHub services in the EU region

What to do

• Check whether you use GitHub Packages in eu. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 14m it lasted.

  Anything that failed between 2026-06-06 16:53 UTC and 2026-06-06 17:07 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 3

1. investigatingJun 6, 2026, 4:53 PM UTC

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

   provider

2. investigatingJun 6, 2026, 4:56 PM UTC

   Packages is experiencing degraded performance. We are continuing to investigate.

   provider

3. resolvedJun 6, 2026, 5:07 PM UTC

   On June 6, 2026 between 16:18 UTC and 17:01 UTC, users experienced elevated error rates when performing Git operations (cloning, fetching, downloading archives) and accessing package registries. The issue affected users whose traffic was routed through our European infrastructure. During this time, on average 0.95% of Codeload requests and 9.2% of Package Registry requests failed with server errors. At peak, the Codeload error rate reached 1.76% and Package Registry errors reached 27%. The root cause was a planned network circuit migration that disrupted connectivity at one of our points of presence. Our process for shifting traffic away from the site did not operate as expected, resulting in a small amount of production traffic to continue being serviced at the effected site during the maintenance window. The issue was mitigated by rolling back the network change, restoring normal connectivity. Services fully recovered by 17:01 UTC. To reduce the likelihood of similar incidents in the future, we are reviewing our site drain process to make it more verbose and add visibility so any unexpected behavior is caught earlier.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.