FOLLOW THE ROUTE, NOT THE HYPE
VPN speed by location and time
The same VPN can feel fast in one country and sluggish in another. Start with your test location, then compare how much of the original connection survives each VPN route.
Choose a test location
Waiting for live workers…
Choose a test worker to compare how much speed VPN exits keep throughout the day.
Map pins = available test workers. The highlighted pin is your test starting point.
Source: —| Metric: Speed kept vs. clean connection (%) Quality-checked results only
| Destination |
|---|
| Connecting to live benchmark data… |
Speed kept · your selected setup
Click any heatmap cell to see that exact destination and UTC block here. The clicked cell will be outlined in blue.
Green: 60–100% · Yellow: 40–59.9% · Red: below 40%. The full-comparison result above the table is separate.Your route at a glance
Your measured route summary will appear when the comparison data is ready.
Based on quality-checked benchmark samples for this selection, not a promise of your personal connection speed.
? How does this work?
See how a VPN performs from one test location to exit servers around the world, and how that changes through the day.
↕ Color shows how much speed the VPN keeps
Each cell shows how much download speed the VPN kept compared with the clean connection, for the selected test location, provider and protocol.
- Excellent≥ 80%
- Good60–80%
- Fair40–60%
- Poor20–40%
- Very Poor< 20%
- No usable data—
- Limited datan<3
Only tests that pass our quality checks are used here. A location needs at least 3 samples in a time block before it can qualify for the main rankings.
Best exits — selected time
at —
For this time: uses only the highlighted UTC time block, so you can see which VPN exits perform best around this time of day.
- Waiting for data…
Best exits overall
across selected data window
Across the full window: uses each exit location’s typical quality-checked result across the selected data window, rather than judging it from only one time block.
- Waiting for data…
Slowest exits — selected time
at —
Uses the same highlighted UTC block as the best-exit list, but shows the weakest measured results.
- Waiting for data…
Selected result details
- Source
- —
- VPN
- —
- Server tested
- —
- Connection endpoint
- —
- Target ID
- —
- Exit IP
- —
- Target
- —
- Detected VPN exit
- —
- Typical download speed
- —
- Speed kept
- —
- Typical upload speed
- —
- Typical latency
- —
- Extra latency from VPN
- —
- Packet Loss
- —
- Usable samples
- —
- Confidence
- —
Choosing a VPN?
We compare the VPNs and protocols measured from your selected test region, then show the strongest setup supported by the available data.
Already using a VPN?
Choose the VPN you already use. We compare its tested protocols from the same region, pick the strongest one, then show the best exit location for the selected time and for the full data window.
Why the test location matters
We measure the connection without a VPN first, then test the VPN from the same machine. That makes it easier to see how much performance the VPN actually keeps instead of comparing raw Mbps from very different connections.
Test location and VPN exit are different
The test location is where the connection starts. The VPN exit is where the tunnel ends. Keeping them separate shows how the same exit can behave differently from different parts of the world.
Quality checks before ranking
Tests with a bad baseline, excessive packet loss or other quality problems stay out of the main heatmap results until they pass our checks.
Protocols stay separate
Lightway, NordLynx, OpenVPN and WireGuard results are kept separate. Commercial relationships are not used to decide technical performance rankings.