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
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

rm_rm_ IPv6 Advocate, Veteran
edited September 2011 in General

http://blog.linode.com/2011/09/19/linode-cloud-asia-pacific/

Perhaps not LEB-grade prices, but from what I see for Asia and general and for Japan especially, this is a superb deal. Also - first the MountSpot offer, now this - maybe something is changing to the better with DC and bandwidth prices in that part of the world.

«1

Comments

  • O-M-F-G

    I am about to try one xD....

  • Sounds like a good alternative to those providing services to the Far East Asia. I wonder what the latency would be like for those from Asia Pacific.

    Would that also reduce the demand for US West Coast servers? Not until there's a low end provider there I guess :)

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    Linode is still only providing 200G bandwidth, that's not a whole lot even by LEB standards :)

    Francisco

  • Francisco said: Linode is still only providing 200G bandwidth, that's not a whole lot even by LEB standards :)

    I'm surprised an average user would even need that much. 100GB used to be "alot" for a VPS a few years ago.

  • Last month I used ~150gb on my main VPS, but I used it a VPN to it almost full time. This month I'm around 80gb without any VPN use. (TBH I don't know why it's so high)

  • Ping from Vietnam is around 180ms, not too much faster than West Coast based providers. (average 200ms, Quadranet is around 19xms)

  • MrAndroidMrAndroid Member
    edited September 2011

    Ping is very inconstant from Western Europe.

    Daniel-Smiths-MacBook-Pro:~ Daniel$ ping tokyo1.linode.com
    PING tokyo1.linode.com (106.187.33.12): 56 data bytes
    64 bytes from 106.187.33.12: icmp_seq=0 ttl=47 time=684.932 ms
    64 bytes from 106.187.33.12: icmp_seq=1 ttl=47 time=282.743 ms
    64 bytes from 106.187.33.12: icmp_seq=2 ttl=47 time=524.371 ms
    64 bytes from 106.187.33.12: icmp_seq=3 ttl=47 time=445.252 ms
    64 bytes from 106.187.33.12: icmp_seq=4 ttl=47 time=672.464 ms
    64 bytes from 106.187.33.12: icmp_seq=5 ttl=47 time=594.233 ms
    64 bytes from 106.187.33.12: icmp_seq=6 ttl=47 time=513.164 ms
    ^C
    --- tokyo1.linode.com ping statistics ---
    7 packets transmitted, 7 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 282.743/531.023/684.932/129.312 ms
    Daniel-Smiths-MacBook-Pro:~ Daniel$ 
    

    One thing would worry me if I had a server there, Earthquake.

  • @Francisco said: Linode is still only providing 200G bandwidth, that's not a whole lot even by LEB standards

    Ha. My BuyVM VPS has 1TB/month data, but just then it says I've used 12TB this month! 200GB/month from Linode would definitely not be enough. </sarcasm>

    @Daniel said: One thing would worry me if I had a server there, Earthquake.

    That's indeed a concern. However with earthquake in Tokyo -- there will be a lot more things to worry about than my damn $20/month VPS. On the other hand, what's the likelihood of earthquake on the other side of Pacific ring of fire, affecting all those LA, Fremont and San Jose data centers?

  • LowEndAdmin said: That's indeed a concern. However with earthquake in Tokyo -- there will be a lot more things to worry about than my damn $20/month VPS. On the other hand, what's the likelihood of earthquake on the other side of Pacific ring of fire, affecting all those LA, Fremont and San Jose data centers?

    Well, Japans tectonic activity is probably much higher, it has 3 fault lines going right through it,

    I do remember doing a case study on a LA & Kobe Earthquake, I believe that from earthquake alone then it wouldn't effect the DCs, but a tsunami would.

  • LowEndAdmin said: Ha. My BuyVM VPS has 1TB/month data, but just then it says I've used 12TB this month!

    Yeah same happenned to me. Anthony said me that they are doing some experiments :P

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    Not quite expirements, more I was upgrading the backend accounting code and franned it real good :P With the amount of VM's we have, BW accounting is the most brutal part of the whole system. The original Solus version (that stallion was emulating) was doing 8 SQL updates per VPS IP during updates.

    The new edition is doing 1 update per IP as well as a lot of other merged counters to cut down on queries.

    I'm sad that I had to reset everyones bandwidth but I'm happy that it's all running like it should and running perfectly now, including ipv6 BW accounting.

    Francisco

  • @Francisco Any reason why I have 500TB bandwidth?

  • maxexcloomaxexcloo Member
    edited September 2011

    Ping from Sydney, Australia:

    [max@Orion ~]$ 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=52 time=442 ms
    64 bytes from tokyo1.linode.com (106.187.33.12): icmp_req=2 ttl=52 time=430 ms
    64 bytes from tokyo1.linode.com (106.187.33.12): icmp_req=3 ttl=52 time=447 ms
    --- tokyo1.linode.com ping statistics ---
    4 packets transmitted, 3 received, 25% packet loss, time 2999ms
    rtt min/avg/max/mdev = 430.656/440.170/447.854/7.180 ms
    

    Traceroute:

    [max@Orion ~]$ traceroute tokyo1.linode.com
    traceroute to tokyo1.linode.com (106.187.33.12), 30 hops max, 52 byte packets
     1  192.168.1.1 (192.168.1.1)  2.572 ms  0.637 ms  0.606 ms
     2  sbr801.ba.optusnet.com.au (198.142.128.118)  42.559 ms  21.815 ms  22.189 ms
     3  sbr4-ge7-1.gw.optusnet.com.au (198.142.144.221)  21.605 ms  25.751 ms  22.348 ms
     4  sbr2-ge5-0.gw.optusnet.com.au (211.29.125.253)  22.439 ms  21.875 ms  22.823 ms
     5  203.208.131.113 (203.208.131.113)  178.082 ms  178.248 ms  185.717 ms
     6  203.208.182.105 (203.208.182.105)  178.874 ms 203.208.171.161 (203.208.171.161)  181.334 ms POS3-6.sngtp-ar2.ix.singtel.com (203.208.182.213)  200.708 ms
     7  203.208.171.105 (203.208.171.105)  261.785 ms 203.208.171.109 (203.208.171.109)  233.273 ms ge-4-0-0-0.plapx-cr3.ix.singtel.com (203.208.183.174)  179.316 ms
     8  so-2-0-1-0.sngtp-cr1.ix.singtel.com (203.208.151.89)  358.426 ms ge-2-1-0-0.sngtp-dr1.ix.singtel.com (203.208.183.62)  381.733 ms 203.208.152.218 (203.208.152.218)  442.858 ms
     9  ae0-0.sngtp-cr2.ix.singtel.com (203.208.183.58)  380.963 ms so-6-0-0-0.sngc3-ar4.ix.singtel.com (203.208.152.29)  367.287 ms  361.588 ms
    10  ge-1-1-0-0.sngc3-ar3.ix.singtel.com (203.208.172.118)  364.887 ms ge-1-0-0-0.sngc3-ar3.ix.singtel.com (203.208.172.162)  385.458 ms  358.585 ms
    11  59.128.15.141 (59.128.15.141)  482.355 ms 203.208.153.109 (203.208.153.109)  370.983 ms 203.181.102.165 (203.181.102.165)  534.868 ms
    12  otejbb204.kddnet.ad.jp (118.155.197.2)  449.783 ms  583.036 ms  453.288 ms
    13  203.208.145.54 (203.208.145.54)  439.381 ms cm-fcu203.kddnet.ad.jp (124.215.194.180)  436.541 ms 203.181.102.165 (203.181.102.165)  447.966 ms
    14  124.215.199.122 (124.215.199.122)  471.184 ms otejbb204.kddnet.ad.jp (118.155.197.2)  449.740 ms  451.991 ms
    15  cm-fcu203.kddnet.ad.jp (124.215.194.180)  423.475 ms tokyo1.linode.com (106.187.33.12)  465.582 ms cm-fcu203.kddnet.ad.jp (124.215.194.180)  446.132 ms
    
  • I wouldn't worry about earthquakes in Japan affecting the DC as a whole - yes they have a lot of earthquakes there but they are the most prepared nation when it comes to earthquakes. I wonder however do earthquakes affect disk failure rates in disk arrays?

  • my own BuyVM/SanJose

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 214ms, Maximum = 226ms, Average = 221ms

    Linode Tokyo

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 122ms, Maximum = 142ms, Average = 132ms

    .... Worth a try!

  • Daniel said: 64 bytes from 106.187.33.12: icmp_seq=4 ttl=47 time=672.464 ms

    64 bytes from 106.187.33.12: icmp_seq=5 ttl=47 time=594.233 ms
    64 bytes from 106.187.33.12: icmp_seq=6 ttl=47 time=513.164 ms

    That looks like a routing issue...looks like the route goes over to New York--> California --> Tokyo rather through than a physically shorter route through Eastern Europe --> Asia --> Tokyo

  • rm_rm_ IPv6 Advocate, Veteran
    edited September 2011

    @TigersWay @kiloserve
    your posted pings are utterly useless if you don't mention where you are pinging FROM!

  • eLohkCalbeLohkCalb Member
    edited September 2011

    Superb deal for the entire Asia Pacific? I don't think so.

    For what I can see, traceroute seems to suggest that it's direct link from Singapore to Japan (via KDDI), however the ping time to tokyo1.linode.com is 1.5x the time to fremont1.linode.com, and the download speed from tokyo1 is half the speed compared to fremont1.

  • Solid ping to Cali

    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_seq=1 ttl=51 time=132 ms
    64 bytes from tokyo1.linode.com (106.187.33.12): icmp_seq=2 ttl=51 time=132 ms
    64 bytes from tokyo1.linode.com (106.187.33.12): icmp_seq=3 ttl=51 time=132 ms
    64 bytes from tokyo1.linode.com (106.187.33.12): icmp_seq=4 ttl=51 time=132 ms
    
  • BoltersdriveerBoltersdriveer Member, LIR
    edited September 2011

    Being from Singapore, here are my results:

    Pinging tokyo1.linode.com [106.187.33.12] with 32 bytes of data:
    Reply from 106.187.33.12: bytes=32 time=98ms TTL=55
    Reply from 106.187.33.12: bytes=32 time=97ms TTL=55
    Reply from 106.187.33.12: bytes=32 time=100ms TTL=55
    Reply from 106.187.33.12: bytes=32 time=98ms TTL=55
    Reply from 106.187.33.12: bytes=32 time=98ms TTL=55
    
  • ZiggaZigga Member
    edited September 2011

    Another traceroute from downunder

      1     1 ms    <1 ms     4 ms  home.loco.net [192.168.1.1]
      2    14 ms    22 ms    12 ms  nme-sot-dry-bras1-lo-20.tpgi.com.au [10.20.20.187]
      3    13 ms    13 ms    12 ms  nme-sot-dry-csw1-te-4-3.tpgi.com.au [203.12.162.249]
      4    13 ms    13 ms    13 ms  nme-sot-dry-crt2-ge-7-0-0.tpgi.com.au [202.7.162.41]
      5    24 ms    24 ms    23 ms  syd-sot-ken-crt2-ge-3-0-0.tpgi.com.au [202.7.162.177]
      6   122 ms   123 ms   122 ms  ix-11-1-0-507.tcore2.TV2-Tokyo.as6453.net[116.0.88.21]
      7   122 ms   122 ms   124 ms  if-14-0-0-1720.core1.TV2-Tokyo.as6453.net [209.58.61.121]
      8   128 ms   124 ms   142 ms  Vlan10.ihar1.OVC-Tokyo.as6453.net [209.58.61.158]
      9   122 ms   122 ms   123 ms  118.155.194.61
     10   129 ms   123 ms   123 ms  otejbb204.kddnet.ad.jp [118.155.197.130]
     11   129 ms   125 ms   125 ms  cm-fcu203.kddnet.ad.jp [124.215.194.180]
     12   124 ms   127 ms   125 ms  124.215.199.122
     13   125 ms   125 ms   124 ms  tokyo1.linode.com [106.187.33.12]
    

    That traceroute from Optus looks horrible!

  • eLohkCalbeLohkCalb Member
    edited September 2011

    @Boltersdriveer

    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.

  • kiloservekiloserve Member
    edited September 2011

    rm_ said: @kiloserve your posted pings are utterly useless if you don't mention where you are pinging FROM!

    Please check the post. Those weren't my pings, it was from Daniel in Western Europe.

  • rm_ said: @TigersWay @kiloserve your posted pings are utterly useless if you don't mention where you are pinging FROM!

    You skipped your breakfast?

    If you have no idea where I was pinging from, then you never read any of my post... But it does not really matters as my point was to show some could easily get a benefit.

  • rm_rm_ IPv6 Advocate, Veteran

    @TigersWay when posting useful technical information never make the crucial bit of it rely on people knowing you, or knowing where are you from via your other posts, etc ;)
    What about someone who e.g. arrives here from googling something.

  • @maxexcloo @Zigga -- indeed Optus route is totally crap. I found going through TPG would get pretty good ping (~120ms) whereas going through MCI/Verizon is not as good (~180ms). Didn't know Optus/Singtel is this bad. Looks like it's going to US West Coast, then Hong Kong and then Tokyo...

  • This sounded exciting... Until I checked the routing.

    PING tokyo1.linode.com (106.187.33.12): 56 data bytes
    64 bytes from 106.187.33.12: seq=0 ttl=48 time=189.927 ms
    64 bytes from 106.187.33.12: seq=1 ttl=48 time=190.266 ms
    64 bytes from 106.187.33.12: seq=2 ttl=48 time=190.419 ms
    
     2  119.93.254.241 (119.93.254.241)  15.670 ms  15.020 ms  14.664 ms
     3  210.213.131.38.static.pldt.net (210.213.131.38)  15.972 ms  16.647 ms  16.403 ms
     4  210.213.128.50.static.pldt.net (210.213.128.50)  16.461 ms  15.516 ms  16.673 ms
     5  210.213.129.21.static.pldt.net (210.213.129.21)  16.947 ms  15.995 ms  26.497 ms
     6  210.213.128.33.static.pldt.net (210.213.128.33)  36.660 ms  15.545 ms  17.393 ms
     7  210.213.130.9.static.pldt.net (210.213.130.9)  14.819 ms  15.773 ms  15.662 ms
     8  59.128.15.54 (59.128.15.54)  188.678 ms  187.979 ms  188.627 ms
     9  otejbb203.kddnet.ad.jp (118.155.197.1)  182.265 ms  220.219 ms  181.769 ms
    10  cm-fcu203.kddnet.ad.jp (124.215.194.164)  191.355 ms  187.813 ms  183.629 ms
    11  124.215.199.122 (124.215.199.122)  191.130 ms  192.675 ms  *
    12  tokyo1.linode.com (106.187.33.12)  190.177 ms  191.925 ms  191.823 ms
    

    That's 190ms from the Philippines to Japan. It's only 170ms to their Fremont server.

    PING fremont1.linode.com (64.71.152.17): 56 data bytes
    64 bytes from 64.71.152.17: seq=0 ttl=55 time=173.970 ms
    64 bytes from 64.71.152.17: seq=1 ttl=55 time=173.733 ms
    64 bytes from 64.71.152.17: seq=2 ttl=55 time=173.686 ms
    
  • LowEndAdmin said: going through MCI/Verizon is not as good (~180ms). Didn't know Optus/Singtel is this bad. Looks like it's going to US West Coast, then Hong Kong and then Tokyo...

    going through the au isps looks like tpg has the best connectivity. even node is doing 132ms(from melb) and they have a pop in Japan!

  • rm_rm_ IPv6 Advocate, Veteran
    edited September 2011

    @david reverse traceroute could contain the answer, perhaps it goes via USA on the path back to you. But to obtain such a trace you will need to run it on a machine on the other end, and target your own IP. Usually scripts called LG (looking glass) are installed for such purpose by hosters and DCs, but I dunno if Linode has one in Japan or at all.

  • 6MB/sec to the UK (RapidSwitch) and only 10 hops.

     2  62-233-127-181.as20860.net (62.233.127.181)  1.135 ms  1.145 ms  1.269 ms
     3  ae0-135.lon25.ip4.tinet.net (77.67.74.225)  1.088 ms  1.075 ms  1.061 ms
     4  xe-0-3-0.nyc20.ip4.tinet.net (89.149.186.209)  73.978 ms xe-2-3-0.nyc20.ip4.tinet.net (89.149.187.109)  111.187 ms xe-0-3-0.nyc20.ip4.tinet.net (89.149.186.209)  73.951 ms
     5  tr-ny5.kddnet.ad.jp (213.200.66.14)  82.397 ms  82.390 ms  82.447 ms
     6  lajbb001.kddnet.ad.jp (59.128.3.57)  136.531 ms lajbb002.kddnet.ad.jp (59.128.3.61)  136.786 ms  136.583 ms
     7  otejbb204.kddnet.ad.jp (203.181.100.21)  239.015 ms  240.815 ms otejbb203.kddnet.ad.jp (203.181.100.9)  253.043 ms
     8  cm-fcu203.kddnet.ad.jp (124.215.194.164)  246.812 ms cm-fcu203.kddnet.ad.jp (124.215.194.180)  246.512 ms  244.334 ms
     9  124.215.199.122 (124.215.199.122)  244.327 ms  243.244 ms  241.182 ms
    10  tokyo1.linode.com (106.187.33.12)  242.071 ms  241.891 ms  239.905 ms
    

    4.5MB/sec to .SE

    Considerably worse (think tens or hundreds of KB/sec) to .nl and .de.

Sign In or Register to comment.