New on LowEndTalk? Please Register and read our Community Rules.
Traceroute and speed test please :)
hello
I put up a server in a DC here and took the cheapest offer which is good for Romania as a test and backup toy, but I would like to test international BW too. They do have many options regarding BW, including full layer 3 but that is too expensive for me.
In EU doesn't do bad, from what i tested with my vpses around, however i read in asia is 800 ms ping :P
Please put up some traceroute and speed test for this ip and file:
http://109.163.230.155/100mb.test
Thanks !
M
Comments
Speeds are fluctuating so either others are also doing tests or the link is not too stable
Leaseweb NL:
Connecting to 109.163.230.155:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [text/plain]
Saving to: â100mb.testâ
100%[==================================================================================================================================>] 104,857,600 3.25M/s in 38s
2012-08-23 08:54:16 (2.65 MB/s) - â100mb.testâ
FINISHED --2012-08-23 08:54:16--
Downloaded: 1 files, 100M in 38s (2.65 MB/s)
Poland:
[[email protected] ~]# wget http://109.163.230.155/100mb.test
--2012-08-23 10:54:27-- http://109.163.230.155/100mb.test
Connecting to 109.163.230.155:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [text/plain]
Saving to: `100mb.test'
100%[==================================================================================================================================>] 104,857,600 1.65M/s in 39s
2012-08-23 10:55:06 (2.56 MB/s) - `100mb.test' saved [104857600/104857600]
Now it's reduced
Download speed is not worth to try because currently I'm at the office with maximum 1mbps
OVH France
wget http://109.163.230.155/100mb.test
--2012-08-23 10:03:22-- http://109.163.230.155/100mb.test
Connecting to 109.163.230.155:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [text/plain]
Saving to: â100mb.testâ
100%[=======================================================================================================================================>] 104,857,600 3.34M/s in 38s
2012-08-23 10:04:00 (2.66 MB/s) - â100mb.testâ
ping 109.163.230.155
PING 109.163.230.155 (109.163.230.155) 56(84) bytes of data.
64 bytes from 109.163.230.155: icmp_seq=1 ttl=57 time=41.0 ms
64 bytes from 109.163.230.155: icmp_seq=2 ttl=57 time=41.0 ms
64 bytes from 109.163.230.155: icmp_seq=3 ttl=57 time=41.0 ms
64 bytes from 109.163.230.155: icmp_seq=4 ttl=57 time=41.2 ms
64 bytes from 109.163.230.155: icmp_seq=5 ttl=57 time=41.3 ms
^C
--- 109.163.230.155 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4847ms
rtt min/avg/max/mdev = 41.038/41.160/41.379/0.292 ms
8 hosted-by.nozhost.com (109.163.230.155) 41.025 ms 41.029 ms 41.452 ms
http://just-ping.com/index.php?vh=109.163.230.155&c=&s=ping!
Traceroute PL
1 212.7.216.1 (212.7.216.1) 0.146 ms 0.156 ms 0.141 ms
2 te4-8.212.ccr01.waw01.atlas.cogentco.com (149.6.70.69) 0.480 ms 0.491 ms 0.525 ms
3 te0-3-0-3.ccr22.ham01.atlas.cogentco.com (154.54.56.173) 13.154 ms 13.316 ms te0-1-0-3.ccr22.ham01.atlas.cogentco.com (154.54.39.161) 13.078 ms
4 te0-0-0-3.mpd22.ams03.atlas.cogentco.com (130.117.1.101) 22.187 ms te0-1-0-3.mpd22.ams03.atlas.cogentco.com (130.117.50.37) 22.292 ms te0-0-0-3.mpd22.ams03.atlas.cogentco.com (130.117.1.101) 22.386 ms
5 level3.ams03.atlas.cogentco.com (130.117.14.182) 22.265 ms 22.252 ms 22.238 ms
6 ae-51-51.csw1.Amsterdam1.Level3.net (4.69.139.153) 26.640 ms 26.719 ms 27.675 ms
7 ae-56-111.ebr1.Amsterdam1.Level3.net (4.69.153.185) 22.196 ms ae-57-112.ebr1.Amsterdam1.Level3.net (4.69.153.189) 22.174 ms ae-56-111.ebr1.Amsterdam1.Level3.net (4.69.153.185) 23.644 ms
8 ae-46-46.ebr2.Dusseldorf1.Level3.net (4.69.143.202) 25.867 ms ae-48-48.ebr2.Dusseldorf1.Level3.net (4.69.143.210) 30.490 ms ae-46-46.ebr2.Dusseldorf1.Level3.net (4.69.143.202) 30.335 ms
9 ae-23-23.ebr1.Dusseldorf1.Level3.net (4.69.143.189) 25.620 ms 34.800 ms ae-24-24.ebr1.Dusseldorf1.Level3.net (4.69.143.193) 25.786 ms
10 ae-47-47.ebr3.Frankfurt1.Level3.net (4.69.143.174) 25.796 ms ae-46-46.ebr3.Frankfurt1.Level3.net (4.69.143.170) 25.686 ms ae-45-45.ebr3.Frankfurt1.Level3.net (4.69.143.166) 25.614 ms
11 ae-83-83.csw3.Frankfurt1.Level3.net (4.69.163.10) 25.710 ms ae-63-63.csw1.Frankfurt1.Level3.net (4.69.163.2) 26.131 ms ae-73-73.csw2.Frankfurt1.Level3.net (4.69.163.6) 32.375 ms
12 ae-1-60.edge4.Frankfurt1.Level3.net (4.69.154.8) 30.206 ms ae-4-90.edge4.Frankfurt1.Level3.net (4.69.154.200) 25.657 ms 25.671 ms
13 212.162.5.154 (212.162.5.154) 26.285 ms 26.421 ms 26.110 ms
14 buc-ird-04gw.voxility.net (109.163.235.129) 57.759 ms 57.923 ms 57.662 ms
15 buc-ird-01c.voxility.net (109.163.235.62) 54.840 ms 54.936 ms 54.574 ms
16 hosted-by.nozhost.com (109.163.230.155) 57.502 ms 57.575 ms 57.446 ms
Traceroute NL
1 212.7.207.62 (212.7.207.62) 0.466 ms 0.449 ms 0.485 ms
2 be25.crs.tc2.leaseweb.net (62.212.80.77) 0.586 ms 0.586 ms 0.580 ms
3 195.69.146.43 (195.69.146.43) 8.504 ms 8.357 ms 8.385 ms
4 buc-ird-04gw.voxility.net (109.163.235.129) 42.062 ms 42.181 ms 42.434 ms
5 buc-ird-01c.voxility.net (109.163.235.62) 41.997 ms 42.191 ms 41.871 ms
6 hosted-by.nozhost.com (109.163.230.155) 41.860 ms 41.801 ms 41.752 ms
Dino
[from SUMATRA, INDONESIA]
to Prometeus:
to Romania:
but I'm on shitty ISP atm, and at the village. If another Indonesian fellow could provide test result from another ISP (fasnet, telkomsel, etc.)..
Tokyo, JP
PING 109.163.230.155 (109.163.230.155) 56(84) bytes of data.
64 bytes from 109.163.230.155: icmp_req=1 ttl=50 time=308 ms
64 bytes from 109.163.230.155: icmp_req=2 ttl=50 time=308 ms
64 bytes from 109.163.230.155: icmp_req=3 ttl=50 time=310 ms
64 bytes from 109.163.230.155: icmp_req=4 ttl=50 time=309 ms
64 bytes from 109.163.230.155: icmp_req=5 ttl=50 time=308 ms
--- 109.163.230.155 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 308.673/309.091/310.076/0.864 ms
Honk Kong
PING 109.163.230.155 (109.163.230.155) 56(84) bytes of data.
64 bytes from 109.163.230.155: icmp_req=1 ttl=51 time=328 ms
64 bytes from 109.163.230.155: icmp_req=3 ttl=51 time=328 ms
64 bytes from 109.163.230.155: icmp_req=4 ttl=51 time=329 ms
64 bytes from 109.163.230.155: icmp_req=5 ttl=51 time=332 ms
--- 109.163.230.155 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4010ms
rtt min/avg/max/mdev = 328.194/329.731/332.341/1.625 ms
Sao Paulo, BR
PING 109.163.230.155 (109.163.230.155) 56(84) bytes of data.
64 bytes from 109.163.230.155: icmp_req=1 ttl=48 time=251 ms
64 bytes from 109.163.230.155: icmp_req=2 ttl=48 time=248 ms
64 bytes from 109.163.230.155: icmp_req=3 ttl=48 time=252 ms
64 bytes from 109.163.230.155: icmp_req=4 ttl=48 time=251 ms
64 bytes from 109.163.230.155: icmp_req=5 ttl=48 time=251 ms
--- 109.163.230.155 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 248.806/251.346/252.714/1.363 ms
So it seems like it is +30ms more latency than uncle Sal's network (from Indonesia)
Speed is meh, around 2-3 MB/s from my home connection. Ping is ok, around 45ms. The biggest hop is from Frankfurt to Bucarest with 30ms (using voxility)
Looks like it
However, this is why a server is on the net, so multiple ppl can use it same time. I can see both multiple loads right now and single ones later on.
Anyway, the fact many ppl are doing it now for me is a very good feeling towards the LET ppl
Thank you !
M
Looks like it, Uncle Sal is closer to Frankfurt where most cables land in EU and connect, this is why I asked a traceroute too, so the difference in distance counts twice for ppl outside Europe, within Europe is not that bad regarding ping and hops.
M
Traceroute from Hongkong (Netvigator)
Default route for them is GBLX LAX (otherwise if it's directly connected to BTN it routes through BTN).
Cool, it travels through US, no wonder ping is 400+ :P
Ah, and that hostname is not mine, probably they recycled the IP and didnt delete it. Since I dont need to send mail from it, didnt bother to ask for one.
M
I am seeing them everyday:3
Even if it's directly connected I doubt if it would decrease dramatically compared to what I got in hitting SJC/LAX
Hmm I just realized that apparently it is common to have ~300ms latency from Asia to Europe.
So my ISP here is not that bad at all
5 vlan90.csw4.LosAngeles1.Level3.net (4.69.144.254) 9.853 ms 9.838 ms 9.823 ms
6 ae-93-93.ebr3.LosAngeles1.Level3.net (4.69.137.45) 0.319 ms 0.282 ms 0.267 ms
7 4.69.132.82 (4.69.132.82) 63.396 ms 63.427 ms 63.418 ms
8 ae-61-61.csw1.Washington1.Level3.net (4.69.134.130) 63.400 ms 63.390 ms 63.308 ms
9 ae-1-60.edge2.Washington4.Level3.net (4.69.149.16) 75.713 ms 75.606 ms 63.061 ms
10 4.53.114.138 (4.53.114.138) 158.083 ms 158.145 ms 158.228 ms
11 lon-tel-01gw.voxility.net (109.163.235.141) 155.596 ms 155.661 ms 155.716 ms
12 fra-anc-02gw.voxility.net (109.163.235.133) 155.021 ms 155.185 ms 155.259 ms
13 buc-ird-04gw.voxility.net (109.163.235.129) 186.425 ms 187.603 ms 187.731 ms
14 buc-ird-01c.voxility.net (109.163.235.62) 186.860 ms 186.624 ms 187.099 ms
15 hosted-by.nozhost.com (109.163.230.155) 187.216 ms 187.351 ms 187.320 ms
This actually goes over the USA, the hops are just hidden.
San Jose, CA
I actually thought if they are MPLS-ed but it seems that there's like a 100ms difference...
@NickM
Hum, I saw that SJ problem at uncle sal too from time to time, when I put review on wht was also very bad. Here it is:
Maybe a problem with EU linking.
M
For Traceroutes/Pings
London, UK
Tampa, FL
Let me know what ya think.
@nunim
From London:
Florida:
Traceroute from florida:
Looks like it should be.
M
From Florida:
1 208.38.174.218 (208.38.174.218) 0.577 ms 0.674 ms 0.857 ms
2 gi2-4.border4.esnet.com (216.139.207.25) 0.495 ms 0.583 ms 0.668 ms
3 vlan340.car1.Orlando1.Level3.net (4.71.2.9) 43.535 ms 43.620 ms 43.649 ms
4 ae-2-6.bar1.Orlando1.Level3.net (4.69.133.78) 28.160 ms 28.247 ms 28.137 ms
5 ae-8-8.ebr1.Atlanta2.Level3.net (4.69.137.150) 38.298 ms 38.292 ms 36.376 ms
6 ae-63-63.ebr3.Atlanta2.Level3.net (4.69.148.241) 36.261 ms 36.192 ms 36.400 ms
7 ae-2-2.ebr1.Washington1.Level3.net (4.69.132.86) 49.945 ms 58.619 ms 58.591 ms
8 ae-81-81.csw3.Washington1.Level3.net (4.69.134.138) 59.876 ms ae-61-61.csw1.Washington1.Level3.net (4.69.134.130) 52.573 ms 52.553 ms
9 ae-4-90.edge2.Washington4.Level3.net (4.69.149.208) 50.346 ms 50.000 ms 49.881 ms
10 4.53.114.138 (4.53.114.138) 144.608 ms 144.490 ms 144.681 ms
11 lon-tel-01gw.voxility.net (109.163.235.141) 146.901 ms 146.937 ms 147.026 ms
12 fra-anc-02gw.voxility.net (109.163.235.133) 143.556 ms 143.385 ms 143.472 ms
13 buc-ird-04gw.voxility.net (109.163.235.129) 177.065 ms 177.546 ms 177.384 ms
14 buc-ird-01c.voxility.net (109.163.235.62) 172.669 ms 172.908 ms 173.102 ms
15 hosted-by.nozhost.com (109.163.230.155) 178.755 ms 178.668 ms 179.008 ms
Thanks all
I was afraid there will be abismal results after Erawan reported 800 ping :P
For the money I am paying it seems more than fair, it is only 24 Eur a month, 2.5 times a connection at home and they have also to supply power and maintain environment, etc.
I see most routes going over l3, speed is not stellar but ping is not much worse than the state of the art DC in Italy.
M
800ms? I believe Erawan was downloading something at that time
Traceroute from Wellington, New Zealand.
3 122-62-xxx.jetstream.xtra.co.nz (122.62.xxx) 42.634 ms 40.527 ms 39.825 ms
4 122-62-128-1.jetstream.xtra.co.nz (122.62.xxx) 46.265 ms 39.215 ms 185.730 ms
5 mdr-fid-int.akbr5.global-gateway.net.nz (202.37.244.222) 54.749 ms 52.979 ms 52.673 ms
6 ae4-10.akbr5.global-gateway.net.nz (202.37.244.221) 51.850 ms 51.636 ms 51.697 ms
7 ae1-2.akbr4.global-gateway.net.nz (202.50.232.77) 51.788 ms 52.642 ms 50.995 ms
8 ae1-10.tkbr9.global-gateway.net.nz (202.50.232.37) 52.979 ms 50.995 ms 70.893 ms
9 xe7-0-0.labr5.global-gateway.net.nz (202.50.232.18) 264.527 ms 299.835 ms 306.519 ms
10 ae0.pabr4.global-gateway.net.nz (203.96.120.74) 301.758 ms 296.570 ms ae1-3.sjbr2.global-gateway.net.nz (203.96.120.94) 210.357 ms
11 ae0.pabr4.global-gateway.net.nz (203.96.120.74) 293.182 ms 298.859 ms 308.472 ms
12 te-7-4.car2.SanJose2.Level3.net (4.59.4.93) 304.840 ms 293.884 ms 298.340 ms
13 vlan90.csw4.SanJose1.Level3.net (4.69.152.254) 306.304 ms 299.011 ms 305.787 ms
14 ae-91-91.ebr1.SanJose1.Level3.net (4.69.153.13) 210.510 ms 299.804 ms 377.564 ms
15 ae-2-2.ebr2.NewYork1.Level3.net (4.69.135.186) 334.655 ms 298.401 ms 306.458 ms
16 ae-6-6.ebr2.NewYork2.Level3.net (4.69.141.22) 308.807 ms 312.806 ms 313.201 ms
17 ae-1-100.ebr1.NewYork2.Level3.net (4.69.135.253) 300.354 ms ae-3-3.ebr2.Washington1.Level3.net (4.69.132.89) 300.842 ms 300.659 ms
18 ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 306.457 ms ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 300.660 ms ae-62-62
.csw1.Washington1.Level3.net (4.69.134.146) 308.167 ms
19 ae-3-80.edge2.Washington4.Level3.net (4.69.149.144) 300.080 ms 301.972 ms ae-1-60.edge2.Washington4.Level3.net (4.69.149.16) 308.166 m
s
20 ae-3-80.edge2.Washington4.Level3.net (4.69.149.144) 277.679 ms 304.443 ms 302.674 ms
21 lon-tel-01gw.voxility.net (109.163.235.141) 416.474 ms 4.53.114.138 (4.53.114.138) 397.003 ms 393.219 ms
22 lon-tel-01gw.voxility.net (109.163.235.141) 515.046 ms 398.376 ms 417.572 ms
23 fra-anc-02gw.voxility.net (109.163.235.133) 404.480 ms 416.107 ms 403.137 ms
24 buc-ird-04gw.voxility.net (109.163.235.129) 406.128 ms 612.824 ms 407.380 ms
25 * buc-ird-01c.voxility.net (109.163.235.62) 424.469 ms 609.467 ms
26 hosted-by.nozhost.com (109.163.230.155) 516.540 ms 612.702 ms 404.511 ms
Incero Dallas
2 23.29.112.73 (23.29.112.73) 3.497 ms 3.540 ms 3.533 ms
3 incero.corexchange.com (209.105.225.45) 50.847 ms 50.862 ms 50.852 ms
4 tengigabitethernet2-2.asr1.dal2.gblx.net (208.48.236.129) 0.865 ms 0.902 ms 0.941 ms
5 xe2-2-0-10G.csr1.DAL2.gblx.net (67.17.79.109) 0.718 ms 0.723 ms 0.717 ms
6 lag13-70G.ar6.DAL2.gblx.net (67.16.150.189) 10.032 ms 4.077 ms 0.747 ms
7 4.68.63.145 (4.68.63.145) 0.783 ms 0.723 ms 0.748 ms
8 vlan70.csw2.Dallas1.Level3.net (4.69.145.126) 6.419 ms 5.768 ms vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 2.231
ms
9 ae-63-63.ebr3.Dallas1.Level3.net (4.69.151.134) 1.133 ms 1.108 ms ae-93-93.ebr3.Dallas1.Level3.net (4.69.151.170) 1
.378 ms
10 ae-7-7.ebr3.Atlanta2.Level3.net (4.69.134.22) 21.032 ms 20.591 ms 20.833 ms
11 ae-2-2.ebr1.Washington1.Level3.net (4.69.132.86) 36.226 ms 34.492 ms 34.312 ms
12 ae-71-71.csw2.Washington1.Level3.net (4.69.134.134) 34.178 ms ae-81-81.csw3.Washington1.Level3.net (4.69.134.138) 40
.946 ms ae-71-71.csw2.Washington1.Level3.net (4.69.134.134) 34.177 ms
13 ae-1-60.edge2.Washington4.Level3.net (4.69.149.16) 34.511 ms 34.939 ms ae-2-70.edge2.Washington4.Level3.net (4.69.14
9.80) 34.754 ms
14 4.53.114.138 (4.53.114.138) 125.907 ms 125.611 ms 125.989 ms
15 lon-tel-01gw.voxility.net (109.163.235.141) 126.347 ms 133.279 ms 134.140 ms
16 fra-anc-02gw.voxility.net (109.163.235.133) 128.886 ms 128.033 ms 128.355 ms
17 buc-ird-04gw.voxility.net (109.163.235.129) 157.450 ms 157.440 ms 157.048 ms
18 buc-ird-01c.voxility.net (109.163.235.62) 168.267 ms 168.196 ms 162.486 ms
19 hosted-by.nozhost.com (109.163.230.155) 159.291 ms 159.380 ms 159.737 ms
Germany, near Karlsruhe
Download speed is so-so.
I could do 1400Kbit/s with my ISP connection.
I get 431Kbit/s (100Mb took 3:52 minutes or 232 seconds)
But Ping is really awesome, 83ms
`ping 109.163.230.155
Ping wird ausgeführt für 109.163.230.155 mit 32 Bytes Daten:
Antwort von 109.163.230.155: Bytes=32 Zeit=83ms TTL=53
Antwort von 109.163.230.155: Bytes=32 Zeit=83ms TTL=53
Antwort von 109.163.230.155: Bytes=32 Zeit=84ms TTL=53
Antwort von 109.163.230.155: Bytes=32 Zeit=84ms TTL=53
Ping-Statistik für 109.163.230.155:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 83ms, Maximum = 84ms, Mittelwert = 83ms
`
Treaceroute can't proceed till the end, from hop 10 it time-outs
`Routenverfolgung zu hosted-by.nozhost.com [109.163.230.155] über maximal 30 Abschnitte:
1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 37 ms 36 ms 37 ms rdsl-krlh-de02.nw.mediaways.net [213.20.56.137]
3 37 ms 36 ms 37 ms xmws-krlh-de01-chan-17.nw.mediaways.net [213.20.220.210]
4 36 ms 36 ms 37 ms rmws-krlh-de01-gigaet-0-0-0.nw.mediaways.net [62.53.222.46]
5 42 ms 42 ms 42 ms rmwc-stgt-de01-pos-0-0.nw.mediaways.net [213.20.222.157]
6 44 ms 43 ms 42 ms rmwc-stgt-de02-pos-9-0.nw.mediaways.net [213.20.222.162]
7 42 ms 41 ms 42 ms rmwc-frnk-de01-xe-7-1-3-0.nw.mediaways.net [195.71.212.165]
8 42 ms 41 ms 41 ms xmws-frnk-de07-chan-0.nw.mediaways.net [213.20.249.202]
9 47 ms 47 ms 46 ms fra-anc-01gw.voxility.net [80.81.194.144]
10 * * * Zeitüberschreitung der Anforderung.
11 * * * Zeitüberschreitung der Anforderung.
........
29 * * * Zeitüberschreitung der Anforderung.
30 * * * Zeitüberschreitung der Anforderung.
Ablaufverfolgung beendet.`
Thanks all, I think I have a general picture.
Like most is 400 or so from south asia/nz over US and lowest from UK/DE and similar.
Speed seems to be low, tho, but cant expect much more at these money
M
Melbourne AU, Speeds suck at most 150kB/s