GlossaryPrivacy & SecurityIntermediate

Multi-Hop VPN

A multi-hop VPN routes your traffic through two or more VPN servers instead of one, so no single server ever knows both who you are and what you are visiting.

Last updated July 29, 2026

Definition

A multi-hop VPN — also called double VPN or a VPN chain — sends your traffic through two or more VPN servers in sequence before it reaches the internet. A standard VPN uses one server; multi-hop adds at least one more in the middle.

The point is not extra encryption for its own sake. It is separation of knowledge. Splitting the journey means no single machine in the chain ever holds the complete picture.

Who knows what

  • The entry server sees your real IP address, because you connected to it directly — but it only sees traffic addressed to the next server, so it has no idea what you are ultimately visiting.
  • The exit server sees which sites you are reaching, because it makes the final request — but as far as it can tell, the traffic came from the entry server, not from you.
  • The website sees only the exit server's IP address.

To identify you, someone would have to compromise or subpoena both servers and correlate the two sets of records. If the servers sit in different countries under different legal jurisdictions, as good providers arrange, that becomes considerably harder.

How the encryption stacks

Your traffic is wrapped in layers, like nested envelopes. The entry server removes the outer layer and finds only an instruction to forward the remainder onward — it cannot read what is inside. The exit server removes the final layer and sends the request out. Each hop learns just enough to do its job and no more.

The cost

This protection is not free. Your data travels further and gets encrypted and decrypted more times, so expect meaningfully slower speeds and higher latency — often 30–50% slower than a single hop, sometimes more if the servers are far apart. Streaming, video calls, and gaming all suffer. Fewer server pairs are available, and not every provider offers the feature at all.

Multi-hop versus Tor

Tor routes through three relays run by unrelated volunteers, which removes the need to trust any single operator — stronger in principle, but much slower. Multi-hop VPN servers usually belong to one company, so you are still trusting that provider not to correlate its own two servers. It is faster and easier to use, but the trust model is weaker. Some people chain the two together for that reason.

Do you actually need it?

Honestly, most people do not. For ordinary privacy, streaming, or public Wi-Fi safety, a single well-run VPN with a no-logs policy and a working kill switch is enough, and the speed you keep is worth more day to day. Multi-hop earns its cost when the consequences of being identified are severe — journalists protecting sources, activists under hostile governments, researchers investigating dangerous infrastructure — or when you specifically want to spread trust across jurisdictions.

Examples

1

Connecting through a Swiss entry server and exiting in Sweden, so neither country's server holds the full picture

2

NordVPN's Double VPN and Surfshark's MultiHop, both offering preset two-server routes inside the app

3

A journalist routing research through two jurisdictions so no single legal request can unmask the session

4

Chaining a VPN into Tor so the entry relay sees the VPN server rather than the user's home connection

Common Use Cases

Journalism and source protection
Activism in countries with heavy surveillance
Security research into hostile infrastructure
Spreading trust across separate legal jurisdictions
Situations where a single compromised server would be unacceptable
Adding distance between your identity and a sensitive session

Frequently Asked Questions

Not twice, and not in a way that helps most people. The gain is that no single server knows both your identity and your destination, which protects against one server being compromised or subpoenaed. Against everyday threats a single good VPN is already sufficient.
Expect roughly 30–50% slower than a single hop, sometimes worse when the two servers sit far apart. Your traffic covers more distance and is encrypted and decrypted more times, so latency rises noticeably — enough to affect calls, gaming, and high-quality streaming.
Different trade-offs. Tor uses three relays run by unrelated volunteers, so you trust no single operator, but it is slow. Multi-hop is far faster and easier, yet both servers usually belong to one company, so you are still trusting that provider.
Probably not. For streaming, public Wi-Fi, and general privacy, one reliable no-logs VPN with a kill switch does the job and keeps your speed. Multi-hop is worth it when being identified would carry serious consequences.
Yes — running one VPN inside a virtual machine connected to another creates a chain across two companies, which removes the single-provider trust problem. It is fiddly to set up and slower still, but the trust model is genuinely stronger.
No. Your network operator can still tell you are connected to a VPN server, because that first hop looks the same as any other VPN connection. To disguise VPN use itself you need obfuscated servers, which is a separate feature.