Slow speed result with SpeedTest test

SpeedTest selects your server based on GeoLocation, Your VPSes physical location may NOT match with the GeoLocation (set on the IP address) in few cases, in these cases, SpeedTest auto selects a server that may be far away from your existing VPSes physical location.

In this example,

VPS "LA" is located in Los Angeles, California, but when looking up in SpeedTest for servers in Los Angeles, we see the distance as 3800+ KM! This is due to the GeoLocation of the VPSes IP address.

Note: If your VPS IP is not GeoLocated correctly to the physical address of the service, we can change the IP for you via ticket if you want this. GeoLocation of the VPS IP does NOT affect its speed or its ping in reality!

[[email protected] ~]# ./speedtest-cli --list | grep "Los Angeles"
 5827) Time Warner Cable (Los Angeles, CA, United States) [3857.64 km]
 3226) Race Communications (Los Angeles, CA, United States) [3857.64 km]
10392) Speedtest.net (Los Angeles, CA, United States) [3857.64 km]
 5031) AT&T (Los Angeles, CA, United States) [3857.64 km]
 2953) Atlantic Metro (Los Angeles, CA, United States) [3857.64 km]
11482) Race Communications (Los Angeles, CA, United States) [3857.64 km]
 6047) Phyber Communications (Los Angeles, CA, United States) [3857.64 km]
 5303) Host Duplex (Los Angeles, CA, United States) [3857.64 km]
 7244) psychz.net (Los Angeles, CA, United States) [3857.64 km]
 3883) SingTel (Los Angeles, CA, United States) [3857.64 km]
 7456) QuadraNet, Inc (Los Angeles, CA, United States) [3857.64 km]
 3864) California Internet Solutions (Los Angeles, CA, United States) [3857.64 km]
 5861) WebNX (Los Angeles, CA, United States) [3857.64 km]
 6248) GorillaServers (Los Angeles, CA, United States) [3857.64 km]
 5905) GigeNET (Los Angeles, CA, United States) [3857.64 km]
10269) Interoute VDC (Los Angeles, CA, United States) [3857.64 km]
13516) Xfernet (Los Angeles, CA, United States) [3857.64 km]
13301) LINK Telecom (Los Angeles, CA, United States) [3857.64 km]
15671) Aspiration Hosting (Los Angeles, CA, United States) [3857.64 km]
 9916) fdcservers.net (Los Angeles, CA, United States) [3857.64 km]
 7190) Sharktech Inc. (Los Angeles, CA, United States) [3857.64 km]
15149) IT&E (Los Angeles, CA, United States) [3857.64 km]
 7048) FPT Telecom (Los Angeles, CA, United States) [3857.64 km]

Next, we run a test with server #5861, again, only 23 milliseconds away!,

[[email protected] ~]# ./speedtest-cli --server 5861
Retrieving speedtest.net configuration...
Testing from SimpleLink LLC (104.194.215.116)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by WebNX (Los Angeles, CA) [3857.64 km]: 23.979 ms
Testing download speed................................................................................
Download: 759.51 Mbit/s
Testing upload speed................................................................................................
Upload: 674.74 Mbit/s

and with server #7456 which is our upstream/same datacenter in Los Angeles and is only 6 milliseconds away based on SpeedTest,

[[email protected] ~]# ./speedtest-cli --server 7456
Retrieving speedtest.net configuration...
Testing from SimpleLink LLC (104.194.215.116)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by QuadraNet, Inc (Los Angeles, CA) [3857.64 km]: 6.215 ms
Testing download speed................................................................................
Download: 658.41 Mbit/s
Testing upload speed................................................................................................
Upload: 511.86 Mbit/s

Now, in both these cases with speedtest, we get around 650 - 760 Mbps.

Next, Let's run a wget based CacheFly speedtest file, here, we notice 94.4 MB/s (940 Mbps!),

[[email protected] ~]# wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2018-02-06 11:22:46--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘/dev/null’

100%[=================================>] 104,857,600 94.4MB/s   in 1.1s

2018-02-06 11:22:47 (94.4 MB/s) - ‘/dev/null’ saved [104857600/104857600]

How to find servers in your VPSes location:

./speedtest-cli --list | grep "Frankfurt"

Can replace the location with "Amsterdam" etc wherever the server is located at.

It will list out the locations with associated numbers along; For eg:

./speedtest-cli --list | grep "Frankfurt"
 1746) Vodafone DE (Frankfurt, Germany) [143.90 km]
10260) Interoute VDC (Frankfurt, Germany) [143.90 km]
 3585) LeaseWeb (Frankfurt, Germany) [143.90 km]
 9273) DEAC (Frankfurt, Germany) [143.90 km]

You can pick out any number associated with the location; For eg:

./speedtest-cli --server 3585
Retrieving speedtest.net configuration...
Testing from Accelerated IT Services GmbH (82.211.1.104)...
Retrieving speedtest.net server list...
Retrieving information for the selected server...
Hosted by LeaseWeb (Frankfurt) [143.90 km]: 11.596 ms
Testing download speed................................................................................
Download: 917.56 Mbit/s
Testing upload speed................................................................................................
Upload: 727.76 Mbit/s

This should show the most accurate speed listing.

With this we can now conclude the following,

  1. Speedtest result also depends on the how "loaded" the test server (in above example, --server 5861 and --server 7456) also is.
  2. CacheFly test must be done to confirm speed as well to see if any issues exist

If you get LOW speeds with CacheFly test + SpeedTest test, please contact us right away and we will fix the issue!


Last Modified: July 25 2018 23:28:04