Common destinations used
Waiting for data…
QC rankable only · same-worker ranking
NordVPN vs ExpressVPN →
Independent VPN Speed Rankings
This is not a raw-Mbps leaderboard. Every ranked provider/protocol is scored on the same well-sampled VPN destinations from one physical benchmark worker, so broader or easier destination catalogs cannot inflate the result.
Status—Waiting for data
Shared destination set—Equal weight per destination
Eligible candidates—Provider + protocol pairs
Source——
Coverage-balanced ranking
Loading ranking policy…
| Rank | Provider | Protocol | Balanced retention | Common exits | Rankable samples | Median latency | Confidence |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Excluded from headline ranking
Candidates without enough destination coverage appear here.
How the ranking avoids common VPN benchmark bias
No cross-worker mixing
A Germany source result is never blended with a US source result. Changing source worker creates a separate ranking.
Same destination set
A provider is not rewarded for having data only on nearby or fast exits. Headline candidates must share the same eligible destination intersection.
QC before ranking
Only measurement_quality.rankable = TRUE measurements contribute. Each destination is reduced to a median score and every destination gets equal weight.