DigitalOcean to add Singapore Region by the end of January

[joshuatly]

Hey guys,

Wanted to give everyone an update that we have started work on our latest region which will be Singapore to service Asia.

We’ve already signed for the DC space and are working on the logistics of shipping equipment to the new region.

There have been a couple of delays on some of the equipment arriving so it’s pushed back our timeline a bit, but we hope to have the new region opened by the end of January.

We’re very excited about this new region that we are adding and hope you guys are as well!

Thanks!

http://digitalocean.uservoice.com/forums/136585-digital-ocean/suggestions/4038460-hong-kong-and-japan-datacenters

 

[drmike]

Very interesting!

DO is pretty nice, so more locations from them are very welcomed from my end.

I am wondering how their network is going to be or if it will end up with tons of long haul to US West Coast and high times for much of Asia which seems to be oh so common?

 

[HalfEatenPie]

Dang! Now I can finally add that 60 USD I got for free to use!

 

[Shados]

Now if only they can wizard real hard and open up an Australian region at their normal prices... Yeah, not going to happen.

 

[nunim]

Very interesting! DO is pretty nice, so more locations from them are very welcomed from my end. I am wondering how their network is going to be or if it will end up with tons of long haul to US West Coast and high times for much of Asia which seems to be oh so common?

Peering seems to be shitty in Asia, but I'm still looking forward to using up some credits, I hope there isn't going to be a premium price attached to SG.

 

[rds100]

Peering seems to be shitty in Asia

I always wondered about this. Bandwidth prices are still high in Asia, and peering could help lower the average bandwidth costs for ISPs. And Singapore is such a small territory - it doesn't seem hard at all to have fiber pairs and peering between each two providers with presence there. It seems they don't peer on purpose, not because they can't.

 

[Kris]

Bandwidth pricing (premium) such as China Telecom / Unicom is very pricey. Unless you have a blend of both, NTT or PCCW for good measure, a connection to the HKIX and a backup such as Pacnet, you won't get great routes at all. Speed or latency wise. Route optimization is crucial, and many times has to be done ISP by ISP to get under optimal speeds and latency under 100ms from Mainland China. 

Not exactly a replacement for China mainland users, but Singapore is good for India (~50ms) Malaysia, HK residents, and even NZ and some Australia traffic (around 100ms latency)

http://www.verizonenterprise.com/au/about/network/latency/

Will be interesting to see what BW blend they choose. 

 

[wlanboy]

Hopefully without any addon price for the location.

 

[josephb]

Bandwidth pricing (premium) such as China Telecom / Unicom is very pricey. Unless you have a blend of both, NTT or PCCW for good measure, a connection to the HKIX and a backup such as Pacnet, you won't get great routes at all. Speed or latency wise. Route optimization is crucial, and many times has to be done ISP by ISP to get under optimal speeds and latency under 100ms from Mainland China. 

Chinese carriers often run massively congested transit and peering links, this results is varying performance depending on the time of day/year/source/destination.

Asia is a massive place, as you've said it needs careful route optimisation, far more so than other geographies.

 

[Tux]

Bandwidth pricing (premium) such as China Telecom / Unicom is very pricey. Unless you have a blend of both, NTT or PCCW for good measure, a connection to the HKIX and a backup such as Pacnet, you won't get great routes at all. Speed or latency wise. Route optimization is crucial, and many times has to be done ISP by ISP to get under optimal speeds and latency under 100ms from Mainland China. 

Not exactly a replacement for China mainland users, but Singapore is good for India (~50ms) Malaysia, HK residents, and even NZ and some Australia traffic (around 100ms latency)

http://www.verizonenterprise.com/au/about/network/latency/

Will be interesting to see what BW blend they choose.

From their previous deployments it's likely going to have Telia and NTT.

 

[DomainBop]

From their previous deployments it's likely going to have Telia and NTT.

Nothing announced yet but here's the AS for Singapore

http://bgp.he.net/AS133165

I posted this link on LET to a VentureBeat interview with DO.  They're up to 6,350 physical servers.

http://venturebeat.com/2013/12/24/digitaloceans-cloud-surpasses-amazon-web-services-in-one-category/

 

[josephb]

Nothing announced yet but here's the AS for Singapore

http://bgp.he.net/AS133165

A /22 is now being announced under that AS, currently only has Telia as the upstream.

Hopefully that changes as Telia isn't exactly optimal as least for Australia, not sure how well connected they are around Asia.

Given DO use NTT in other places, hopefully they'll add NTT or similar in for Singapore.

 

[sv01]

Good News

There has been a response to your ticket:

Hello, The pricing will be the same as all our other data centers. The new Singapore data center is currently undergoing internal testing and we have not yet announced a final date as it is dependent on the testing all being completed successfully so we can ensure that everything operates as expected when launched.

 

[DomainBop]

Good News

Semi-good news.  It looks like they're still single homed to TeliaSonera. http://lg.telia.net/ .  and a lot of the tracroutes I tried from TS Singapore to other Asian locations are going through Los Angeles.  An extreme example is below: TeliaSonera Singapore  to HongKong 364ms vs OneAsiaHost's 36ms to HK

TeliaSonera Singapore to Edis Hong Kong


traceroute to hk.edis.at (158.255.208.12), 30 hops max, 40 byte packets
1 hnk-b2-link.telia.net (80.91.245.149) 34.070 ms hnk-b2-link.telia.net (80.91.245.151) 39.270 ms 52.097 ms
2 las-bb1-link.telia.net (213.155.136.44) 198.216 ms las-bb1-link.telia.net (213.155.134.194) 190.922 ms las-bb1-link.telia.net (213.155.132.215) 195.139 ms
3 te0-7-0-29.ccr23.lax05.atlas.cogentco.com (154.54.10.9) 188.030 ms 200.376 ms 204.040 ms
4 be2181.mpd21.lax01.atlas.cogentco.com (154.54.41.113) [AS 174] 195.987 ms be2179.ccr22.lax01.atlas.cogentco.com (154.54.41.81) [AS 174] 182.854 ms be2181.mpd21.lax01.atlas.cogentco.com (154.54.41.113) [AS 174] 195.865 ms
5 be2161.ccr22.sjc01.atlas.cogentco.com (154.54.27.170) [AS 174] 220.231 ms be2163.ccr22.sjc01.atlas.cogentco.com (154.54.27.238) [AS 174] 216.592 ms 210.941 ms
6 be2047.ccr21.sjc03.atlas.cogentco.com (154.54.5.114) [AS 174] 220.332 ms 216.448 ms be2000.ccr21.sjc03.atlas.cogentco.com (154.54.6.106) [AS 174] 198.132 ms
7 38.104.138.46 (38.104.138.46) [AS 174] 197.849 ms 210.288 ms 211.056 ms
8 te0-3-0-0.wr2.osa0.asianetcom.net (202.147.50.198) [AS 10026] 367.423 ms ip-61-14-158-46.asianetcom.net (61.14.158.46) [AS 10026] 372.229 ms te0-3-0-0.wr2.osa0.asianetcom.net (202.147.50.198) [AS 10026] 373.813 ms
MPLS Label=16046 CoS=0 TTL=255 S=1
9 ge-2-2-0-0.cr4.hkg3.asianetcom.net (61.14.157.106) [AS 10026] 377.818 ms te0-0-0-0.wr2.hkg0.asianetcom.net (61.14.157.6) [AS 10026] 367.172 ms ge-2-2-0-0.cr4.hkg3.asianetcom.net (61.14.157.106) [AS 10026] 352.881 ms
10 ge-2-2-0-0.cr4.hkg3.asianetcom.net (61.14.157.106) [AS 10026] 375.630 ms ge-1-1-0-0.gw4.hkg3.asianetcom.net (203.192.134.70) [AS 10026] 375.125 ms ge-2-2-0-0.cr4.hkg3.asianetcom.net (61.14.157.106) [AS 10026] 365.055 ms
11 HVI-0001.gw4.hkg3.asianetcom.net (61.14.134.97) [AS 10026] 383.467 ms ge-1-1-0-0.gw4.hkg3.asianetcom.net (203.192.134.70) [AS 10026] 353.009 ms HVI-0001.gw4.hkg3.asianetcom.net (61.14.134.97) [AS 10026] 377.520 ms
12 HVI-0001.gw4.hkg3.asianetcom.net (61.14.134.97) [AS 10026] 368.394 ms 205.147.104.249 (205.147.104.249) [AS 36236] 366.066 ms HVI-0001.gw4.hkg3.asianetcom.net (61.14.134.97) [AS 10026] 355.184 ms
13 205.147.104.254 (205.147.104.254) [AS 36236] 389.305 ms 205.147.104.249 (205.147.104.249) [AS 36236] 397.458 ms 205.147.104.254 (205.147.104.254) [AS 36236] 352.815 ms
14 205.147.104.254 (205.147.104.254) [AS 36236] 372.239 ms * 364.906 ms
One AsiaHost (http://www.oneasiahost.com/lg/) to Edis Hong Kong

traceroute to hk.edis.at (158.255.208.12) from 116.251.209.255, 30 hops max, 40 byte packets
 1  edge-1.v34.ntp.sg.gs (203.175.175.49)  1.590 ms  1.667 ms edge-1.v33.ntp.sg.gs (203.175.175.33)  1.158 ms
 2  63-216-152-185.static.pccwglobal.net (63.216.152.185) [AS  3491]  3.536 ms  2.021 ms  1.411 ms
 3  TenGE11-2.br01.sin02.pccwbtn.net (63.218.228.65) [AS  3491]  6.864 ms  2.722 ms  2.149 ms
 4  p10026.sgw.equinix.com (202.79.197.20) [AS  3491]  5.209 ms  3.255 ms  3.487 ms
 5  te0-1-2-0.wr2.sin0.asianetcom.net (61.14.157.169) [AS  3491]  8.872 ms  10.277 ms  9.046 ms
 6  te0-1-0-0.wr2.hkg0.asianetcom.net (61.14.157.9) [AS  3491]  34.950 ms  36.268 ms  46.752 ms
     MPLS Label=16098 CoS=0 TTL=255 S=1
 7  gi15-0-0.gw5.hkg3.asianetcom.net (61.14.157.138) [AS  3491]  34.148 ms  35.085 ms  34.232 ms
 8  ge-0-1-0-0.gw4.hkg3.asianetcom.net (203.192.134.66) [AS  3491]  34.450 ms  34.594 ms  39.786 ms
 9  HVI-0001.gw4.hkg3.asianetcom.net (61.14.134.97) [AS  3491]  35.693 ms  35.721 ms  35.253 ms
10  205.147.104.249 (205.147.104.249) [AS  3491]  35.704 ms  35.410 ms  39.834 ms
11  205.147.104.254 (205.147.104.254) [AS  3491]  36.534 ms  36.249 ms  36.663 ms

 

[josephb]

Semi-good news.  It looks like they're still single homed to TeliaSonera. http://lg.telia.net/ .  and a lot of the tracroutes I tried from TS Singapore to other Asian locations are going through Los Angeles.  An extreme example is below: TeliaSonera Singapore  to HongKong 364ms vs OneAsiaHost's 36ms to HK

Yeah definitely still single homed.

Unfortunately just about all Australian ISPs seem to haul to the US to connect to Telia, so latency is double just getting to West Coast of US.

Hopefully some connectivity with NTT or Asian peering comes online which should make a difference.

 

[shovenose]

Wow, DigitalOcean is going crazy with locations. Wouldn't it make sense to grow out existing locations first?

 

[sv01]

Yeah definitely still single homed.

Unfortunately just about all Australian ISPs seem to haul to the US to connect to Telia, so latency is double just getting to West Coast of US.

Hopefully some connectivity with NTT or Asian peering comes online which should make a difference.

http://bgp.he.net/AS133165


they just add another peer : NTT America

 

[DomainBop]

http://bgp.he.net/AS133165


they just add another peer : NTT America

Better than Telia, but traceroutes to Hong Kong at least are still going through the US.  194ms Singapore to HK compared to 364ms for Telia and only 36ms for OneAsiaHost which goes direct.

traceroute to hk.edis.at (158.255.208.12), 30 hops max, 40 byte packets
 1  ae-3.r20.sngpsi05.sg.bb.gin.ntt.net (129.250.3.182)  0.689 ms  3.930 ms  0.734 ms
     MPLS Label=486689 CoS=0 TTL=1 S=0
     MPLS Label=367472 CoS=0 TTL=1 S=1
 2  ae-3.r20.snjsca04.us.bb.gin.ntt.net (129.250.3.48)  171.448 ms  180.133 ms  187.286 ms
     MPLS Label=367472 CoS=0 TTL=1 S=1
 3  ae-1.r07.snjsca04.us.bb.gin.ntt.net (129.250.5.53)  172.363 ms  192.088 ms  182.508 ms
 4  te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85)  180.969 ms te0-4-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.10.49)  172.437 ms te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85)  172.222 ms
 5  38.104.138.46 (38.104.138.46) [AS  174]  173.125 ms  171.629 ms  174.602 ms
 6  ip-61-14-158-46.asianetcom.net (61.14.158.46) [AS  10026]  235.700 ms te0-3-0-0.wr2.osa0.asianetcom.net (202.147.50.198) [AS  10026]  229.636 ms ip-61-14-158-46.asianetcom.net (61.14.158.46) [AS  10026]  226.885 ms
     MPLS Label=16046 CoS=0 TTL=255 S=1
 7  te0-0-0-0.wr2.hkg0.asianetcom.net (61.14.157.6) [AS  10026]  216.890 ms gi15-0-0.gw5.hkg3.asianetcom.net (61.14.157.138) [AS  10026]  226.925 ms te0-0-0-0.wr2.hkg0.asianetcom.net (61.14.157.6) [AS  10026]  222.885 ms
 8  ge-0-1-0-0.gw4.hkg3.asianetcom.net (203.192.134.66) [AS  10026]  232.028 ms gi15-0-0.gw5.hkg3.asianetcom.net (61.14.157.138) [AS  10026]  215.671 ms ge-0-1-0-0.gw4.hkg3.asianetcom.net (203.192.134.66) [AS  10026]  221.730 ms
 9  ge-0-1-0-0.gw4.hkg3.asianetcom.net (203.192.134.66) [AS  10026]  219.557 ms HVI-0001.gw4.hkg3.asianetcom.net (61.14.134.97) [AS  10026]  194.417 ms ge-0-1-0-0.gw4.hkg3.asianetcom.net (203.192.134.66) [AS  10026]  225.747 ms
10  205.147.104.249 (205.147.104.249) [AS  36236]  188.635 ms HVI-0001.gw4.hkg3.asianetcom.net (61.14.134.97) [AS  10026]  192.013 ms 205.147.104.249 (205.147.104.249) [AS  36236]  187.403 ms
11  205.147.104.249 (205.147.104.249) [AS  36236]  194.273 ms 205.147.104.254 (205.147.104.254) [AS  36236]  193.213 ms 205.147.104.249 (205.147.104.249) [AS  36236]  197.418 ms
12  * 205.147.104.254 (205.147.104.254) [AS  36236]  192.603 ms *

 

[josephb]

Some traceroutes from various AU ISPs http://pastebin.com/KSHnEfxK

I'd say mostly speaking SFO is still a better option for AU.

As per a comment earlier in the thread, Asia is hard from a connectivity point of view, it's a big place with lots of challenges.

 

[accident]

I'd be interested in australian test ips.   we're not done adding peering yet and I could arrange some better for australia ones.   Not in time for opening but not long after.