Howdy, Stranger!

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


Linode opens DC in Tokyo - Page 2
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.

Linode opens DC in Tokyo

2»

Comments

  • I have a pretty weird traceroute, it gets to the East Coast of the US, then zips all the way to Japan on what appears to be one hop.

    Daniel-Smiths-MacBook-Pro:~ Daniel$ traceroute tokyo1.linode.com
    traceroute to tokyo1.linode.com (106.187.33.12), 64 hops max, 52 byte packets
     1  my.router (192.168.1.1)  42.043 ms  0.834 ms  0.620 ms
     2  217.47.93.250 (217.47.93.250)  29.792 ms  28.636 ms  48.859 ms
     3  217.47.93.193 (217.47.93.193)  40.734 ms  28.184 ms  28.551 ms
     4  213.1.69.86 (213.1.69.86)  29.230 ms  28.601 ms  28.470 ms
     5  81.147.49.49 (81.147.49.49)  28.106 ms  27.963 ms  27.685 ms
     6  213.120.176.14 (213.120.176.14)  29.788 ms  28.287 ms  28.078 ms
     7  213.120.176.178 (213.120.176.178)  27.945 ms  28.014 ms  28.541 ms
     8  acc1-10gige-0-2-0-7.l-far.21cn-ipp.bt.net (109.159.249.103)  28.553 ms
        acc1-10gige-0-0-0-5.l-far.21cn-ipp.bt.net (109.159.249.78)  28.747 ms
        acc1-10gige-0-7-0-4.l-far.21cn-ipp.bt.net (109.159.249.74)  28.259 ms
     9  core1-te0-11-5-0.ealing.ukcore.bt.net (109.159.249.5)  33.151 ms
        core1-te0-4-0-6.ealing.ukcore.bt.net (109.159.249.1)  32.279 ms
        core1-te0-0-0-13.ealing.ukcore.bt.net (109.159.249.33)  34.140 ms
    10  transit1-xe0-0-0.ealing.ukcore.bt.net (62.6.200.106)  28.952 ms  32.762 ms  28.919 ms
    11  t2c3-xe-9-1-0.uk-eal.eu.bt.net (166.49.168.21)  28.883 ms  28.514 ms  28.990 ms
    12  t2c1-ge6-1.uk-glo.eu.bt.net (166.49.237.17)  29.657 ms  28.459 ms  28.906 ms
    13  t2c1-p4-0-0.us-ash.eu.bt.net (166.49.164.225)  104.950 ms  105.454 ms  105.807 ms
    14  166-49-151-134.eu.bt.net (166.49.151.134)  114.317 ms  114.480 ms  114.052 ms
    15  * * *
    16  63.146.26.70 (63.146.26.70)  186.738 ms  183.876 ms  182.959 ms
    17  lajbb001.kddnet.ad.jp (59.128.2.173)  185.556 ms
        lajbb001.kddnet.ad.jp (59.128.2.69)  182.501 ms
        lajbb002.kddnet.ad.jp (59.128.2.73)  177.840 ms
    18  otejbb203.kddnet.ad.jp (203.181.100.9)  316.350 ms
        otejbb204.kddnet.ad.jp (203.181.100.45)  323.620 ms
        otejbb203.kddnet.ad.jp (203.181.100.9)  322.444 ms
    19  cm-fcu203.kddnet.ad.jp (124.215.194.180)  322.535 ms
        cm-fcu203.kddnet.ad.jp (124.215.194.164)  321.972 ms
        cm-fcu203.kddnet.ad.jp (124.215.194.180)  378.484 ms
    20  124.215.199.122 (124.215.199.122)  304.449 ms  490.455 ms  674.075 ms
    21  tokyo1.linode.com (106.187.33.12)  489.493 ms  282.350 ms  769.201 ms
    Daniel-Smiths-MacBook-Pro:~ Daniel$ 
    
  • 21 stops seems rather high in number as well.

  • user@COMPAQ:~$ ping tokyo1.linode.com
    PING tokyo1.linode.com (106.187.33.12) 56(84) bytes of data.
    64 bytes from tokyo1.linode.com (106.187.33.12): icmp_req=1 ttl=53 time=369 ms
    64 bytes from tokyo1.linode.com (106.187.33.12): icmp_req=2 ttl=53 time=359 ms
    64 bytes from tokyo1.linode.com (106.187.33.12): icmp_req=3 ttl=53 time=358 ms
    64 bytes from tokyo1.linode.com (106.187.33.12): icmp_req=4 ttl=53 time=366 ms
    ^C
    --- tokyo1.linode.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3002ms
    rtt min/avg/max/mdev = 358.239/363.464/369.180/4.707 ms
    user@COMPAQ:~$ traceroute tokyo1.linode.com
    traceroute to tokyo1.linode.com (106.187.33.12), 30 hops max, 60 byte packets
     1  10.64.193.101 (10.64.193.101)  59.641 ms  80.810 ms  80.784 ms
     2  139.97.22.194 (139.97.22.194)  182.223 ms  181.900 ms  181.870 ms
     3  ae2.heltli-gw1.fi.elisa.net (139.97.6.246)  129.414 ms  129.392 ms  129.358 ms
     4  ae1-10.bbr2.hel1.fi.eunetip.net (213.192.191.49)  139.236 ms  139.206 ms  181.976 ms
     5  ae1-0.bbr1.sto4.se.eunetip.net (213.192.184.46)  181.944 ms  181.915 ms  181.883 ms
     6  xe-0-1-0-xcr1.skt.cw.net (166.63.221.193)  181.847 ms  111.343 ms  69.667 ms
     7  xe-7-0-0-xcr1.amd.cw.net (195.2.25.89)  261.300 ms  261.246 ms  301.589 ms
     8  xe-0-2-0-xcr1.lsw.cw.net (195.2.25.105)  301.330 ms xe-4-1-0-xcr1.bru.cw.net (195.2.25.254)  301.461 ms  311.236 ms
     9  xe-4-0-0-xcr1.lnd.cw.net (195.2.25.30)  301.568 ms xe-0-1-0-xcr2.bru.cw.net (195.2.25.234)  311.108 ms xe-4-0-0-xcr1.lnd.cw.net (195.2.25.30)  311.221 ms
    10  ge-11-0-0-xcr1.nyk.cw.net (195.2.25.18)  311.161 ms  330.764 ms so-7-0-0-dcr2.bru.cw.net (195.2.9.206)  339.056 ms
    11  xe-7-3-0-xcr1.ash.cw.net (195.2.21.138)  330.659 ms xe-11-1-0-xcr1.prp.cw.net (195.2.9.190)  338.931 ms xe-7-3-0-xcr1.ash.cw.net (195.2.21.138)  330.456 ms
    12  xe-7-1-0-xcr1.ash.cw.net (195.2.25.193)  269.872 ms xe-3-2-0-xcr1.lax.cw.net (195.2.28.50)  221.114 ms xe-7-1-0-xcr1.ash.cw.net (195.2.25.193)  229.206 ms
    13  ae0-ecr1.lax.cw.net (195.2.10.14)  238.548 ms  238.250 ms  247.900 ms
    14  ae0-ecr1.lax.cw.net (195.2.10.14)  247.844 ms  247.782 ms peering.kddi.com (198.32.146.36)  257.646 ms
    15  peering.kddi.com (198.32.146.36)  257.591 ms  267.783 ms lajbb001.kddnet.ad.jp (59.128.2.157)  267.515 ms
    16  lajbb002.kddnet.ad.jp (59.128.2.161)  267.661 ms otejbb203.kddnet.ad.jp (203.181.100.13)  387.390 ms lajbb001.kddnet.ad.jp (59.128.2.157)  277.169 ms
    17  otejbb203.kddnet.ad.jp (203.181.100.13)  387.274 ms cm-fcu203.kddnet.ad.jp (124.215.194.180)  406.995 ms  349.410 ms
    18  124.215.199.122 (124.215.199.122)  349.300 ms  349.638 ms  349.527 ms
    19  tokyo1.linode.com (106.187.33.12)  359.859 ms  379.419 ms 124.215.199.122 (124.215.199.122)  389.222 ms
  • From North Carolina, on the East Coast of the US :)

      1     1 ms     1 ms     1 ms  192.168.2.1
      2     9 ms     9 ms     9 ms  h1.31.82.166.dynamic.ip.windstream.net [166.82.31.1]
      3     9 ms     9 ms     9 ms  t9-3.cr01.cncr.ctc.net [166.82.3.13]
      4     8 ms     9 ms     9 ms  h194.6.82.166.static.ip.windstream.net [166.82.6.194]
      5    11 ms    11 ms    11 ms  h57.224.190.173.ip.windstream.net [173.190.224.57]
      6    11 ms    11 ms     9 ms  h20.207.190.173.static.ip.windstream.net [173.190.207.20]
      7    14 ms    15 ms    15 ms  h106.254.213.151.static.ip.windstream.net [151.213.254.106]
      8    15 ms    15 ms    15 ms  h9.254.213.151.static.ip.windstream.net [151.213.254.9]
      9    14 ms    25 ms    15 ms  xe-4-3-2.edge5.Atlanta2.Level3.net [4.59.12.53]
     10    34 ms    15 ms    15 ms  vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]
     11    14 ms    15 ms    66 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
     12    35 ms    35 ms    35 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
     13    66 ms    66 ms    66 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
     14    68 ms    68 ms    66 ms  ae-82-82.csw3.LosAngeles1.Level3.net [4.69.137.26]
     15    65 ms    92 ms    66 ms  ae-3-80.edge2.LosAngeles9.Level3.net [4.69.144.143]
     16   180 ms    68 ms   181 ms  otejbb203.kddnet.ad.jp [203.181.100.13]
     17    65 ms   190 ms   182 ms  cm-fcu203.kddnet.ad.jp [124.215.194.164]
     18   179 ms   181 ms   181 ms  otejbb203.kddnet.ad.jp [203.181.100.13]
     19   192 ms   182 ms   192 ms  cm-fcu203.kddnet.ad.jp [124.215.194.164]
     20   181 ms   182 ms   183 ms  124.215.199.122
     21   183 ms   182 ms   182 ms  tokyo1.linode.com [106.187.33.12]
    
  • WintereiseWintereise Member
    edited September 2011

    Not a bad deal for us in Japan, I guess.

    I haven't a clue how to do the code boxes, so I'll post the traceroute on pastebin instead.

    http://pastebin.com/8CxhZyfe

    Trace is from Nagano, Japan.

    Still, single homed to KDDI isn't my idea of the best Japanese transit. A blend of IIJ, NTT and KDDI is more practical (or, if they're feeling generous, throw in ODN(softbank corp.) Telecom as well).

    @Daniel:

    The lajbb hops are in Los Angeles :p

    And, @david PLDT has horrible routes, I wouldn't blame KDDI for that one.

  • eLohkCalb said: I can't seem to get <100ms with Singnet, however I'm able to get that if I were to do it directly from M1 DC, but that defeats the purpose IMHO.


    @eLohkCalb @LowEndAdmin SingNet (SingTel) sucks. Go for either M1 or a StarHub DC.

  • BoltersdriveerBoltersdriveer Member, LIR
    edited September 2011

    Anyway, here is my traceroute (StarHub Singapore again) :

    1 10 ms 7 ms 7 ms cm1.iota117.maxonline.com.sg [116.89.117.1]

    2 8 ms 11 ms 7 ms 172.20.52.33

    3 9 ms 11 ms 12 ms 172.26.52.1

    4 13 ms 10 ms 23 ms 172.20.7.86

    5 11 ms 11 ms 11 ms 172.20.7.42

    6 22 ms 11 ms 13 ms 203.117.35.237

    7 14 ms 26 ms 15 ms 203.117.34.6

    8 12 ms 15 ms 25 ms 203.117.34.13

    9 13 ms 15 ms 20 ms 203.117.34.1

    10 119 ms 106 ms 107 ms 118.155.194.173

    11 98 ms 135 ms 116 ms otejbb204.kddnet.ad.jp [59.128.7.130]

    12 98 ms 104 ms 107 ms cm-fcu203.kddnet.ad.jp [124.215.194.180]

    13 101 ms 98 ms 99 ms 124.215.199.122

    14 97 ms 101 ms 98 ms tokyo1.linode.com [106.187.33.12]

    By the way, can someone point me in how to format my posts for not requiring (br) for every line?

  • kylixkylix Member
    edited September 2011

    You could use Markdown. At least it works for me in here.

  • @Wintereise put it between pre tags. Better than having to jump through hoops and use a non standard method like Markdown. :P

  • Boltersdriveer said: SingNet (SingTel) sucks. Go for either M1 or a StarHub DC.

    Well, don't be surprised that there are places in SG where you can't use anything other than Singnet. :)

  • @eLohkCalb: Not really :P . I prefer M1 as an alternative.

  • Ping from PLDT Philippines

    Reply from 106.187.33.12: bytes=32 time=103ms TTL=52
    Reply from 106.187.33.12: bytes=32 time=105ms TTL=52
    Reply from 106.187.33.12: bytes=32 time=104ms TTL=52
    Reply from 106.187.33.12: bytes=32 time=104ms TTL=52
    

    Pretty decent. Lowest ping I've ever seen from DCs outside Philippines.

  • I guess that the server market in Asia is about to open up. Just after this, SoftLayer will be starting to take orders for servers in Singapore ( near Jurong East district ). It should be interesting to see how more providers start to pop up for the Asia-Pacific region.

  • http://digitalswift.net/?l=en&n=vpsplans seems to be good price (1,680 Yen/$22 per month) with unlimited bandwidth

    but...

    Can I use the VPS for inbound line mainly like proxy server?/Are there any restriction(s) in using VPS? †
    This service is suitable to use such as web server (except Ultimate2 plan), and not suitable to use inbound for proxy server. In addition, please refrain from using VPS following purposes. Currently, the following uses are not allowed on our VPS (except for Ultimate2 plan). If you use inbound more than outbound at PLANS except at Ultimate2 PLAN, we may restrict bandwidth speed of your VPS without advance notice.
    Torrent
    P2P
    IRC
    Proxies
    VPN
    
  • flyahflyah Member
    edited September 2011

    From Manila, Philippines on PLDT Pinging tokyo1.linode.com [106.187.33.12] with 32 bytes of data: Reply from 106.187.33.12: bytes=32 time=105ms TTL=52 Reply from 106.187.33.12: bytes=32 time=108ms TTL=52 Reply from 106.187.33.12: bytes=32 time=110ms TTL=52 Reply from 106.187.33.12: bytes=32 time=112ms TTL=52 Ping statistics for 106.187.33.12: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 105ms, Maximum = 112ms, Average = 108ms _____ Tracing route to tokyo1.linode.com [106.187.33.12] over a maximum of 30 hops: 1

Sign In or Register to comment.