Help · Users

Speedtest

Measures download, upload, ping and jitter between this browser and ProofKit's servers. It goes through your VPN only when the VPN is on for the browser; the page checks where your traffic comes from and files signed-in runs under the exit they went through.

Open in the app All help topics
example
Seen from: DE · Cloudflare FRA  → matches your DE exit
Download 245 Mbps · Upload 180 Mbps
Ping 22 ms · Jitter 1.4 ms

The Speedtest page tests the path from this browser, through Cloudflare, to ProofKit's servers in Germany, and back. With the VPN on for this browser, that path runs through your exit (and through the entry node on a 2-hop route). With the VPN off, it measures your connection without ProofKit.

What is measured

  • Download and upload: data moved divided by the time it took, over up to 8 seconds each on parallel requests, after a short warm-up. A run moves at most 50 MB down and 20 MB up.
  • Ping: the median of 6 HTTP round trips to the server (not an ICMP ping).
  • Jitter: the average change between one round trip and the next.

Is my VPN on?

Before each run the page checks which country your traffic comes from and matches it against your active exits. A signed-in run is saved under an exit only when the countries match, or as a run without a ProofKit exit, which becomes your baseline. A run whose route the page cannot tell is not saved.

Reading the result

  • Run it once with the VPN off for a baseline, then with each exit.
  • A result far below the exit's own benchmark means the limit is before the exit: your line, the entry node, the transport, or the distance to Germany.
  • A distant exit shows a higher ping here than it has for sites near it.
  • The page can't see which transport your app uses. olcRTC travels inside a video call and is slower by design.
Through a paid route, test traffic is charged like any other traffic at your route's price. The page shows what your last run cost.