Howdy, Stranger!

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


EDIS Asia! - Page 4
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.

EDIS Asia!

124

Comments

  • klikliklikli Member
    edited June 2012

    @William said: Upstream Telstra and PCCW, v6 enabled.

    You sure? :P (Perfectly no offense)
    image

  • Yes, but PCCW seems to prefer Telstra over their own BW for whatever reason :p

  • AndriAndri Member
    edited June 2012

    From Indonesia

    Pinging 103.11.140.3 with 32 bytes of data:
    
    Reply from 103.11.140.3: bytes=32 time=174ms TTL=241
    Reply from 103.11.140.3: bytes=32 time=174ms TTL=241
    Reply from 103.11.140.3: bytes=32 time=176ms TTL=241
    Reply from 103.11.140.3: bytes=32 time=174ms TTL=241
    
    Ping statistics for 103.11.140.3:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 174ms, Maximum = 176ms, Average = 174ms
  • AndriAndri Member
    edited June 2012

    From Indonesia (Traceroute):

    Tracing route to 10G-ADN-103-11-140-3.solone.net [103.11.140.3]
    over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  . [192.168.2.1]
      2    48 ms    48 ms    43 ms  180.253.144.1
      3    45 ms    44 ms    47 ms  180.252.2.45
      4    72 ms    75 ms    74 ms  13.subnet118-98-57.astinet.telkom.net.id [118.98.57.13]
      5    76 ms    78 ms    77 ms  161.subnet118-98-53.astinet.telkom.net.id [118.98.53.161]
      6    76 ms    74 ms    71 ms  37.subnet118-98-56.astinet.telkom.net.id [118.98.56.37]
      7    75 ms    78 ms    77 ms  61.subnet118-98-61.astinet.telkom.net.id [118.98.61.61]
      8     *       73 ms     *     62.subnet118-98-61.astinet.telkom.net.id [118.98.61.62]
      9    72 ms    75 ms    74 ms  if-13-0-1.core1.S9R-Singapore.as6453.net [209.58.82.185]
     10    72 ms    74 ms    75 ms  if-0-3-1-0.tcore2.SVW-Singapore.as6453.net [180.87.15.33]
     11   184 ms   166 ms   169 ms  180.87.15.218
     12   171 ms   171 ms   174 ms  unknown.telstraglobal.net [202.126.128.26]
     13   174 ms   174 ms   176 ms  10G-ADN-103-11-140-3.solone.net [103.11.140.3]</pre>
    
  • HerrMaulwurfHerrMaulwurf Member
    edited June 2012

    From T-Online DSL in Germany

    Routenverfolgung zu 10G-ADN-103-11-140-3.solone.net [103.11.140.3] über maximal
    30 Abschnitte:

    1 1 ms 1 ms <1 ms 192.168.2.1
    2 34 ms 30 ms 30 ms 217.0.117.91
    3 30 ms 30 ms 31 ms 87.190.189.86
    4 49 ms 50 ms 47 ms lon-sa3-i.LON.GB.NET.DTAG.DE [62.154.14.22]
    5 45 ms 46 ms 47 ms 80.157.128.226
    6 314 ms 261 ms 242 ms i-3-3-3.istt-core01.bx.telstraglobal.net 202.84.143.254]
    7 277 ms 249 ms 247 ms unknown.telstraglobal.net [202.84.243.114]
    8 287 ms 294 ms 297 ms unknown.telstraglobal.net [202.126.128.26]
    9 315 ms 359 ms 339 ms 10G-ADN-103-11-140-3.solone.net [103.11.140.3]

    Ablaufverfolgung beendet.

    From T-Online DSL with Teredo tunneling in Germany

    Routenverfolgung zu 2400:8800:1f08::1 über maximal 30 Abschnitte

    1 1180 ms 358 ms 359 ms 6to4.hkg1.he.net [2001:470:0:163::2]
    2 382 ms 359 ms 362 ms gigabitethernet3-14.core1.hkg1.he.net [2001:470:0:163::1]
    3 360 ms 361 ms 363 ms pccw.gige-g3-4.core1.hkg1.he.net [2001:470:0:11f::2]
    4 * * * Zeitüberschreitung der Anforderung.
    5 * * * Zeitüberschreitung der Anforderung.
    6 489 ms * 396 ms 2400:8800:1f08::1

    Ablaufverfolgung beendet.

    EDIT: Code tag is not working correctly for me.

  • SpiritSpirit Member
    edited June 2012

    From india:

    traceroute to 103.11.140.3 (103.11.140.3), 30 hops max, 40 byte packets
     1  static-202-65-135-204.ctrls.in (202.65.135.204)  0.179 ms  0.110 ms  0.085 ms
     2  static-202-65-152-25.pol.net.in (202.65.152.25)  0.421 ms  0.350 ms  0.290 ms
     3  121.240.252.17.STATIC-Hyderabad.vsnl.net.in (121.240.252.17)  1.402 ms 121.241.54.229.static-Hyderabad.vsnl.net.in (121.241.54.229)  1.357 ms 121.240.252.17.STATIC-Hyderabad.vsnl.net.in (121.240.252.17)  1.296 ms
     4  * * *
     5  ix-4-2.tcore1.CXR-Chennai.as6453.net (180.87.36.9)  48.887 ms  48.778 ms  48.884 ms
     6  if-5-2.tcore1.SVW-Singapore.as6453.net (180.87.12.53)  50.531 ms  50.492 ms  50.424 ms
     7  if-5-2.tcore2.SVW-Singapore.as6453.net (180.87.15.69)  46.340 ms  46.733 ms if-2-2.tcore2.SVW-Singapore.as6453.net (180.87.12.2)  48.200 ms
     8  180.87.15.218 (180.87.15.218)  51.307 ms  51.264 ms  51.199 ms
     9  unknown.telstraglobal.net (202.126.128.26)  47.816 ms  47.826 ms  47.521 ms
    10  10G-ADN-103-11-140-3.solone.net (103.11.140.3)  47.815 ms  47.936 ms  48.368 ms

    Nice, isn't it? :)

    From estonia:

    traceroute to 103.11.140.3 (103.11.140.3), 30 hops max, 60 byte packets
     1  80.79.116.82 (80.79.116.82)  0.100 ms  0.030 ms  0.036 ms
     2  80.79.118.193 (80.79.118.193)  0.483 ms  0.536 ms  0.565 ms
     3  194.204.15.230 (194.204.15.230)  29.408 ms  29.450 ms  29.514 ms
     4  so2-2-0-0.bbr1.tln1.ee.eunetip.net (213.192.190.225)  0.351 ms  0.327 ms  0.303 ms
     5  so6-0-0-0.bbr1.sto4.se.eunetip.net (213.192.184.86)  9.154 ms  9.135 ms  9.096 ms
     6  xe-0-1-0-xcr1.skt.cw.net (166.63.221.193)  9.343 ms  9.260 ms  9.260 ms
     7  xe-0-2-1-xcr2.amd.cw.net (195.2.9.233)  35.543 ms  35.533 ms xe-0-3-1-xcr2.amd.cw.net (195.2.9.217)  35.980 ms
     8  xe-4-2-1-xcr1.amd.cw.net (195.2.30.37)  35.645 ms  35.575 ms  35.514 ms
     9  xe-0-1-0-xcr1.lsw.cw.net (195.2.25.101)  36.389 ms xe-7-2-0-xcr2.lsw.cw.net (195.2.25.138)  35.554 ms xe-0-1-0-xcr1.lsw.cw.net (195.2.25.101)  36.330 ms
    10  xe-4-3-0-xcr1.lns.cw.net (195.2.28.42)  35.732 ms xe-3-0-0-xcr1.lns.cw.net (195.2.25.206)  40.466 ms  35.448 ms
    11  195.66.236.166 (195.66.236.166)  35.972 ms  35.967 ms  35.420 ms
    12  i-3-3-3.istt-core01.bx.telstraglobal.net (202.84.143.254)  230.557 ms  237.940 ms  237.851 ms
    13  unknown.telstraglobal.net (202.84.243.114)  241.550 ms  241.532 ms  241.510 ms
    14  unknown.telstraglobal.net (202.126.128.26)  239.183 ms  239.184 ms  239.183 ms
    15  10G-ADN-103-11-140-3.solone.net (103.11.140.3)  243.922 ms  243.732 ms  243.553 ms
  • KenshinKenshin Member
    edited June 2012

    @William said: Yes, but PCCW seems to prefer Telstra over their own BW for whatever reason :p

    PCCW path heavily prepended 4 times. Telstra route not prepended. Added my route view from my PCCW router, IPs edited just in case.

    103.11.140.0/24    *[BGP/170] 00:08:53, MED 10, localpref 100, from X.X.X.X
                          AS path: 9911 3758 4657 4637 9234 I
                        > to X.X.X.X via ae0.72
                          to X.X.X.X via ae0.72
                        [BGP/170] 00:08:53, MED 10, localpref 100, from X.X.X.X
                          AS path: 9911 3758 4657 4637 9234 I
                        > to X.X.X.X via ae0.72
                          to X.X.X.X via ae0.72
                        [BGP/170] 4w6d 06:51:30, MED 10, localpref 100
                          AS path: 3491 9234 9234 9234 9234 9234 I
                        > to X.X.X.X via ae0.91
    

    4657 = Starhub
    4637 = Telstra
    3491 = PCCW
    9234 = Sol One

  • ChanChan Member
    edited June 2012

    From Linode in Japan

    root@linode512:~# ping 103.11.140.3

    PING 103.11.140.3 (103.11.140.3) 56(84) bytes of data.
    64 bytes from 103.11.140.3: icmp_req=1 ttl=245 time=94.9 ms
    64 bytes from 103.11.140.3: icmp_req=2 ttl=245 time=93.2 ms
    64 bytes from 103.11.140.3: icmp_req=3 ttl=245 time=93.9 ms
    64 bytes from 103.11.140.3: icmp_req=4 ttl=245 time=93.9 ms
    64 bytes from 103.11.140.3: icmp_req=5 ttl=245 time=93.6 ms
    64 bytes from 103.11.140.3: icmp_req=6 ttl=245 time=93.2 ms
    ^C
    --- 103.11.140.3 ping statistics ---
    11 packets transmitted, 11 received, 0% packet loss, time 10009ms
    rtt min/avg/max/mdev = 93.087/93.745/94.991/0.647 ms

    root@linode512:~# ping6 2400:8800:1f08::1

    PING 2400:8800:1f08::1(2400:8800:1f08::1) 56 data bytes
    64 bytes from 2400:8800:1f08::1: icmp_seq=1 ttl=54 time=101 ms
    64 bytes from 2400:8800:1f08::1: icmp_seq=2 ttl=54 time=93.9 ms
    64 bytes from 2400:8800:1f08::1: icmp_seq=3 ttl=54 time=94.3 ms
    64 bytes from 2400:8800:1f08::1: icmp_seq=4 ttl=54 time=100 ms
    64 bytes from 2400:8800:1f08::1: icmp_seq=5 ttl=54 time=93.9 ms
    64 bytes from 2400:8800:1f08::1: icmp_seq=6 ttl=54 time=102 ms
    64 bytes from 2400:8800:1f08::1: icmp_seq=7 ttl=54 time=97.5 ms
    64 bytes from 2400:8800:1f08::1: icmp_seq=8 ttl=54 time=94.0 ms
    ^C
    --- 2400:8800:1f08::1 ping statistics ---
    9 packets transmitted, 8 received, 11% packet loss, time 8007ms
    rtt min/avg/max/mdev = 93.911/97.181/102.196/3.372 ms

    root@linode512:~# traceroute 103.11.140.3

    traceroute to 103.11.140.3 (103.11.140.3), 30 hops max, 60 byte packets
    1 106.187.33.2 (106.187.33.2) 82.448 ms 82.451 ms 82.438 ms
    2 124.215.199.121 (124.215.199.121) 82.454 ms 82.453 ms 82.435 ms
    3 otejbb204.kddnet.ad.jp (124.215.194.177) 82.359 ms 82.346 ms 59.128.4.121 (59.128.4.121) 82.303 ms
    4 ix-ote206.kddnet.ad.jp (118.155.197.5) 82.321 ms 82.326 ms 82.304 ms
    5 i-0-2-0-0.siko02.bi.telstraglobal.net (202.84.219.38) 97.517 ms 97.553 ms 97.539 ms
    6 i-1-1-0.siko-core01.bi.telstraglobal.net (202.84.219.37) 82.206 ms 2.830 ms 2.795 ms
    7 i-10-2.hkhh-core01.bx.telstraglobal.net (202.84.141.221) 61.014 ms 60.992 ms 60.804 ms
    8 i-3-0-0.istt-core01.bx.telstraglobal.net (202.84.249.218) 101.980 ms 101.791 ms 101.721 ms
    9 unknown.telstraglobal.net (202.84.243.114) 105.265 ms 105.200 ms 105.207 ms
    10 63.216.152.194 (63.216.152.194) 93.001 ms 92.920 ms 92.941 ms
    11 10G-ADN-103-11-140-3.solone.net (103.11.140.3) 93.683 ms 93.650 ms 93.223 ms

    The traffic seems to be routed through Hong Kong so the ping isn't that great. Also I pinged the IP using "just-ping" and the ping from Shanghai to the IP was not stable, goes from 100ms to 900ms. http://just-ping.com/index.php?vh=103.11.140.3

  • lbftlbft Member
    edited June 2012

    @William said: It is in SIngapore.

    Surprisingly good results from Sydney, Australia:

      2    28 ms    26 ms    27 ms  lns20.syd6.internode.on.net [150.101.199.159]
      3    28 ms    26 ms    27 ms  te3-3.cor2.syd6.internode.on.net [150.101.195.9]
      4    29 ms    29 ms    26 ms  gi6-0-0-134.bdr1.syd6.internode.on.net [150.101.195.229]
      5    28 ms    29 ms    26 ms  te2-0-0.bdr1.syd4.internode.on.net [150.101.197.2]
      6    28 ms    26 ms    28 ms  150-101-197-234.internode.on.net [150.101.197.234]
      7   131 ms   134 ms   137 ms  i-0-1-0-0-3001-peer.6ntp02.pr.telstraglobal.net [202.126.173.149]
      8   132 ms   130 ms   129 ms  63.216.152.194
      9   132 ms   131 ms   132 ms  10G-ADN-103-11-140-3.solone.net [103.11.140.3]

    I looked at several Aussie looking glasses and they all had similar pings (100-110ms from Sydney). Very nice.

    Edit: IPv6 routing is atrocious, though. I don't have native IPv6 yet but my ISP's looking glass only sees the IPv6 via HE in Chicago. The same result on several VPSes. It makes me wonder if it's not using the HE tunnelbroker in Chicago (which makes no sense, HE even has a node in Singapore...)

    @William said: Yes, but PCCW seems to prefer Telstra over their own BW for whatever reason :p

    PCCW and Telstra are partners in Reach. I wouldn't be surprised if there was some blurring in their networks in Reach's area.

  • ZiggaZigga Member
    edited June 2012

    @lbft said: Surprisingly good results from Sydney, Australia:

    +1 but from Melbourne

    1 10.20.20.187 12 msec 12 msec 12 msec 2 nme-sot-dry-csw1-te-4-3.tpgi.com.au (203.12.162.249) 12 msec 12 msec 12 msec 3 nme-sot-dry-crt2-ge-7-0-0.tpgi.com.au (202.7.162.41) 12 msec 12 msec 12 msec 4 syd-sot-ken-crt3-Te-9-1.tpgi.com.au (203.29.140.82) 24 msec 24 msec 24 msec 5 202.167.228.80 24 msec 24 msec 24 msec 6 i-0-1-0-0-3001-peer.6ntp02.pr.telstraglobal.net (202.126.173.149) 160 msec 1 60 msec 160 msec 7 unknown.telstraglobal.net (202.126.128.26) 176 msec 176 msec 172 msec 8 10G-ADN-103-11-140-3.solone.net (103.11.140.3) 160 msec 160 msec 160 msec

    @William Wish I read the entire post to see the upstream providers, was a bit of a shock to see Telstra there!

  • @lbft said: if it's not using the HE tunnelbroker in Chicago

    No, it's PCCW - They likely route large amounts of v6 over HE to save costs....

  • From Indonesia using Smart Telecom :

    C:\Users\Mr_Five>tracert 103.11.140.3

    Tracing route to 10G-ADN-103-11-140-3.solone.net [103.11.140.3]

    over a maximum of 30 hops:

    1 68 ms 59 ms 58 ms 10.17.94.77

    2 * * * Request timed out.
    3 48 ms 61 ms 79 ms 10.17.97.41
    4 39 ms 58 ms 58 ms 202.70.48.49
    5 59 ms 55 ms 61 ms 202.70.48.17
    6 111 ms 71 ms 68 ms IP-125-13.MCS.napinfo.net [119.110.125.13]
    7 96 ms 71 ms 81 ms IP-112-245.MCS.napinfo.net [119.110.112.245]
    8 88 ms 75 ms 94 ms 203.208.192.229
    9 86 ms 87 ms 80 ms ge-1-1-9-0.sngc3-dr1.ix.singtel.com [203.208.182.133]
    10 164 ms 248 ms 159 ms so-4-3-1-0.toknf-cr3.ix.singtel.com [203.208.151.122]
    11 159 ms 161 ms 167 ms i-0-2-0-0.siko02.bi.telstraglobal.net [202.84.219.38]
    12 143 ms 159 ms 150 ms i-0-2-0-0.siko02.bi.telstraglobal.net [202.84.219.38]
    13 164 ms 302 ms 138 ms i-1-1-0.siko-core01.bi.telstraglobal.net [202.84.219.37]
    14 180 ms 154 ms 158 ms i-3-1-0.istt-core01.bx.telstraglobal.net [202.84.249.214]
    15 157 ms 159 ms 151 ms unknown.telstraglobal.net [202.84.243.114]
    16 162 ms 159 ms 150 ms unknown.telstraglobal.net [202.84.243.114]
    17 142 ms 132 ms 150 ms 10G-ADN-103-11-140-3.solone.net [103.11.140.3]

    Trace complete.

  • klikliklikli Member

    @William
    It's weird because they routed via 6to4.hkg1.he.net I guess:o
    I see that hop when using Windows' integrated Teredo anyway.

  • lbftlbft Member
    edited June 2012

    @William said: No, it's PCCW - They likely route large amounts of v6 over HE to save costs....

    Yeah, I was way off the mark. I ran some more IPv6 traceroutes from various places and I can see it going via Level 3 and Cogent as well as HE.

    I could only see PCCW connecting with HE in Chicago and HK, which looks to be the cause of the crappy routing I noticed - my ISP peers with HE in L.A., but nowhere in Asia, and so it has to go via Chicago.

    I'm sure the IPv6 routing will get better as time goes on (especially with Australia-Singapore Cable coming online) and the unusually good IPv4 connectivity to Australia more than makes up for it in the meantime for me (although to be honest, if the HK price premium is anything to go by I probably won't be picking one up anyway.)

  • WilliamWilliam Member
    edited June 2012

    The problem is that the Test IPv6 is currently not inside their network but the PCCW edge in SG :)

    Anyway, i will try to get some testfiles.

  • MaouniqueMaounique Host Rep, Veteran
    edited June 2012

    Looks disastruos from vodafone in romania I hope this is not your intended audience:
    [root@www ~]# wget http://hktest.edis.at/100mb.bin
    --2012-06-14 12:34:51-- http://hktest.edis.at/100mb.bin
    Resolving hktest.edis.at... 124.248.212.94, 2400:f100:2:1:216:3eff:feb2:ddc0
    Connecting to hktest.edis.at|124.248.212.94|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 102400000 (98M) [application/octet-stream]
    Saving to: `100mb.bin'

    100%[======================================>] 102,400,000 124K/s in 5m 37s

    2012-06-14 12:40:29 (297 KB/s) - `100mb.bin' saved [102400000/102400000]

    traceroute to 124.248.212.94 (124.248.212.94), 30 hops max, 40 byte packets
    1 my router 0.875 ms 0.709 ms 0.649 ms
    2 gw 1.873 ms 1.581 ms 1.408 ms
    3 192.168.133.53 (192.168.133.53) 3.103 ms 2.780 ms 2.207 ms
    4 192.168.196.121 (192.168.196.121) 2.450 ms 2.724 ms 2.514 ms
    5 85.205.17.241 (85.205.17.241) 11.056 ms 12.395 ms 12.821 ms
    6 85.205.30.73 (85.205.30.73) 53.179 ms 52.958 ms 50.342 ms
    7 85.205.25.166 (85.205.25.166) 58.981 ms 58.606 ms 58.514 ms
    8 92.79.213.121 (92.79.213.121) 219.640 ms 219.774 ms 219.663 ms
    9 188.111.129.238 (188.111.129.238) 218.068 ms 218.179 ms 217.890 ms
    10 145.254.23.46 (145.254.23.46) 215.970 ms 219.690 ms 219.353 ms
    11 paix.he.net (198.32.176.20) 211.339 ms 216.778 ms 218.250 ms
    12 10gigabitethernet9-3.core1.sjc2.he.net (72.52.92.70) 216.494 ms 216.457 ms 216.538 ms
    13 pacnet.10gigabitethernet2-2.core1.sjc2.he.net (216.218.192.234) 213.594 ms 213.628 ms 215.745 ms
    14 po8-0.gw1.sjc1.asianetcom.net (202.147.50.165) 214.634 ms 212.698 ms 212.919 ms
    15 te0-0-2-0.wr1.osa0.asianetcom.net (61.14.157.97) 327.086 ms 327.170 ms 326.851 ms
    16 te0-2-0-0.wr1.hkg0.asianetcom.net (61.14.157.69) 428.190 ms 428.316 ms 427.896 ms
    17 ge-4-1-0-0.cr4.hkg3.asianetcom.net (61.14.157.142) 425.071 ms 425.180 ms 424.875 ms
    18 ge-0-2-0-0.csgw1.hkg3.asianetcom.net (122.152.184.49) 425.723 ms 425.355 ms 425.139 ms
    19 NIT-0002.csgw1.hkg3.asianetcom.net (122.152.189.146) 365.390 ms 365.112 ms 365.323 ms
    20 in.core-rt-003.gi.gi0.2.sunnyvision.com (123.242.225.26) 364.301 ms 363.686 ms 365.496 ms
    21 in.core-sw-001.gi.gi1.0.25.sunnyvision.com (123.242.225.2) 365.072 ms 365.772 ms 365.419 ms
    22 124-248-212-94.sunnyvision.com (124.248.212.94) 364.645 ms 364.321 ms 366.028 ms

    From RDS:

    traceroute 124.248.212.94
    traceroute to 124.248.212.94 (124.248.212.94), 64 hops max, 40 byte packets
    1 GW 2.364 ms 1.742 ms 1.743 ms
    2 172.17.205.234 (172.17.205.234) 1.961 ms 1.910 ms 1.915 ms
    3 194.102.81.1 (194.102.81.1) 4.138 ms 2.838 ms 3.896 ms
    4 213.154.124.55 (213.154.124.55) 51.786 ms 52.757 ms 48.151 ms
    5 195.66.225.168 (195.66.225.168) 189.333 ms 189.072 ms 191.447 ms
    6 61.14.157.93 (61.14.157.93) 290.155 ms 286.981 ms 291.657 ms
    7 61.14.157.2 (61.14.157.2) 300.231 ms 296.254 ms 301.079 ms
    8 61.14.157.6 (61.14.157.6) 402.757 ms 406.207 ms 400.289 ms
    9 61.14.157.106 (61.14.157.106) 406.166 ms 397.081 ms 400.678 ms
    10 122.152.184.49 (122.152.184.49) 396.910 ms 396.759 ms 395.838 ms
    11 122.152.189.146 (122.152.189.146) 338.997 ms 342.279 ms 338.499 ms
    12 123.242.225.26 (123.242.225.26) 336.772 ms 338.699 ms 336.315 ms
    13 123.242.225.2 (123.242.225.2) 354.004 ms 414.001 ms 340.253 ms
    14 124.248.212.94 (124.248.212.94) 338.628 ms 339.306 ms 342.842 ms

    Speed is even worse...
    So connectivity in Eastern Europe is really bad.
    M

  • @Maounique said: So connectivity in Eastern Europe is really bad.

    Yes, but connectivity from anything to eastern europe is bad, so not surprising :)
    (And RDS is bad in general)

    Please also test 103.11.140.3

    Thanked by 1klikli
  • gbshousegbshouse Member, Host Rep

    From Hong Kong
    traceroute to 103.11.140.3 (103.11.140.3), 30 hops max, 40 byte packets
    1 208.111.42.3 0.811 ms 0.753 ms 0.731 ms
    2 208.111.42.2 1.970 ms 3.011 ms 3.667 ms
    3 203.131.243.13 1.385 ms 1.324 ms 1.328 ms
    4 129.250.2.89 1.956 ms 2.084 ms 2.232 ms
    5 129.250.5.213 2.110 ms 1.944 ms 1.921 ms
    6 129.250.4.114 95.017 ms 95.035 ms 95.407 ms
    7 61.213.162.174 95.608 ms 95.557 ms 95.509 ms
    8 210.163.230.237 95.550 ms 210.163.230.233 99.338 ms 210.163.230.237 95.104 ms
    9 60.37.27.68 95.933 ms 118.23.168.69 95.646 ms 60.37.27.68 95.779 ms
    10 210.254.187.174 110.560 ms 122.28.104.190 95.699 ms 210.254.187.174 110.464 ms
    11 210.163.230.218 103.377 ms 210.163.230.98 104.762 ms 210.163.230.94 108.179 ms
    12 59.128.7.136 104.918 ms 104.797 ms 118.155.197.133 104.372 ms
    13 202.84.219.38 108.128 ms 108.085 ms 108.059 ms
    14 202.84.219.37 103.452 ms 103.412 ms 104.014 ms
    15 202.84.141.221 103.996 ms 103.523 ms 103.034 ms
    16 202.84.143.57 135.880 ms 135.795 ms 136.953 ms
    17 202.84.243.114 144.651 ms 144.536 ms 144.232 ms
    18 63.216.152.194 137.674 ms 137.669 ms 137.193 ms
    19 103.11.140.3 141.448 ms 139.759 ms 139.721 ms

    PING 103.11.140.3 (103.11.140.3) 56(84) bytes of data.
    64 bytes from 103.11.140.3: icmp_seq=1 ttl=244 time=156 ms
    64 bytes from 103.11.140.3: icmp_seq=2 ttl=244 time=140 ms
    64 bytes from 103.11.140.3: icmp_seq=3 ttl=244 time=140 ms
    64 bytes from 103.11.140.3: icmp_seq=4 ttl=244 time=141 ms
    64 bytes from 103.11.140.3: icmp_seq=5 ttl=244 time=139 ms

    From India
    traceroute to 103.11.140.3 (103.11.140.3), 30 hops max, 40 byte packets
    1 208.111.45.1 2.484 ms 2.981 ms 3.515 ms
    2 27.251.38.65 0.848 ms 0.895 ms 0.918 ms
    3 114.79.196.182 0.832 ms 0.858 ms 0.889 ms
    4 114.79.196.189 1.108 ms 1.121 ms 1.453 ms
    5 202.148.198.181 0.857 ms 0.878 ms 0.877 ms
    6 114.79.232.1 0.899 ms 0.681 ms 0.614 ms
    7 195.22.197.197 123.544 ms 123.566 ms 123.552 ms
    8 89.221.35.128 322.389 ms 89.221.35.146 325.382 ms 89.221.35.128 322.362 ms
    9 134.159.61.25 324.006 ms 323.831 ms 322.715 ms
    10 202.40.149.129 333.951 ms 202.84.251.169 324.629 ms 202.84.251.193 325.503 ms
    11 202.84.144.2 483.763 ms 484.184 ms 482.538 ms
    12 202.84.140.218 511.517 ms 510.259 ms 510.165 ms
    13 202.84.243.82 520.564 ms 521.916 ms 521.940 ms
    14 202.126.128.26 520.670 ms 519.451 ms 518.938 ms
    15 103.11.140.3 524.191 ms 525.437 ms 525.110 ms

    PING 103.11.140.3 (103.11.140.3) 56(84) bytes of data.
    64 bytes from 103.11.140.3: icmp_seq=1 ttl=242 time=530 ms
    64 bytes from 103.11.140.3: icmp_seq=2 ttl=242 time=530 ms
    64 bytes from 103.11.140.3: icmp_seq=3 ttl=242 time=531 ms
    64 bytes from 103.11.140.3: icmp_seq=4 ttl=242 time=530 ms
    64 bytes from 103.11.140.3: icmp_seq=5 ttl=242 time=531 ms

  • MaouniqueMaounique Host Rep, Veteran

    @William said: Yes, but connectivity from anything to eastern europe is bad, so not surprising :)

    (And RDS is bad in general)

    Please also test 103.11.140.3

    traceroute to 103.11.140.3 (103.11.140.3), 30 hops max, 40 byte packets
    1 Router 0.907 ms 0.449 ms 1.031 ms
    2 GW 3.917 ms 3.883 ms 3.559 ms
    3 192.168.133.53 (192.168.133.53) 3.802 ms 4.079 ms 4.165 ms
    4 192.168.196.121 (192.168.196.121) 3.204 ms 3.649 ms 3.584 ms
    5 85.205.17.241 (85.205.17.241) 14.193 ms 14.627 ms 14.464 ms
    6 85.205.30.73 (85.205.30.73) 53.908 ms 53.625 ms 50.173 ms
    7 85.205.25.166 (85.205.25.166) 56.363 ms 60.519 ms 58.599 ms
    8 92.79.213.121 (92.79.213.121) 72.611 ms 72.474 ms 72.939 ms
    9 188.111.129.238 (188.111.129.238) 67.638 ms 67.357 ms 66.980 ms
    10 92.79.213.138 (92.79.213.138) 71.616 ms 71.723 ms 71.378 ms
    11 * * *
    12 63-218-51-150.static.pccwglobal.net (63.218.51.150) 208.703 ms 208.381 ms 208.600 ms
    13 i-0-0-0-0.tlot-core01.bi.telstraglobal.net (202.84.251.193) 210.100 ms 210.927 ms i-0-4-4-0.tlot-core01.bi.telstraglobal.net (202.40.149.133) 210.555 ms
    14 i-1-0-3.tmh-core04.bx.telstraglobal.net (202.84.144.2) 366.259 ms 365.801 ms 366.271 ms
    15 i-6-3.6ntp-core01.bx.telstraglobal.net (202.84.249.126) 335.207 ms 334.898 ms 334.589 ms
    16 i-0-3-0-0.6ntp02.bi.telstraglobal.net (202.84.243.82) 336.365 ms 336.225 ms 336.532 ms
    17 unknown.telstraglobal.net (202.126.128.26) 336.163 ms 335.709 ms 335.554 ms
    18 10G-ADN-103-11-140-3.solone.net (103.11.140.3) 335.242 ms 334.664 ms 335.173 ms

  • @gbshouse said: 15 103.11.140.3 524.191 ms 525.437 ms 525.110 ms

    God damn Hosrtvirtual has crap connectivity to Asia (even inside Asia itself)

    Thanked by 1klikli
  • gbshousegbshouse Member, Host Rep

    @William - yop, especially from India

  • klikliklikli Member

    @William
    I think their Hongkong location is single-homed with NTT?
    (On iPad now so can't rDNS and I did not read the routes)

  • edited June 2012
    # tracert 103.11.140.3
    
    Tracing route to 10G-ADN-103-11-140-3.solone.net [103.11.140.3]
    over a maximum of 30 hops:
      1    1 ms    1 ms    1 ms  192.168.1.1
      2    39 ms    39 ms    38 ms  xxx.xxx.xxx.xxx
      3    54 ms    39 ms    39 ms  197.subnet125-160-11.speedy.telkom.net.id [125.1
    60.11.197]
      4    39 ms    38 ms    38 ms  61.94.114.109
      5    67 ms    65 ms   109 ms  41.subnet118-98-59.astinet.telkom.net.id [118.98
    .59.41]
      6    64 ms    62 ms    66 ms  42.subnet118-98-59.astinet.telkom.net.id [118.98
    .59.42]
      7    63 ms    66 ms    66 ms  180.240.190.13
      8    71 ms    65 ms    66 ms  if-13-0-1.core1.S9R-Singapore.as6453.net [209.58
    .82.185]
      9    65 ms    66 ms    66 ms  if-0-3-1-0.tcore2.SVW-Singapore.as6453.net [180.
    87.15.33]
     10   260 ms   260 ms   258 ms  180.87.15.218
     11   261 ms   257 ms   257 ms  unknown.telstraglobal.net [202.126.128.26]
     12   259 ms   258 ms   257 ms  10G-ADN-103-11-140-3.solone.net [103.11.140.3]
    
    # ping 103.11.140.3
    
    Pinging 103.11.140.3 with 32 bytes of data:
    Reply from 103.11.140.3: bytes=32 time=259ms TTL=237
    Reply from 103.11.140.3: bytes=32 time=257ms TTL=237
    Reply from 103.11.140.3: bytes=32 time=257ms TTL=237
    Reply from 103.11.140.3: bytes=32 time=258ms TTL=237
    
    Ping statistics for 103.11.140.3:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 257ms, Maximum = 259ms, Average = 257ms
    
    # tracert 124.248.212.94
    
    Tracing route to 124-248-212-94.sunnyvision.com [124.248.212.94]
    over a maximum of 30 hops:
      1     1 ms    1 ms    1 ms  192.168.1.1
      2    40 ms    39 ms    38 ms  xxx.xxx.xxx.xxx
      3    37 ms    39 ms    38 ms  197.subnet125-160-11.speedy.telkom.net.id [125.1
    60.11.197]
      4    37 ms    39 ms    38 ms  61.94.114.109
      5    68 ms    66 ms    67 ms  41.subnet118-98-59.astinet.telkom.net.id [118.98
    .59.41]
      6    63 ms    62 ms    62 ms  42.subnet118-98-59.astinet.telkom.net.id [118.98
    .59.42]
      7    93 ms    97 ms    93 ms  78.190.240.180.telin.sg [180.240.190.78]
      8    99 ms    97 ms    97 ms  sunnyvision2-RGE.hkix.net [202.40.161.79]
      9     *       96 ms   103 ms  in.core-sw-001.gi.gi1.0.25.sunnyvision.com [123.
    242.225.2]
     10    99 ms    97 ms    97 ms  124-248-212-94.sunnyvision.com [124.248.212.94]
    
    Trace complete.
    
    # ping 124.248.212.94
    
    Pinging 124.248.212.94 with 32 bytes of data:
    Reply from 124.248.212.94: bytes=32 time=97ms TTL=55
    Reply from 124.248.212.94: bytes=32 time=97ms TTL=55
    Reply from 124.248.212.94: bytes=32 time=98ms TTL=55
    Reply from 124.248.212.94: bytes=32 time=98ms TTL=55
    
    Ping statistics for 124.248.212.94:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 97ms, Maximum = 98ms, Average = 97ms
    
  • So, what would you pick for now?

    Hongkong or Singapore?
    Need to decide soon.....

  • gbshousegbshouse Member, Host Rep

    Hong Kong, for Singapore you have OneAsiaHost and at least from my point of view it's better to have two good providers in Asia with two different locations

  • nabonabo Member

    @William said: Hongkong

    Hong Kong.

  • AndriAndri Member

    @William said: Hongkong

    Yes. Hongkong.

  • ChanChan Member
    edited June 2012

    @William said: Hongkong

    Yes, not trying to be biased here but Hong Kong has better connection to mainland China (and Japan) and for SG I can easily go for OneAsiaHost or AWS.

  • rds100rds100 Member

    @William choose Ankara ;-) It's in Asia and has good connectivity to Europe.

  • lbftlbft Member
    edited June 2012

    @William said: So, what would you pick for now?

    From my perspective, I'd pick Singapore - SunnyVision has unimpressive connectivity to both mainland China and the rest of the world IMHO; both SunnyVision and OneAsiaHost are worse than the west coast of the US for Australia whereas Sol One is better.

    But then as I said before I'm not really a prospective buyer right now. It's not different enough from the US west coast for me to be able to justify $60 a year for a 128 without a specific need for a specific location, especially given how spotty intra-Asia connectivity can be, even though that's good pricing for the location.

Sign In or Register to comment.