IPVanish Test Results

PPG tested IPVanish Paid on Windows using WireGuard across five standardized regions. IPVanish performed particularly well on nearby European routes, retaining 94.82% of baseline download speed in Sweden and 95.29% in Germany. The UK result was lower at 73.02%, while US East and Singapore showed the much larger performance drop expected from substantially longer Sweden-origin network paths.

All five requested exit countries validated correctly and the fixed-target stability probes recorded 0% packet loss in every region. WebRTC testing showed only the VPN public IPv4 address while connected. DNS and IPv6 could not be conclusively scored because the VPN-off baseline did not provide the evidence needed for a reliable pass/fail comparison.

What Our IPVanish Test Showed

• Germany produced the best download retention: 100.08 Mbps from a 105.03 Mbps baseline.
• Sweden was nearly as strong: 99.59 Mbps download and 100.67 Mbps upload.
• UK retention dropped to 73.02%: still substantially better than the distant US East and Singapore routes.
• All five locations validated: the observed VPN exit country matched the requested country in every test.
• Stability was clean: 0% packet loss and no detected latency spikes across the standardized fixed-target probes.
• WebRTC passed the machine-scored IPv4 check: only a VPN public IPv4 candidate was observed while connected.
• DNS and IPv6 remain inconclusive: the baseline did not support a defensible leak pass/fail classification.
• Kill switch was not tested: no kill-switch conclusion should be inferred from this dataset.

IPVanish Speed Test Results

The VPN-off baseline was 105.03 Mbps download and 105.26 Mbps upload. Each VPN location was measured with three standardized speed runs after connection stabilization, and the table below uses the median result.

Nearby European performance

Germany was the strongest measured IPVanish route, retaining 95.29% of baseline download throughput. Sweden followed at 94.82%. Upload performance was also strong: 98.82 Mbps in Germany and 100.67 Mbps in Sweden from a 105.26 Mbps baseline.

The UK produced a larger reduction, with 76.69 Mbps download and 75.30 Mbps upload. Its 73.02% download retention remains respectable but is materially below the Sweden and Germany results.

IPVanish Latency, Jitter and Stability

PPG records two different latency views. Regional Speedtest latency measures the route to the selected benchmark infrastructure, while a separate fixed-target ICMP probe measures tunnel stability against the same target. These values should not be described as latency to a specific game server.

The VPN-off fixed-target baseline was approximately 9 ms. Sweden added about 7 ms to the ICMP median and remained tightly grouped at a 17 ms p95. Germany and the UK also showed stable probes with no packet loss or detected spikes.

US East and Singapore predictably added much more latency because packets had to travel considerably farther from the Swedish test location. The important stability result is that neither route showed packet loss during the standardized probe.

IPVanish Server Location Validation

Every requested country passed PPG’s multi-source exit-country validation.

Result: 5/5 validated. This indicates that the tested IPVanish exits appeared in the requested countries across the geolocation sources used by the PPG runner.

DNS Leak Test

IPLeak reported no usable public DNS resolvers during the VPN-off baseline despite retrying the observation. VPN-connected resolver observations were available, but without a comparable baseline resolver set there is no defensible way to determine whether the VPN reused or exposed the baseline resolver.

BrowserLeaks and local Windows DNS configuration provided supporting observations, but they do not override the missing scoring baseline. For that reason, the correct classification is INCONCLUSIVE_BASELINE_NO_PUBLIC_RESOLVERS_DETECTED.

This is important: inconclusive does not mean leak detected, and it also does not justify claiming that IPVanish passed the DNS leak test.

WebRTC Test

The VPN-off baseline showed the normal public IPv4 address. In each tested VPN region, the WebRTC evidence corresponded to the VPN-connected public IPv4 path. That supports a WebRTC IPv4 pass for this specific Windows test configuration.

IPv6 Test

The baseline environment did not expose a usable public IPv6 address and direct IPv6 probes were unsuccessful. Because the VPN-off connection lacked a valid public IPv6 baseline, the runner could not determine whether IPVanish changed, blocked or leaked an otherwise functioning public IPv6 path.

There were no global IPv6 addresses or usable IPv6 default route in the local evidence, but this still does not justify calling the VPN’s IPv6 handling a pass.

IPVanish Connection Time

PPG measures connection time by observing when the public IP changes to the requested VPN route.

The UK connected fastest in this batch at approximately 3.44 seconds. Sweden and US East were close to five seconds, while Germany and Singapore took considerably longer.

Connection timing can vary between individual servers, sessions and network conditions, so these figures describe this test batch rather than a guaranteed connection time.

Kill Switch

IPVanish Test Summary

How PPG Tested IPVanish

The test methodology intentionally separates throughput, regional latency, fixed-target stability, location validation and security observations. One measurement is not used as a substitute for another.

For example, fixed-target latency is useful for comparing tunnel stability, but it is not a measurement of a game server. Likewise, speed retention does not prove streaming access, and an inconclusive DNS or IPv6 observation is not converted into a pass or failure.

IPVanish Test Verdict

IPVanish delivered excellent nearby European performance in PPG’s September 2026 test. Germany retained 95.29% of baseline download speed and Sweden retained 94.82%, while both routes maintained high upload throughput. The UK showed a larger but still moderate reduction at 73.02%.

The stability results were also encouraging: all five fixed-target probes completed with 0% packet loss, and all five requested exit countries validated correctly. WebRTC exposed the VPN public IPv4 rather than the baseline public address in the tested Windows configuration.

The main limitations are evidentiary rather than automatically negative: DNS could not be conclusively scored because the baseline resolver set was unavailable, IPv6 lacked a valid public baseline, and the kill switch was not tested. US East and Singapore also showed substantial throughput reduction, but those routes are inherently disadvantaged by the fact that PPG’s test connection originates in Sweden.

Overall, the dataset makes IPVanish a particularly strong candidate when nearby European throughput and stable WireGuard routing are priorities.

FAQ: IPVanish Test Results