Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Traceroute Help/Feedback
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Traceroute Help/Feedback

KenshinKenshin Member
edited April 2012 in General

I'm still in the process of getting everything ready for our VPS launch, but meanwhile would appreciate some community help with some traceroutes and feedback if the routing is sub-optimal. Servers are located in Singapore, but I have 2 IPs that are routed slightly differently. Thanks all in advance.

116.251.209.66
116.251.210.1
2405:4200:202::1 (Yes, we'll be offering IPv6)

If anyone is interested in the outgoing traceroute from these servers, PM me with an IP and I'll assist.

Comments

  • gsrdgrdghdgsrdgrdghd Member
    edited April 2012
    
    traceroute to 116.251.209.66 (116.251.209.66), 30 hops max, 60 byte packets
    [ISPS SNAP]
     9  nl-ams05a-rd2-ae-2.aorta.net (84.116.131.141)  23.069 ms  23.059 ms  22.991 ms
    10  uk-lon01b-rd1-xe-1-3-0.aorta.net (84.116.133.77)  30.494 ms 84.116.133.18 (84.116.133.18)  31.258 ms  34.687 ms
    11  uk-lon02a-rd1-Te-15-0-0.aorta.net (84.116.130.38)  34.592 ms 84.116.132.6 (84.116.132.6)  33.395 ms uk-lon02a-rd2-xe-1-1-0.aorta.net (84.116.130.34)  34.427 ms
    12  84.116.136.186 (84.116.136.186)  34.125 ms 84.116.132.246 (84.116.132.246)  30.673 ms 84.116.136.186 (84.116.136.186)  31.492 ms
    13  195.66.236.167 (195.66.236.167)  31.966 ms  32.176 ms  32.503 ms
    14  63.216.152.186 (63.216.152.186)  242.203 ms  242.970 ms  242.900 ms
    15  edge-1.v75.globalswitch.sg.gs (203.175.175.161)  227.793 ms  217.165 ms  217.066 ms
    16  ifair.ntu.edu.sg (116.251.209.66)  237.139 ms  232.754 ms  236.890 ms
    
    traceroute to 116.251.210.1 (116.251.210.1), 30 hops max, 60 byte packets
    [ISP SNAP]
     9  uk-lon01b-rd1-ae-1.aorta.net (84.116.131.145)  33.041 ms  33.037 ms  32.925 ms
    10  84.116.132.2 (84.116.132.2)  33.503 ms 84.116.132.6 (84.116.132.6)  34.516 ms 84.116.132.2 (84.116.132.2)  34.368 ms
    11  84.116.136.186 (84.116.136.186)  36.486 ms  31.868 ms 84.116.132.246 (84.116.132.246)  31.780 ms
    12  195.66.237.10 (195.66.237.10)  31.932 ms  31.861 ms  31.841 ms
    13  203.208.152.242 (203.208.152.242)  31.712 ms 203.208.152.246 (203.208.152.246)  31.683 ms ge-2-3-0-0.lonlx-cr2.ix.singtel.com (203.208.151.210)  31.728 ms
    14  203.208.152.249 (203.208.152.249)  32.017 ms 203.208.173.177 (203.208.173.177)  32.250 ms 203.208.171.181 (203.208.171.181)  32.157 ms
    15  so-3-2-0-0.sngc3-ar4.ix.singtel.com (203.208.153.17)  222.549 ms  220.938 ms 203.208.153.49 (203.208.153.49)  217.777 ms
    16  203.208.166.173 (203.208.166.173)  220.811 ms  222.928 ms  217.141 ms
    17  203.208.166.58 (203.208.166.58)  241.631 ms 203.208.166.162 (203.208.166.162)  223.449 ms 203.208.166.58 (203.208.166.58)  241.553 ms
    18  203.208.191.102 (203.208.191.102)  224.611 ms 203.208.174.182 (203.208.174.182)  224.544 ms  224.465 ms
    19  Ge-2-0-0.sn-sintp1-bo303.singnet.com.sg (165.21.12.106)  222.271 ms  224.528 ms  217.884 ms
    20  165.21.255.74 (165.21.255.74)  219.986 ms  217.845 ms  217.764 ms
    21  115.42.248.33 (115.42.248.33)  220.558 ms  229.423 ms  227.022 ms
    22  115.42.248.34 (115.42.248.34)  243.977 ms  238.529 ms  232.794 ms
    23  edge-1.v51.com3.sg.gs (203.175.175.25)  239.523 ms  234.340 ms  238.831 ms
    24  edge-1.v71.globalswitch.sg.gs (203.175.175.132)  241.965 ms  233.792 ms  233.751 ms
    25  116.251.210.240 (116.251.210.240)  229.157 ms  225.674 ms  231.130 ms
    26  dns1.oneasiahost.com (116.251.210.1)  228.734 ms  238.682 ms  236.650 ms
    

    Using a he.net tunnel for ipv6

    
    traceroute to 2405:4200:202::1 (2405:4200:202::1), 30 hops max, 80 byte packets
     1  * * *
     2  gige-g2-4.core1.fra1.he.net (2001:470:0:69::1)  15.904 ms  15.869 ms  18.963 ms
     3  10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1)  31.579 ms  31.535 ms  32.934 ms
     4  10gigabitethernet7-4.core1.nyc4.he.net (2001:470:0:128::1)  97.850 ms  111.908 ms  100.730 ms
     5  10gigabitethernet5-3.core1.lax1.he.net (2001:470:0:10e::1)  162.299 ms  171.106 ms  166.533 ms
     6  gige-g3-18.core1.hkg1.he.net (2001:470:0:16b::2)  321.213 ms  316.147 ms  316.755 ms
     7  hostsg-RFE.hkix.net (2001:7fa:0:1::ca28:a0d4)  356.555 ms  350.891 ms  351.387 ms
     8  edge-1.v75.globalswitch.sg.gs (2405:4200:0:ff05::1)  354.479 ms edge-2.v75.globalswitch.sg.gs (2405:4200:0:ff05::2)  354.558 ms  373.468 ms
     9  2405:4200:202::240 (2405:4200:202::240)  1843.800 ms * *
    10  2405:4200:202::1 (2405:4200:202::1)  1088.138 ms * *

    Looks like the ping is almost identical (for ipv6) but the first IP has far fewer hops.

  • DanielMDanielM Member
    edited April 2012

    <

    pre>
    --116.251.209.66-- (Test From USA DC)

    1 1 ms <1 ms <1 ms gateway.dallas.us.serversupportgroup.com [207.21
    0.239.97]
    2 1 ms 1 ms <1 ms host.colocrossing.com [96.8.115.253]
    3 <1 ms <1 ms <1 ms 65.99.208.121
    4 <1 ms <1 ms <1 ms 206.123.64.25
    5 <1 ms <1 ms <1 ms 206.123.64.42
    6 <1 ms <1 ms <1 ms xe-4-2-0.er2.dfw2.us.above.net [64.124.196.225]

    7 1 ms <1 ms <1 ms xe-3-0-0.cr2.dfw2.us.above.net [64.125.30.94]
    8 54 ms 33 ms 28 ms xe-2-0-0.cr2.ord2.us.above.net [64.125.25.137]
    9 28 ms 28 ms 28 ms xe-1-1-0.er2.ord7.us.above.net [64.125.26.254]
    10 28 ms 28 ms 28 ms ge2-8.br02.chc01.pccwbtn.net [63.218.5.41]
    11 328 ms 263 ms 257 ms 63.216.152.186
    12 250 ms 250 ms 251 ms edge-1.v75.globalswitch.sg.gs [203.175.175.161]

    13 264 ms 263 ms 247 ms 116.251.209.66

    <

    pre>
    --116.251.210.1-- (Test From UK DC)

    1 1 ms 1 ms <1 ms 95.172.5.81
    2 1 ms 1 ms 1 ms g1-7-tcl2-ar2.router.uk.clara.net [195.8.78.133]

    3 2 ms 1 ms 1 ms gi1-1-3-t40-cr2.router.uk.clara.net [195.8.90.73
    ]
    4 1 ms 2 ms 1 ms ten2-0-0-t40-br3.router.uk.clara.net [195.8.86.1
    42]
    5 2 ms 2 ms 3 ms 195.66.225.10
    6 2 ms 1 ms 2 ms 203.208.152.238
    7 246 ms 188 ms 187 ms 203.208.166.46
    8 190 ms 187 ms 191 ms 203.208.166.162
    9 190 ms 191 ms 188 ms 203.208.191.102
    10 191 ms 192 ms 190 ms Ge-2-0-0.sn-sintp1-bo303.singnet.com.sg [165.21.
    12.106]
    11 191 ms 204 ms 192 ms 165.21.255.74
    12 197 ms 197 ms 197 ms 115.42.248.33
    13 191 ms 192 ms 191 ms 115.42.248.34
    14 193 ms 188 ms 188 ms edge-2.v51.com3.sg.gs [203.175.175.26]
    15 192 ms 190 ms 190 ms edge-1.v71.globalswitch.sg.gs [203.175.175.132]

    16 * 193 ms 192 ms 116.251.210.240
    17 * 193 ms 192 ms dns1.oneasiahost.com [116.251.210.1]

    <

    pre>
    --Ipv6 Test-- (Test From UK DC)

    1 2 ms <1 ms <1 ms 2a01:7b8:2011:bb3b::1
    2 3 ms 2 ms 2 ms g1-7.tcl2-ar2.ipv6.router.uk.clara.net [2001:a88
    :0:2::61]
    3 1 ms * 1 ms g1-1-7-t40-cr2.ipv6.router.uk.clara.net [2001:a8
    8:0:1::de]
    4 1 ms * 2 ms ten2-0-0.t40-br3.ipv6.router.uk.clara.net [2001:
    a88:0:1::11e]
    5 1 ms 1 ms 1 ms 10gigabitethernet1-1.core1.lon1.he.net [2001:7f8
    :4::1b1b:1]
    6 74 ms 74 ms 86 ms 10gigabitethernet7-4.core1.nyc4.he.net [2001:470
    :0:128::1]
    7 139 ms 136 ms 137 ms 10gigabitethernet5-3.core1.lax1.he.net [2001:470
    :0:10e::1]
    8 302 ms 299 ms 295 ms gige-g3-18.core1.hkg1.he.net [2001:470:0:16b::2]

    9 330 ms 329 ms 332 ms hostsg-RFE.hkix.net [2001:7fa:0:1::ca28:a0d4]
    10 336 ms 329 ms 330 ms edge-1.v75.globalswitch.sg.gs [2405:4200:0:ff05:
    :1]
    11 * 330 ms 331 ms 2405:4200:202::240
    12 332 ms 330 ms 331 ms 2405:4200:202::1

  • @DanielM Why do your trace routes look weird? Their meant to look like this

    traceroute to 116.251.209.66 (116.251.209.66), 64 hops max, 52 byte packets
     1  my.router (192.168.1.1)  3.529 ms  0.682 ms  0.614 ms
     2  217.47.93.250 (217.47.93.250)  32.029 ms  31.349 ms  32.675 ms
     3  217.47.93.161 (217.47.93.161)  30.381 ms  30.356 ms  29.787 ms
     4  213.1.69.86 (213.1.69.86)  31.267 ms  30.917 ms  31.212 ms
     5  217.41.168.102 (217.41.168.102)  30.233 ms  30.650 ms  31.098 ms
     6  217.41.168.177 (217.41.168.177)  30.411 ms  31.019 ms  30.709 ms
     7  217.41.168.107 (217.41.168.107)  30.791 ms  31.221 ms  30.770 ms
     8  acc1-10gige-0-0-0-4.l-far.21cn-ipp.bt.net (109.159.249.66)  30.442 ms
        109.159.249.112 (109.159.249.112)  30.409 ms
        109.159.249.64 (109.159.249.64)  30.257 ms
     9  core1-te0-0-0-13.ealing.ukcore.bt.net (109.159.249.33)  34.927 ms
        core2-te-0-0-0-2.ilford.ukcore.bt.net (109.159.249.31)  36.877 ms
        core2-te-0-0-0-0.ilford.ukcore.bt.net (109.159.249.29)  40.425 ms
    10  peer2-xe-1-0-0.redbus.ukcore.bt.net (109.159.254.90)  66.139 ms  32.367 ms
        peer2-xe0-1-0.redbus.ukcore.bt.net (109.159.254.70)  61.578 ms
    11  194.74.65.6 (194.74.65.6)  42.930 ms  566.634 ms  155.783 ms
    12  63.216.152.186 (63.216.152.186)  458.500 ms  596.818 ms  230.490 ms
    13  edge-1.v75.globalswitch.sg.gs (203.175.175.161)  383.351 ms  232.519 ms  287.104 ms
    14  116.251.209.66 (116.251.209.66)  237.110 ms  237.593 ms  376.267 ms
    
    traceroute to 116.251.210.1 (116.251.210.1), 64 hops max, 52 byte packets
     1  my.router (192.168.1.1)  4.224 ms  1.449 ms  1.458 ms
     2  217.47.93.250 (217.47.93.250)  30.396 ms  30.757 ms  31.246 ms
     3  217.47.90.161 (217.47.90.161)  30.456 ms  29.857 ms  30.254 ms
     4  213.1.69.82 (213.1.69.82)  30.818 ms  30.402 ms  31.043 ms
     5  217.41.168.177 (217.41.168.177)  31.484 ms  30.397 ms  30.473 ms
     6  217.41.168.107 (217.41.168.107)  35.463 ms  30.049 ms  30.701 ms
     7  109.159.249.68 (109.159.249.68)  31.283 ms
        109.159.249.106 (109.159.249.106)  30.629 ms
        acc1-10gige-0-0-0-6.l-far.21cn-ipp.bt.net (109.159.249.90)  30.604 ms
     8  core1-te0-0-0-13.ealing.ukcore.bt.net (109.159.249.33)  36.615 ms
        core1-te0-0-0-2.ealing.ukcore.bt.net (109.159.249.27)  35.668 ms
        core1-te0-0-0-0.ealing.ukcore.bt.net (109.159.249.25)  40.676 ms
     9  core1-pos5-0-0.telehouse.ukcore.bt.net (194.74.65.122)  32.133 ms  31.827 ms  34.200 ms
    10  t2as1-tge4-4.uk-lon1.eu.bt.net (166.49.211.145)  31.143 ms  31.302 ms  31.939 ms
    11  t2a1-ge7-0-0.uk-lon1.eu.bt.net (166.49.135.49)  33.534 ms  33.558 ms  31.757 ms
    12  195.66.225.10 (195.66.225.10)  31.540 ms  32.058 ms  31.812 ms
    13  ge-2-3-0-0.lonlx-cr2.ix.singtel.com (203.208.151.210)  32.227 ms
        203.208.152.238 (203.208.152.238)  32.745 ms
        203.208.152.242 (203.208.152.242)  31.707 ms
    14  203.208.173.85 (203.208.173.85)  32.258 ms
        203.208.171.181 (203.208.171.181)  33.655 ms
        203.208.173.85 (203.208.173.85)  31.908 ms
    15  203.208.166.62 (203.208.166.62)  217.992 ms
        203.208.166.162 (203.208.166.162)  231.706 ms  221.569 ms
    16  203.208.166.181 (203.208.166.181)  363.033 ms
        203.208.174.182 (203.208.174.182)  224.239 ms
        203.208.166.181 (203.208.166.181)  224.263 ms
    17  ge-2-0-0.sn-sintp1-bo303.singnet.com.sg (165.21.12.106)  524.459 ms
        203.208.166.162 (203.208.166.162)  390.152 ms
        ge-2-0-0.sn-sintp1-bo303.singnet.com.sg (165.21.12.106)  219.141 ms
    18  165.21.255.74 (165.21.255.74)  393.483 ms
        203.208.191.102 (203.208.191.102)  391.272 ms
        165.21.255.74 (165.21.255.74)  220.899 ms
    19  115.42.248.33 (115.42.248.33)  359.100 ms  215.196 ms
        ge-2-0-0.sn-sintp1-bo303.singnet.com.sg (165.21.12.106)  354.578 ms
    20  115.42.248.34 (115.42.248.34)  214.840 ms  354.687 ms
        165.21.255.74 (165.21.255.74)  227.106 ms
    21  edge-1.v50.com3.sg.gs (203.175.175.17)  386.005 ms
        115.42.248.33 (115.42.248.33)  215.354 ms
        edge-1.v50.com3.sg.gs (203.175.175.17)  397.893 ms
    22  edge-1.v71.globalswitch.sg.gs (203.175.175.132)  229.154 ms  226.138 ms
        115.42.248.34 (115.42.248.34)  386.582 ms
    23  edge-1.v50.com3.sg.gs (203.175.175.17)  225.607 ms
        116.251.210.240 (116.251.210.240)  388.134 ms  313.270 ms
    24  dns1.oneasiahost.com (116.251.210.1)  229.735 ms  232.345 ms  233.265 ms
    
  • @Daniel said: Why do your trace routes look weird? Their meant to look like this

    lol i was using windows

  • MrAndroidMrAndroid Member
    edited April 2012

    @DanielM said: lol i was using windows

    Windows ones look so messy, also Windows uses a different method to trace route compared to UNIX.

    Which is why UNIX returns a trace route so much quicker, but I think Windows is slightly more accurate.

  • minamina Member
    edited April 2012

    From Finland:

    3 2 ms 1 ms 1 ms hkicore2-o-4-1-0-0.datanet.tele.fi [141.208.25.1
    ]
    4 139 ms 98 ms 9 ms hkiasbr2-s0-0-0.datanet.tele.fi [141.208.8.14]
    5 1 ms 1 ms 1 ms hls-b1-link.telia.net [213.248.68.209]
    6 8 ms 8 ms 8 ms s-bb1-link.telia.net [213.248.64.101]
    7 18 ms 18 ms 18 ms kbn-bb1-link.telia.net [213.248.65.142]
    8 99 ms 99 ms 99 ms nyk-bb1-link.telia.net [80.91.249.24]
    9 172 ms 173 ms 173 ms sjo-bb1-link.telia.net [213.248.80.1]
    10 174 ms 174 ms 174 ms singaporetelecom-ic-150842-sjo-bb1.c.telia.net [
    80.239.167.178]
    11 173 ms 173 ms 173 ms 203.208.149.2
    12 185 ms 175 ms 175 ms 203.208.171.105
    13 369 ms 357 ms 358 ms 203.208.166.198
    14 363 ms 348 ms 393 ms ge-4-0-0-0.sngtp-cr2.ix.singtel.com [203.208.182
    .102]
    15 356 ms 367 ms 369 ms 203.208.166.198
    16 368 ms 352 ms 374 ms 202.160.250.230
    17 407 ms 367 ms 375 ms 203.208.232.234
    18 363 ms 360 ms 365 ms 203.208.255.230
    19 351 ms 351 ms 362 ms 202.176.211.36
    20 375 ms 356 ms 378 ms edge-1.v71.globalswitch.sg.gs [203.175.175.132]

    21 348 ms 358 ms 348 ms 116.251.209.66

    3 1 ms 1 ms 1 ms hkicore2-o-4-1-0-0.datanet.tele.fi [141.208.25.1
    ]
    4 1 ms 1 ms 1 ms hkiasbr2-s0-0-0.datanet.tele.fi [141.208.8.14]
    5 1 ms 1 ms 1 ms hls-b1-link.telia.net [213.248.68.209]
    6 31 ms 8 ms 8 ms s-bb1-link.telia.net [213.155.134.106]
    7 18 ms 17 ms 17 ms kbn-bb1-link.telia.net [213.155.130.53]
    8 98 ms 98 ms 98 ms nyk-bb1-link.telia.net [80.91.247.117]
    9 171 ms 171 ms 171 ms sjo-bb1-link.telia.net [80.91.252.153]
    10 172 ms 172 ms 172 ms singaporetelecom-ic-150842-sjo-bb1.c.telia.net [
    80.239.167.178]
    11 173 ms 173 ms 173 ms 203.208.152.109
    12 369 ms 173 ms 361 ms so-2-0-2-0.sngtp-cr1.ix.singtel.com [203.208.149
    .241]
    13 356 ms 368 ms 371 ms 203.208.166.62
    14 420 ms 360 ms 364 ms 203.208.191.102
    15 355 ms 367 ms 363 ms Ge-2-0-0.sn-sintp1-bo303.singnet.com.sg [165.21.
    12.106]
    16 354 ms 345 ms 370 ms 203.208.174.182
    17 356 ms 368 ms 356 ms 115.42.248.33
    18 344 ms 347 ms 356 ms 115.42.248.34
    19 365 ms 367 ms 357 ms edge-1.v50.com3.sg.gs [203.175.175.17]
    20 366 ms 357 ms 354 ms 115.42.248.34
    21 350 ms 359 ms 347 ms edge-1.v50.com3.sg.gs [203.175.175.17]
    22 353 ms 372 ms 358 ms dns1.oneasiahost.com [116.251.210.1]

  • DanielMDanielM Member
    edited April 2012

    @Daniel said: Which is why UNIX returns a trace route so much quicker, but I think Windows is slightly more accurate.

    I have an Mod for my ping/traceroutes. its called tracert2 and its like x10 faster

    For example here is a trace from HOME.

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    
    C:\Users\DL2>tracert2 116.251.209.66
    
    Tracing route to 116.251.209.66 with TTL of 32:
    
     1  1ms    2ms    1ms    192.168.43.1
     2   *      *      *     Request timed out.
     3  101ms  87ms   91ms   10.126.243.1
     4  107ms  79ms   89ms   10.111.227.221
     5  97ms   159ms  108ms  10.111.227.82
     6  158ms  99ms   69ms   10.111.226.101
     7  68ms   79ms   79ms   149.254.195.226
     8  65ms   69ms   69ms   10.126.168.222
     9  126ms  69ms   69ms   194.25.208.253
    10  116ms  99ms   119ms  217.239.40.181
    11   *      *      *     Request timed out.
    12  320ms  310ms  308ms  63.216.152.187
    13  296ms  297ms  290ms  edge-1.v75.globalswitch.sg.gs [203.175.175.161]
    14  457ms  357ms  298ms  116.251.209.66
    
  • @DanielM said: I have an Mod for my ping/traceroutes. its called tracert2 and its like x10 faster

    So its probably using UDP packets then.

  • @Daniel said: So its probably using UDP packets then.

    Am not sure. I always thought UDP was blocked on this connection

  • I prefer mtr when debugging traceroutes. Jeez, the 2nd IP is like a drunken traveling salesman going around and around singtel (from San Diego). It looks like Singtel is randomly load-balancing across multiple routers all the way from the edge at LAX to Singapore. This is averaged over 100 traceroutes:

    anoc (0.0.0.0)                                                               Wed Apr 18 03:04:25 2012
    Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                 Packets               Pings
     Host                                                      Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. gw.sd1.amerinoc.com                                     0.0%   101    0.5   4.3   0.3 112.0  16.2
     2. te2-4.ccr01.san05.atlas.cogentco.com                    0.0%   101    0.8  15.9   0.5 202.5  40.7
     3. te4-8.ccr01.san03.atlas.cogentco.com                    0.0%   101    0.9   9.5   0.7 196.4  33.7
     4. te8-2.ccr01.san01.atlas.cogentco.com                    0.0%   101  160.3  37.0   0.9 199.7  61.5
     5. te0-3-0-4.ccr22.lax01.atlas.cogentco.com                0.0%   101    4.0   5.4   3.8  81.9   9.1
     6. te3-4.ccr02.lax04.atlas.cogentco.com                    0.0%   100    3.9  13.2   3.8 169.3  31.3
     7. 203.208.153.45                                          0.0%   100    3.8   9.7   3.7 137.2  21.8
     8. GigabitEthernet0-1.sngtp-ar1.ix.singtel.com             0.0%   100    6.6   8.6   3.7  79.6  14.8
        ge-3-1-0-0.sngtp-cr2.ix.singtel.com
        203.208.153.141
        ge-1-0-0-0.laxow-cr2.ix.singtel.com
        203.208.152.105
        203.208.171.225
        ge-5-0-0-0.laxow-cr2.ix.singtel.com
        xe-1-1-0-0.laxow-dr3.ix.singtel.com
     9. 203.208.171.189                                         0.0%   100  180.2  88.5   3.9 227.9  89.1
        203.208.153.121
        203.208.178.185
        ge-2-3-0-0.laxow-ar2.ix.singtel.com
        so-2-0-2-0.sngc3-cr2.ix.singtel.com
        203.208.171.85
        xe-1-0-0-0.laxow-cr1.ix.singtel.com
        ge-0-3-0-0.laxow-ar1.ix.singtel.com
    10. 203.208.178.185                                         0.0%   100  196.6 189.2 168.2 292.6  16.2
        ge-2-3-0-0.laxow-ar2.ix.singtel.com
        203.208.153.246
        203.208.153.242
        203.208.153.121
        POS6-0-0.sngtp-ar5.ix.singtel.com
        203.208.154.45
        203.208.171.189
    11. ge-4-0-0-0.sngtp-dr2.ix.singtel.com                     0.0%   100  199.3 193.4 175.5 299.3  16.3
        ge-3-0-0-0.sngtp-dr2.ix.singtel.com
        so-6-0-0-0.sngtp-ar6.ix.singtel.com
        xe-0-0-0-0.sngc3-cr2.ix.singtel.com
        203.208.153.254
        ge-7-0-0-0.laxow-dr1.ix.singtel.com
        xe-0-0-0-0.laxow-cr2.ix.singtel.com
        xe-0-0-0-0.sngc3-cr1.ix.singtel.com
    12. 203.208.174.182                                         0.0%   100  197.2 188.9 168.2 252.3  13.4
        203.208.166.202
        203.208.191.102
        203.208.153.246
        203.208.152.230
        POS0-0-0.venus.ix.singtel.com
        POS6-0-0.sngtp-ar5.ix.singtel.com
    13. ge-3-0-0-0.sngtp-dr2.ix.singtel.com                     0.0%   100  180.6 192.6 173.5 254.6  13.4
        so-6-0-0-0.sngtp-ar6.ix.singtel.com
        Ge-2-0-0.sn-sintp1-bo303.singnet.com.sg
        ge-4-0-0-0.sngtp-dr2.ix.singtel.com
        203.208.153.110
    14. 203.208.191.102                                         0.0%   100  178.1 187.2 169.0 221.3  10.8
        203.208.174.182
        165.21.255.74
    15. Ge-2-0-0.sn-sintp1-bo303.singnet.com.sg                 1.0%   100  178.7 181.4 168.9 263.7  11.9
        115.42.248.33
    16. 115.42.248.34                                           1.0%   100  186.4 184.1 168.9 276.8  14.1
        165.21.255.74
    17. 115.42.248.33                                           0.0%   100  178.7 184.8 168.9 233.0  12.9
        edge-2.v51.com3.sg.gs
    18. edge-1.v71.globalswitch.sg.gs                           3.0%   100  195.7 191.7 176.4 249.6   9.7
        115.42.248.34
    19. edge-2.v51.com3.sg.gs                                   0.0%   100  196.4 191.0 178.7 233.7   7.1
        116.251.210.240
    20. dns1.oneasiahost.com                                    1.0%   100  195.1 197.0 186.0 330.2  15.7
    

    That took a 250x80 xterm!!

    The other one performs great:

    anoc (0.0.0.0)                                                        Wed Apr 18 03:17:43 2012
    Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                          Packets               Pings
     Host                                               Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. gw.sd1.amerinoc.com                              0.0%   137    0.4  12.7   0.3 726.5  69.1
     2. te2-4.ccr01.san05.atlas.cogentco.com             0.0%   136    1.2  21.5   0.6 646.7  69.0
     3. te4-8.ccr01.san03.atlas.cogentco.com             0.7%   136    1.8   8.9   0.8 562.9  50.9
     4. te8-2.ccr01.san01.atlas.cogentco.com             0.0%   136    1.0  77.0   0.9 6005. 516.4
     5. te0-3-0-4.ccr22.lax01.atlas.cogentco.com         0.0%   136    4.0   7.0   3.8 402.7  34.2
     6. te4-8.ccr02.lax05.atlas.cogentco.com             2.9%   136    3.9  44.0   3.9 318.8  65.5
     7. te4-1.mpd01.lax05.atlas.cogentco.com             0.0%   136    5.0  48.1   3.9 238.3  67.4
     8. te1-3-10G.ar3.LAX2.gblx.net                      0.7%   136    5.3   9.0   4.4 103.5  16.7
     9. PCCW.te6-2.1140.ar4.LAX1.gblx.net                1.5%   136  146.3  62.8  15.1 1042. 110.2
    10. 63.216.152.186                                   0.0%   136  191.6 193.8 185.4 978.1  68.8
    11. edge-1.v75.globalswitch.sg.gs                    0.7%   136  186.2 187.6 186.1 239.8   6.5
    12. 116.251.209.66                                   0.0%   136  190.9 194.0 188.7 817.8  54.1
    

    The only difference is that one is using Singtel and the other Global Crossing on the hop across the Pacific!

  • @joepie91: sprunge is awesome...thanks

  • klikliklikli Member
    edited April 2012

    Hongkong with PCCW/Netvigator: http://pastebin.com/rfJW4V0r
    I highly recommend SoftLayer Singapore location however. They announces their prefixes around Asia (Hongkong, Tokyo, and Singapore of course) with hopes to minimize the Asia transport issue. They also get transits from major ISPs' from Asia (Tata, NTT). Plus, the prices are as same as that you got for US locations.

  • @klikli
    Thanks, I'm quite surprised with your traceroute though, because we're actually peering at HKIX so we're receiving netvigator routes from there, but it seems that they aren't accepting our routes from the route server so the reverse isn't true.

    traceroute to 112.119.178.254 (112.119.178.254), 30 hops max, 60 byte packets
     1  116.251.210.253 (116.251.210.253)  0.399 ms  0.475 ms  0.551 ms
     2  edge-1.v75.ntp.sg.gs (203.175.175.164)  1.101 ms  1.218 ms  1.232 ms
     3  ims5-10G.hkix.net (202.40.161.25)  37.782 ms  37.784 ms *
     4  n219076107037.netvigator.com (219.76.107.37)  38.231 ms  38.520 ms  38.448 ms
     5  n112119178254.netvigator.com (112.119.178.254)  39.846 ms  39.385 ms  39.594 ms
  • klikliklikli Member
    edited April 2012

    @Kenshin said: Thanks, I'm quite surprised with your traceroute though, because we're actually peering at HKIX so we're receiving netvigator routes from there, but it seems that they aren't accepting our routes from the route server so the reverse isn't true.

    My bad, see your prefixes at HKIX looking glass. Are you getting your own transport from Hongkong to Singapore? I fear you will be needing to upgrade your FE to GE soon...

    EDIT: I suppose you're purchasing transit from PCCW/BTN right? Then that's the reason;)

    EDIT 2: Traceroute from HE Singapore actually get back to HKIX.

    PS: For all of the above statements, I was actually referring to the first IP provided:)

  • KenshinKenshin Member
    edited April 2012

    @klikli said: My bad, see your prefixes at HKIX looking glass. Are you getting your own transport from Hongkong to Singapore? I fear you will be needing to upgrade your FE to GE soon...

    EDIT: I suppose you're purchasing transit from PCCW/BTN right? Then that's the reason;)

    EDIT 2: Traceroute from HE Singapore actually get back to HKIX.

    Yes we have our own L2 transport from HKIX back to Singapore. Usage is still low at this point so no rush to upgrade beyond FE. We also have PCCW transit, which you see in the first IP only since I'm using a different route for the second IP. I'm just amused that netvigator doesn't use any of the routes from the RS, but yet they're broadcasting their routes, likely due to HKIX's requirement that all HK IPs are broadcasted through the RS.

Sign In or Register to comment.