Multi-hop VPN routes traffic through two or more VPN servers in sequence rather than one. The first server sees the user’s IP and connects to the second server; the second server sees the first server’s IP and connects to the destination. Neither server alone has both the source identity and the destination. Offered by Mullvad, Proton VPN, NordVPN (Double VPN), and Surfshark (MultiHop) at varying technical-quality levels.
What it means in practice
The structural defense multi-hop adds: a single subpoena to either VPN provider returns less than a single subpoena to a single-hop VPN. The first-hop provider has source IP plus destination of the second-hop server. The second-hop provider has the second-hop entry IP plus the destination. Reconstructing the chain requires compelling both providers, ideally simultaneously, ideally in jurisdictions that cooperate. The trade-off is performance: each hop adds 20 to 100ms of latency and reduces throughput, multi-hop in practice is 30 to 50% slower than single-hop. The further trade-off: if both hops are owned by the same provider (Mullvad multi-hop, Proton VPN Secure Core), the legal compulsion is the same as single-hop unless the provider runs the second hop in a different legal entity.
Who uses it, and against whom
Used by: high-target operators where single-jurisdiction subpoena reach is the threat model (journalists working with hostile-state sources, activists in monitored regions, security researchers exposing nation-state operations), Tor users who want VPN-over-Tor or Tor-over-VPN configurations for traffic-correlation defense, and privacy-conscious users who accept the speed cost for the architectural improvement. Less useful for: streaming, gaming, video calls (the latency is felt), and most threat models where single-hop with audited no-logs already addresses the operational concern. Predaxia’s editorial position: multi-hop is the right tool for the right threat tier and the wrong tool for casual privacy use.
What you can change today
If your threat model includes nation-state subpoena reach across jurisdictions, multi-hop adds meaningful protection. Mullvad: enable multi-hop in Settings, where you can chain entry and exit servers from different countries (Germany entry, Sweden exit is the canonical Mullvad multi-hop). Proton VPN: Secure Core feature routes through Iceland, Switzerland, or Sweden as the entry hop before the exit. For higher-tier configurations: Tor over VPN (connect Mullvad first, then Tor Browser) gives jurisdiction-distributed three-hop Tor routing on top of an audited VPN; the latency is significant but the architectural defense is meaningful. For most readers: single-hop to Mullvad or Proton VPN is the operational default; multi-hop is an upgrade for specific threat scenarios.