Why Git Is Slow on VPN

Git transfers thousands of small objects during clone and fetch operations. Each object requires a network round trip. VPN adds latency to every single one.

• •

  Clone a repo: thousands of object transfers

• •

  Each transfer: added VPN latency overhead

• •

  Large repos: minutes become hours

• •

  Push and pull: same problem

Symptoms of VPN Git Slowdown

You'll recognize these:

• •

  git clone hangs at "Receiving objects"

• •

  Progress crawls: 1%... 2%... 3%...

• •

  Timeouts on large repositories

• •

  git pull takes minutes for small changes

• •

  git push fails with timeout errors

Measuring the Impact

# Off VPN - baseline
time git clone https://github.com/facebook/react.git

# On VPN - compare
rm -rf react
time git clone https://github.com/facebook/react.git

Often 5-10x slower on VPN. Large repos make it painfully obvious.

Fix 1: Shallow Clone

Reduce the number of objects transferred:

# Clone only recent history
git clone --depth 1 https://github.com/user/repo.git

# Or limit to single branch
git clone --single-branch https://github.com/user/repo.git

Fewer objects = faster clone. But you lose git history.

Fix 2: Increase Git Timeouts

Prevent git from giving up:

git config --global http.lowSpeedLimit 0
git config --global http.lowSpeedTime 999999

Fix 3: Use SSH Instead of HTTPS

Sometimes SSH routes differently than HTTPS:

git clone git@github.com:user/repo.git

Results vary depending on VPN configuration. Worth trying.

Fix 4: Route Terminal Direct (Best)

The most effective fix: route your Terminal outside the VPN tunnel.

Git Services That Benefit

Route Terminal direct and all these speed up:

• •

  GitHub (github.com)

• •

  GitLab (gitlab.com)

• •

  Bitbucket (bitbucket.org)

• •

  Azure DevOps

• •

  Any public git hosting

Corporate Git Repositories

If your company hosts internal git repos that require VPN access:

• •

  Keep Terminal on VPN when working with internal repos

• •

  Route Terminal direct for public repos (GitHub, etc.)

• •

  Toggle routing based on what you're working on

SplitTunnel makes switching easy.

Git LFS and Large Files

Git LFS is especially affected by VPN slowdown. Large binary files + VPN latency = painful waits.

# After setting up SplitTunnel
git lfs pull  # Much faster

Binary assets that took minutes now download in seconds.

Verifying the Fix

After setting up SplitTunnel with Terminal routed direct:

# Connect VPN

# Clone a large repo
time git clone https://github.com/facebook/react.git

# Should match non-VPN speeds