Why Kite
Pricing
Download
Blog Help
Back to Blog
Under the hood

Multi-hop routing explained: what the entry and exit server each do

Instead of one server doing everything, multi-hop routing splits the job between an entry server and an exit server. What that changes, what it does not, and what it costs.

Daniel Brooks
6 min read

In a simple setup, your device connects to one server, and that server connects onward to the website. It is the door in and the door out at the same time. Multi-hop routing splits those two jobs between two servers, and that small change has some useful effects.

Entry server and exit server

With multi-hop, your traffic takes a path with two servers:

  • The entry server is the one your device connects to. It receives your encrypted traffic and forwards it onward.
  • The exit server is the one that reaches the website or app you are using. To that destination, the connection appears to come from the exit server.

Your traffic stays encrypted between your device and the exit server, and the entry server only passes it along. So the entry server knows that you are connecting, but not what you are doing, while the exit server knows what is being requested, but not who you are.

Why it is useful

  • Knowledge is divided. No single server has both halves of the picture, which makes it harder for any one point on the path to connect you with your activity.
  • The route can be better. Between two distant places, a well-connected entry point can sometimes give a steadier path than a direct long-haul connection.
  • The service is more flexible. Entry points can be added or adjusted without changing the exit servers that you may have chosen for a rule.

What it costs

An extra hop is an extra stop, so multi-hop can add a little latency. In practice the difference depends on where the two servers are, which is one reason the Kite app measures latency to each server end to end rather than assuming that fewer hops are always faster.

How you will see it in Kite

You do not need to manage hops yourself. Servers that are reached through an entry server appear in the list like any other. With Auto Select turned on, the app picks according to the speed it actually measures, whichever kind of path that turns out to be.

When to care

  • If you simply want a fast, private connection, leave routing on Auto and ignore the details.
  • If you are curious about how your traffic travels, multi-hop is one reason a server in the list may behave differently from what its location suggests.
  • If you have a rule pinned to a specific server, it applies to that server’s whole path, entry and exit.

Daniel Brooks

Privacy & security writer

Daniel writes about online privacy, network security and how Kite works under the hood.

Browse with peace of mind

Encrypted connections, no record of your activity, and smart routing that keeps things fast. Try Kite free.