Ping results from tokyo1.linode.com
I'm checking this from Sydney, I was wondering if there was anyone else from Oz that can post their results of tokyo1.
I know that the southern cross cable terminates practically on HE's front doorstep, but i'm thinking that the routes to toyko won't make it a viable option for hosting on the eastern seaboard of Oz.
9 Replies
fremont 210ms
from iinet sydney
traceroute to tokyo1.linode.com (106.187.33.12), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 2.743 ms 2.919 ms 3.141 ms
2 nexthop.nsw.iinet.net.au (203.55.231.88) 25.148 ms 29.653 ms 32.825 ms
3 te7-1.syd-ult-bdr1.iinet.net.au (203.215.16.27) 37.523 ms 40.864 ms 45.235 ms
4 xe-1-1-0-0.syd-ult-core1.iinet.net.au (203.215.20.30) 48.737 ms 53.293 ms 56.139 ms
5 Bundle-Ether12.chw48.Sydney.telstra.net (139.130.0.137) 64.592 ms 67.645 ms 71.337 ms
6 Bundle-Ether6.chw-core2.Sydney.telstra.net (203.50.6.153) 84.678 ms 31.413 ms 30.634 ms
7 Bundle-Ether1.oxf-gw2.Sydney.telstra.net (203.50.6.90) 24.085 ms 25.990 ms 30.311 ms
8 203.50.13.134 (203.50.13.134) 33.057 ms 37.379 ms 41.260 ms
9 i-4-0-0.siko-core02.bx.reach.com (202.84.140.138) 164.064 ms 168.079 ms 171.660 ms
10 i-1-1-0.siko01.bi.reach.com (202.84.148.138) 176.448 ms 179.236 ms 183.915 ms
11 118.155.194.149 (118.155.194.149) 189.309 ms 192.149 ms 196.543 ms
12 otejbb203.kddnet.ad.jp (118.155.197.129) 200.279 ms otejbb203.kddnet.ad.jp (118.155.197.1) 143.319 ms otejbb204.kddnet.ad.jp (118.155.197.2) 143.265 ms
13 cm-fcu203.kddnet.ad.jp (124.215.194.164) 145.565 ms cm-fcu203.kddnet.ad.jp (124.215.194.180) 148.137 ms cm-fcu203.kddnet.ad.jp (124.215.194.164) 163.329 ms
14 124.215.199.122 (124.215.199.122) 156.955 ms 143.777 ms 143.470 ms
15 tokyo1.linode.com (106.187.33.12) 144.799 ms 148.531 ms 151.153 ms
Tokyo
traceroute to tokyo1.linode.com (106.187.33.12), 30 hops max, 60 byte packets
1 115.31.88.230 (115.31.88.230) 1.025 ms 1.120 ms 1.363 ms
2 10.1.1.1 (10.1.1.1) 0.927 ms 0.905 ms 0.885 ms
3 ge-0-0-0.169.bdr01.mel01.vic.VOCUS.net.au (114.31.197.105) 1.204 ms 1.183 ms 1.155 ms
4 ge-0-0-2.bdr02.mel04.vic.VOCUS.net.au (114.31.196.33) 169.973 ms 169.962 ms 169.943 ms
5 ge-0-0-3.bdr01.mel04.vic.VOCUS.net.au (114.31.196.34) 169.879 ms 169.880 ms 169.834 ms
6 ge-1-0-6.cor01.syd03.nsw.VOCUS.net.au (114.31.192.82) 169.046 ms 169.282 ms 169.260 ms
7 ten-1-3-0.cor02.syd03.nsw.VOCUS.net.au (114.31.192.87) 14.193 ms 14.180 ms 14.319 ms
8 pos-1-2-2.bdr02.sjc01.ca.VOCUS.net.au (114.31.199.46) 169.445 ms 169.428 ms 169.410 ms
9 10gigabitethernet3-2.core1.sjc1.he.net (64.71.184.45) 169.306 ms 169.849 ms 169.831 ms
10 10gigabitethernet2-3.core1.pao1.he.net (72.52.92.114) 170.328 ms 170.267 ms 170.198 ms
11 124.215.192.93 (124.215.192.93) 170.142 ms 124.215.192.81 (124.215.192.81) 181.087 ms 124.215.192.97 (124.215.192.97) 170.586 ms
12 pajbb002.kddnet.ad.jp (124.211.34.73) 169.453 ms pajbb001.kddnet.ad.jp (124.211.34.53) 170.045 ms pajbb001.kddnet.ad.jp (124.211.34.85) 169.994 ms
13 otejbb203.kddnet.ad.jp (203.181.100.5) 294.232 ms otejbb203.kddnet.ad.jp (203.181.100.209) 283.760 ms otejbb204.kddnet.ad.jp (203.181.100.201) 284.729 ms
14 cm-fcu203.kddnet.ad.jp (124.215.194.180) 288.256 ms cm-fcu203.kddnet.ad.jp (124.215.194.164) 288.240 ms cm-fcu203.kddnet.ad.jp (124.215.194.180) 292.974 ms
15 124.215.199.122 (124.215.199.122) 279.356 ms 285.749 ms 277.127 ms
16 tokyo1.linode.com (106.187.33.12) 275.822 ms 275.324 ms 285.960 ms
Fremont
traceroute to fremont1.linode.com (64.71.152.17), 30 hops max, 60 byte packets
1 115.31.88.230 (115.31.88.230) 7.375 ms 8.166 ms 8.330 ms
2 10.1.1.1 (10.1.1.1) 7.377 ms 7.346 ms 7.399 ms
3 ge-0-0-0.169.bdr01.mel01.vic.VOCUS.net.au (114.31.197.105) 9.629 ms 9.619 ms 9.591 ms
4 ge-0-0-2.bdr02.mel04.vic.VOCUS.net.au (114.31.196.33) 176.355 ms 176.351 ms 176.337 ms
5 ge-0-0-3.bdr01.mel04.vic.VOCUS.net.au (114.31.196.34) 176.274 ms 176.276 ms 176.226 ms
6 ge-1-0-6.cor01.syd03.nsw.VOCUS.net.au (114.31.192.82) 175.499 ms 169.604 ms 169.538 ms
7 ten-1-3-0.cor02.syd03.nsw.VOCUS.net.au (114.31.192.87) 169.636 ms 169.616 ms 169.594 ms
8 pos-1-2-2.bdr02.sjc01.ca.VOCUS.net.au (114.31.199.46) 169.337 ms 168.946 ms 168.927 ms
9 pos-1-2-0.bdr01.sjc02.ca.VOCUS.net.au (114.31.199.118) 169.540 ms 169.528 ms 169.434 ms
10 10gigabitethernet2-3.core1.sjc2.he.net (206.223.116.37) 170.080 ms 170.761 ms 170.721 ms
11 10gigabitethernet1-1.core1.fmt1.he.net (72.52.92.109) 171.462 ms 171.437 ms 170.672 ms
12 linode-llc.10gigabitethernet2-3.core1.fmt1.he.net (64.62.250.6) 171.967 ms 170.534 ms 171.060 ms
13 fremont1.linode.com (64.71.152.17) 170.453 ms 170.432 ms 171.238 ms
@TheClient:
Does anyone has data for Singapore: Fremont vs Tokyo?
http://traceroute.org/#Singapore
traceroute to tokyo1.linode.com (106.187.33.12), 30 hops max, 40 byte packets
1 202-150-221-169.rev.ne.com.sg (202.150.221.169) 0.584 ms 0.638 ms 0.706 ms
2 s4-6-r10.cyberway.com.sg (203.117.6.209) 0.633 ms 0.679 ms 0.721 ms
3 anutsi10.starhub.net.sg (203.118.3.226) 2.454 ms 2.448 ms 2.436 ms
4 203.181.102.193 (203.181.102.193) 79.365 ms 79.375 ms 79.364 ms
5 otejbb203.kddnet.ad.jp (59.128.7.129) 79.762 ms 80.029 ms 80.075 ms
6 cm-fcu203.kddnet.ad.jp (124.215.194.164) 84.072 ms 83.321 ms 83.398 ms
7 124.215.199.122 (124.215.199.122) 81.217 ms 81.407 ms 81.234 ms
8 tokyo1.linode.com (106.187.33.12) 80.958 ms 80.869 ms 80.854 ms
traceroute to fremont1.linode.com (64.71.152.17), 30 hops max, 40 byte packets
1 202-150-221-169.rev.ne.com.sg (202.150.221.169) 0.337 ms 0.381 ms 0.429 ms
2 s4-6-r10.cyberway.com.sg (203.117.6.209) 0.678 ms 0.719 ms 0.745 ms
3 anutsi10.starhub.net.sg (203.118.3.226) 2.382 ms 2.371 ms 2.359 ms
4 paix.he.net (198.32.176.20) 180.718 ms 180.727 ms 180.715 ms
5 10gigabitethernet1-2.core1.fmt1.he.net (66.160.158.241) 190.110 ms 195.417 ms 190.356 ms
6 linode-llc.10gigabitethernet2-3.core1.fmt1.he.net (64.62.250.6) 181.292 ms 181.263 ms 181.320 ms
7 fremont1.linode.com (64.71.152.17) 186.094 ms 186.090 ms 186.079 ms
@TheClient:
Thanks, it shows that Tokyo will be faster for Singapore.
Sure, for that one Singapore ISP.
****Reply from [hidden]: bytes=32 time=177ms TTL=56
Reply from [hidden]: bytes=32 time=176ms TTL=56
Reply from [hidden]: bytes=32 time=173ms TTL=56****
Very good, I see around +50% performance increase compare to Fremont DC which I used before.
Also my home internet connection is quite slow, so I believe those guys with broadband will have better results.
Plus it's not Fremont !!