Can you please let me know your download speed from these test files?

nrep

Well-known member
I'm having some problems troubleshooting a speed problem with my hosting company, and I'd be grateful if I could get a selection of download speed test results (and MTR / tracert results) from the following site. It would also be useful to let me know if that is saturating your connection, so I don't mistake low speeds.

http://speedtest.hivelocity.net

I'm only getting ~800kb/s, which is really slow for my connection, so I think the problem may be with their network rather than my server. If I could get other users to verify this, it will give me something to show them.

Thank you :).
 
Last edited:
Thanks Rob - is your connection normally faster than that? I forgot to ask in my OP, so I've edited it now.
 
Hivelocity 2.55MB/s
Code:
[root@server ~]# wget http://speedtest.hivelocity.net/100mb.file
--2017-12-03 12:15:59--  http://speedtest.hivelocity.net/100mb.file
Resolving speedtest.hivelocity.net (speedtest.hivelocity.net)... 2604:4500:0:286::44e9:e022, 68.233.224.34
Connecting to speedtest.hivelocity.net (speedtest.hivelocity.net)|2604:4500:0:286::44e9:e022|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M)
Saving to: ‘100mb.file’

100%[===============================================================================================================================================>] 104,857,600 2.55MB/s   in 40s

2017-12-03 12:16:38 (2.53 MB/s) - ‘100mb.file’ saved [104857600/104857600]

Linode East 70.9MB/s

Code:
[root@server ~]# wget http://speedtest.newark.linode.com/100MB-newark.bin
--2017-12-03 12:17:18--  http://speedtest.newark.linode.com/100MB-newark.bin
Resolving speedtest.newark.linode.com (speedtest.newark.linode.com)... 2600:3c03::4b, 50.116.57.237
Connecting to speedtest.newark.linode.com (speedtest.newark.linode.com)|2600:3c03::4b|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘100MB-newark.bin’

100%[===============================================================================================================================================>] 104,857,600 70.9MB/s   in 1.4s

2017-12-03 12:17:19 (70.9 MB/s) - ‘100MB-newark.bin’ saved [104857600/104857600]

Linode London 16.0MB/s

Code:
[root@server ~]# wget http://speedtest.london.linode.com/100MB-london.bin
--2017-12-03 12:17:59--  http://speedtest.london.linode.com/100MB-london.bin
Resolving speedtest.london.linode.com (speedtest.london.linode.com)... 2a01:7e00::4b, 176.58.107.39
Connecting to speedtest.london.linode.com (speedtest.london.linode.com)|2a01:7e00::4b|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘100MB-london.bin’

100%[===============================================================================================================================================>] 104,857,600 16.0MB/s   in 6.8s

2017-12-03 12:18:06 (14.8 MB/s) - ‘100MB-london.bin’ saved [104857600/104857600]

Hivelocity is really slow. Tested from ReliableSite dedicated server in NY.
 
Thanks, yup - Hivelocity does seem really slow from what I can tell. @Jake B. seems to get much better speeds from his HV server, so I wonder if it's just from my particular datacentre.
 
From my RamNode VPS (Atlanta, Georgia based)
Code:
[13:52][root@whiskey work]# wget http://speedtest.hivelocity.net/100mb.file
--2017-12-03 13:52:58--  http://speedtest.hivelocity.net/100mb.file
Resolving speedtest.hivelocity.net... 2604:4500:0:286::44e9:e022, 68.233.224.34
Connecting to speedtest.hivelocity.net|2604:4500:0:286::44e9:e022|:80... failed: No route to host.
Connecting to speedtest.hivelocity.net|68.233.224.34|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M)
Saving to: ‘100mb.file’

100mb.file                                100%[====================================================================================>] 100.00M  2.51MB/s    in 32s
Code:
[13:55][root@whiskey work]# traceroute speedtest.hivelocity.net
traceroute to speedtest.hivelocity.net (68.233.224.34), 30 hops max, 60 byte packets
1  23.226.232.1 (23.226.232.1)  0.466 ms  0.515 ms  0.614 ms
2  xe-0-0-25-1.a01.atlnga05.us.bb.gin.ntt.net (129.250.203.221)  0.782 ms  0.778 ms  0.771 ms
3  ae-11.r03.atlnga05.us.bb.gin.ntt.net (129.250.5.57)  1.181 ms ae-1.r04.atlnga05.us.bb.gin.ntt.net (129.250.5.59)  0.454 ms ae-11.r03.atlnga05.us.bb.gin.ntt.net (129.250.5.57)  0.444 ms
4  ae-3.r21.atlnga05.us.bb.gin.ntt.net (129.250.5.211)  0.581 ms  0.567 ms  0.636 ms
5  ae-6.r23.dllstx09.us.bb.gin.ntt.net (129.250.4.116)  23.796 ms  23.428 ms  23.789 ms
6  ae-3.r22.dllstx09.us.bb.gin.ntt.net (129.250.5.20)  25.173 ms  24.285 ms  22.896 ms
7  ae-5.r22.lsanca07.us.bb.gin.ntt.net (129.250.7.69)  60.644 ms  52.803 ms  60.640 ms
8  ae-1.r01.lsanca07.us.bb.gin.ntt.net (129.250.3.123)  59.094 ms ae-1.r00.lsanca07.us.bb.gin.ntt.net (129.250.3.17)  59.118 ms  60.160 ms
9  ae-1.a00.lsanca07.us.bb.gin.ntt.net (129.250.2.116)  59.130 ms ae-0.a00.lsanca07.us.bb.gin.ntt.net (129.250.2.104)  72.026 ms  71.190 ms
10  xe-0-0-24-0.a00.lsanca07.us.ce.gin.ntt.net (129.250.201.114)  56.758 ms  60.194 ms  52.997 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Just to compare
Linode Newark
Code:
[root@whiskey work]# wget http://speedtest.newark.linode.com/100MB-newark.bin
--2017-12-03 14:00:57--  http://speedtest.newark.linode.com/100MB-newark.bin
Resolving speedtest.newark.linode.com... 2600:3c03::4b, 50.116.57.237
Connecting to speedtest.newark.linode.com|2600:3c03::4b|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘100MB-newark.bin’

100MB-newark.bin                          100%[====================================================================================>] 100.00M  7.18MB/s    in 20s    

2017-12-03 14:01:17 (5.00 MB/s) - ‘100MB-newark.bin’ saved [104857600/104857600]


Linode London
Code:
[root@whiskey work]# wget http://speedtest.london.linode.com/100MB-london.bin
--2017-12-03 14:03:11--  http://speedtest.london.linode.com/100MB-london.bin
Resolving speedtest.london.linode.com... 2a01:7e00::4b, 176.58.107.39
Connecting to speedtest.london.linode.com|2a01:7e00::4b|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘100MB-london.bin’

100MB-london.bin                          100%[====================================================================================>] 100.00M  1.99MB/s    in 58s    

2017-12-03 14:04:10 (1.72 MB/s) - ‘100MB-london.bin’ saved [104857600/104857600]
 
Last edited:
I think this issue has now been fixed - TCP auto-tuning was disabled on the server for some reason. Now enabled and running and full speed (for my server at least) :).
 
From Estonia, 500mbit connection:
Code:
$ wget http://speedtest.hivelocity.net/100mb.file
--2017-12-06 23:01:46--  http://speedtest.hivelocity.net/100mb.file
Resolving speedtest.hivelocity.net... 68.233.224.34, 2604:4500:0:286::44e9:e022
Connecting to speedtest.hivelocity.net|68.233.224.34|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M)
Saving to: '100mb.file'

100mb.file                       100%[=======================================================>] 100.00M  4.78MB/s    in 23s     

2017-12-06 23:02:09 (4.43 MB/s) - '100mb.file' saved [104857600/104857600]
Its rather slow.

Traceroute:
Code:
traceroute speedtest.hivelocity.net
traceroute to speedtest.hivelocity.net (68.233.224.34), 64 hops max, 52 byte packets
 1  192.168.0.1 (192.168.0.1)  1.661 ms  1.277 ms  1.050 ms
 2  10.65.0.1 (10.65.0.1)  9.091 ms  10.179 ms  8.512 ms
 3  akad-bb1-bu43.starman.ee (85.253.5.146)  7.901 ms  4.954 ms  8.530 ms
 4  ae5.rt.eln.tll.ee.retn.net (87.245.242.76)  8.836 ms  5.408 ms  7.782 ms
 5  ae1-5.rt.irx.fkt.de.retn.net (87.245.232.245)  39.681 ms  42.230 ms  41.076 ms
 6  213.198.77.213 (213.198.77.213)  43.650 ms  42.249 ms  45.242 ms
 7  ae-7.r20.frnkge04.de.bb.gin.ntt.net (129.250.7.54)  42.836 ms  44.087 ms  41.951 ms
 8  ae-8.r22.asbnva02.us.bb.gin.ntt.net (129.250.4.96)  128.706 ms  128.145 ms  134.522 ms
 9  ae-5.r23.lsanca07.us.bb.gin.ntt.net (129.250.3.189)  186.011 ms  196.708 ms  193.860 ms
10  ae-2.r01.lsanca07.us.bb.gin.ntt.net (129.250.4.107)  196.052 ms
    ae-2.r00.lsanca07.us.bb.gin.ntt.net (129.250.3.238)  202.537 ms  192.645 ms
11  ae-0.a00.lsanca07.us.bb.gin.ntt.net (129.250.2.104)  203.459 ms
    ae-1.a00.lsanca07.us.bb.gin.ntt.net (129.250.2.116)  195.685 ms  225.503 ms
12  xe-0-0-24-0.a00.lsanca07.us.ce.gin.ntt.net (129.250.201.114)  209.843 ms  188.853 ms  192.026 ms
13  * * *
14  * * *
15  * * *
^C
Didn't wait for it to end.
 
Tested from different servers:

Frankfurt: same as traceroute above, stuck on same node. Latency is similar too.
Sydney: same as above
Tokyo: same as above
 
Top Bottom