Ordinary speed tests will show inaccurate results for tests on a network with Winston.

Here's why:

1) Your test traffic may be routed far from home because of Winston's IP scrambling

The Winston Distributed Privacy Mesh Network scrambles your internet activity across other Winstons, making your IP address impossible to locate. So, your IP address will appear to be elsewhere, possibly far from your actual location.

Speed tests select a server based on your detected IP address, so they may select a server far from you. The resulting latency and other network factors will impact the results of those tests, providing an inaccurate reflection of your actual upload/download speeds.

Selecting a test server close to your actual location may be far from the location of the IP address the test site detects, compounding the inaccuracy of the results.

2) Speed tests send traffic over the Distributed Privacy Mesh Network that Winston would normally handle locally

Winston sends internet traffic over the Distributed Privacy Mesh Network, except for large data transfers such as large file downloads and high-bandwidth streaming. Large data transfers are routed locally, like normal, non-Winston traffic.

Speed tests, however, send large bursts of small packets, which Winston doesn't recognize as a large data transfer. Winston therefore routes all that test traffic over the Distributed Privacy Mesh Network.

Winston's Distributed Privacy Mesh Network is optimized for low latency and fast response times, as it should be for the internet traffic it typically handles, not bandwidth speed which is important for large bursts of small packets (which is generally only used by speed tests) and large data transfers.