Singapore Linodes are now available!

April 27, 2015 10:04 am

SingaporeWe’re very excited to announce the opening of our newest datacenter in Singapore! This marks Linode’s seventh datacenter, and is purpose-built to serve the already huge and growing markets in Southeast Asia, India, Australia, and surrounding regions.

We’ve spent the majority of the past few months working on getting great connectivity to the Internet. Our Singapore network is powered by Cisco ASR 9000-series routers, and currently blends transit from Telstra/Pacnet and PCCW, along with direct peering into the Equinix Internet Exchange (EIE) – providing us with access to hundreds of peering opportunities. Check out our Speedtest page to test latency and download speeds.

Singapore supports all of the standard Linode features available in all of our datacenters – like 40 Gbps redundant connectivity to each hypervisor host machine, the Linode Backup service, NodeBalancers, native IPv6, etc – and is the same simple pricing as our other datacenters. Try Singapore now!

We’re also hard at work on other great news. Stay tuned!

Enjoy!

60 Responses

  1. Unfortunately, the RTT to a Singapore linode from Sydney via TPG (fluctuating between 300ms and 400ms with some packet loss) is worse than the RTT to a London linode from Sydney (consistent 320ms).

    There’s also a fluctuating 60ms-160ms RTT between the Singapore linode and its default gateway.

  2. Wow, Its Nice to hear, can’t want to move to my local datacenter.

    Regards,
    Raja.

  3. Great job! You’re the best.

  4. Well done. Still blocked regarding VMs bookings until D/Frankfurt location is missing. We love this service but cannot use yet.

  5. Hi,

    I would like to know which is better from India and China, Tokyo or Singapore?

    Thanks in advance to anyone replying me.

  6. We are going to give it a try with our website soon, hope to get the good response as been discussed here in the post.

    Great Job indeed!

  7. Please direct china telecom please use china telecom CN2 Network

  8. @Garron

    I recommend Singapore from India. Following from Kerala

    PING speedtest.singapore.linode.com (139.162.23.4) 56(84) bytes of data.
    64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=1 ttl=55 time=74.5 ms
    64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=2 ttl=55 time=74.8 ms
    64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=3 ttl=55 time=74.2 ms
    64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=4 ttl=55 time=73.8 ms

  9. I also shifted my linode to Singapore datacenter. Thank you linode for starting Singapore datacenter

  10. Hi, I am no expert, just a user and I love using Linode. But look at what I’ve found! You can’t really take the speedtest server at face value….

    Besides ping, you have to use tracert to see at which nodes are slowing down your linode server in singapore to the internet.

    Here’s what I do:
    1. I shifted my linode to Singapore DC.
    2. Using the one of fastest broadband subscriptions (500mbps) from singapore isp, i ping from my client machine in Singapore to Linode Singapore DC:

    2.1 Pinging speedtest.singapore.linode.com [139.162.23.4] with 32 bytes of data:
    Reply from 139.162.23.4: bytes=32 time=5ms TTL=51
    Reply from 139.162.23.4: bytes=32 time=4ms TTL=51
    Reply from 139.162.23.4: bytes=32 time=4ms TTL=51
    Reply from 139.162.23.4: bytes=32 time=4ms TTL=51

    2.2 Pinging li863-XX.members.linode.com [139.162.2X.XX] with 32 bytes of data:
    Reply from 139.162.2X.XX: bytes=32 time=179ms TTL=46
    Reply from 139.162.2X.XX: bytes=32 time=178ms TTL=46
    Reply from 139.162.2X.XX: bytes=32 time=179ms TTL=48
    Reply from 139.162.2X.XX: bytes=32 time=166ms TTL=48

    WHY there is such a huge difference in time between ping the speedtest Singapore linode server and my actual linode server that is now in Linode Singapore DC?

    At first I thought it might be my OS causing the delay. But I’ve striped my server to its bare to respond very fast to network request. So, here’s what I did: I just do a simple tracert and viola! the answer is there.

    3.1 tracert speedtest.singapore.linode.com
    9 4 ms * 4 ms ip-202-147-32-126.asianetcom.net [202.147.32.126]
    10 83 ms 6 ms 7 ms te0-0-2-0.wr1.sin0.asianetcom.net [61.14.157.109]
    11 9 ms 4 ms * xe-0-1-1.gw1.sin2.pacnet.net [202.147.52.64]
    12 9 ms 4 ms * ip-61-14-147-179.asianetcom.net [61.14.147.179]
    13 10 ms 4 ms * 139.162.0.6
    14 4 ms 4 ms 3 ms speedtest.singapore.linode.com [139.162.23.4]

    3.2 tracert li863-XX.members.linode.com
    9 4 ms * 3 ms ip-202-147-32-126.asianetcom.net [202.147.32.126]
    10 7 ms * 6 ms te0-3-0-3.wr2.sin0.asianetcom.net [61.14.158.42]
    11 4 ms * 4 ms xe0-2-0.gw1.sin2.pacnet.net [202.147.52.66]
    12 190 ms 189 ms 190 ms ip-61-14-147-177.asianetcom.net [61.14.147.177]
    13 4 ms 4 ms * 139.162.0.2
    14 166 ms 178 ms 176 ms li863-XX.members.linode.com

    4. ANALYSIS.
    From the 2 tracert tests, you can see that everything is the same until my 12 hops. ip-61-14-147-179.asianetcom.net to the speedtest server returns a super fast 4ms while ip-61-14-147-177.asianetcom.net to the actual linode returns 190ms. 47 to 48 times slower! Which means even though the Singapore speedtest server and the actual linode server are on Linode Singapore DC, they are placed on different networks (1 fast and the other much slower!). Linode, can you accept that?

    As a user, I felt misled and sad. Assuming my test is right, this is a quality issue and Linode should rectify this with it’s Singapore service provider or network team asap. I hope Linode can rectify this issue soon as this is not the kind of quality we’ve bought into.

    PS: You can buy me tea some time after you have corrected this. :)

    Thanks!

Leave a Reply