Howdy, Stranger!

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


DigitalOcean @ Singapore - Page 3
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.

DigitalOcean @ Singapore

13»

Comments

  • @FtpIt_Radi said:
    If anybody wants my DigitalOcean account with 49.99 credit it's yours for $40.

    Can negotiate the price.

    i'll take it for $10

  • Can't wait! does anyone know of pricing?

  • rm_rm_ IPv6 Advocate, Veteran

    Eobble said: does anyone know of pricing?

    They have 3 geographic locations (NY, SF, AMS) with same prices in all three; also there's an emphasis on simplicity in billing etc. It will be very unlike them to have a different pricing in SG.

  • can't wait for SG launching date. I'll take few VPS there

  • I'm interested to in SG location from DO, hope the price is the same.

  • @rm_ said:
    They have 3 geographic locations (NY, SF, AMS) with same prices in all three; also there's an emphasis on simplicity in billing etc. It will be very unlike them to have a different pricing in SG.

    I hope it's not like SFO where about half the time I go to create a droplet it's either full or there's a DC problem.

  • rm_rm_ IPv6 Advocate, Veteran
    edited January 2014

    They have set up some IP space announcements from their SG AS http://bgp.he.net/AS133165
    103.253.144.1 and 2400:6180::1 respond to ping/trace.
    Don't make any conclusions just yet, it's 100% Telia at the moment, I think they will add at least some 2nd upstream before launch.

  • DO and IPv6? Now we have news.

  • good news and these test IP fast enough for me :)

    DO :

        PING 103.253.144.1 (103.253.144.1) 56(84) bytes of data.
        64 bytes from 103.253.144.1: icmp_seq=1 ttl=53 time=38.8 ms
        64 bytes from 103.253.144.1: icmp_seq=2 ttl=53 time=39.1 ms
        64 bytes from 103.253.144.1: icmp_seq=3 ttl=53 time=38.1 ms
        64 bytes from 103.253.144.1: icmp_seq=4 ttl=53 time=38.4 ms
        64 bytes from 103.253.144.1: icmp_seq=5 ttl=53 time=37.8 ms
        64 bytes from 103.253.144.1: icmp_seq=6 ttl=53 time=37.9 ms
    

    OAH :

        64 bytes from 116.251.208.201: icmp_seq=1 ttl=54 time=38.7 ms
        64 bytes from 116.251.208.201: icmp_seq=2 ttl=54 time=38.1 ms
        64 bytes from 116.251.208.201: icmp_seq=3 ttl=54 time=38.1 ms
        64 bytes from 116.251.208.201: icmp_seq=4 ttl=54 time=38.6 ms
        64 bytes from 116.251.208.201: icmp_seq=5 ttl=54 time=37.3 ms
        64 bytes from 116.251.208.201: icmp_seq=6 ttl=54 time=38.3 ms
    
  • nonubynonuby Member
    edited January 2014

    Routing seem very weak for me at the moment. From SimplerCloud (Singtel) its 255ms as it bounces to San Jose, HK and back to SG, suggesting an absence of local peering (open or not). Also from Thailand its hitting 80ms, which is pretty poor compared to AWS, Softlayer, OAH, and SimplerCloud, generally between 45-60ms.

    As rm_ notes its probably too early to make conclusions, AWS SG had hit and miss routing initially, the more competition in the area the better so I look forward to this (even though SimplerCloud has been near flawless for me)

  • BoltersdriveerBoltersdriveer Member, LIR
    edited January 2014

    nonuby said: Routing seem very weak for me at the moment. From SimplerCloud (Singtel) its 255ms as it bounces to San Jose, HK and back to SG, suggesting an absence of local peering (open or not). Also from Thailand its hitting 80ms, which is pretty poor compared to AWS, Softlayer, OAH, and SimplerCloud, generally between 45-60ms.

    As rm_ notes its probably too early to make conclusions, AWS SG had hit and miss routing initially, the more competition in the area the better so I look forward to this (even though SimplerCloud has been near flawless for me)

    Yep, seems like they have quite little local peering at the moment. I expect this would improve quite soon though. A few traceroutes from various providers:

    ViewQwest [18106]:

    1 192.168.1.1 (192.168.1.1) [*] 1.161 ms 1.284 ms 1.531 ms
    2 fnet254-f36-access.vqbn.com.sg (202.73.36.254) [AS18106] 9.069 ms 9.069 ms 9.267 ms
    3 202.73.37.230 (202.73.37.230) [AS18106] 9.280 ms 9.499 ms 9.549 ms
    4 ge-11-3-0.singapore2.sin.seabone.net (213.144.176.44) [AS6762] 9.541 ms 9.577 ms 9.579 ms
    5 ge2-0-0.singapore1.sin.seabone.net (213.144.176.49) [AS6762] 9.724 ms ge6-0-0.singapore1.sin.seabone.net (213.144.176.64) [AS6762] 9.769 ms 9.769 ms
    6 telia.singapore1.sin.seabone.net (213.144.176.78) [AS6762] 253.410 ms 199.968 ms 198.784 ms
    7 aire-ic-305221-mad-b2.c.telia.net (62.115.40.170) [AS1299] 187.283 ms 187.746 ms 188.522 ms
    8 103.253.144.1 (103.253.144.1) [AS133165] 210.383 ms 211.174 ms 211.580 ms

    MyRepublic [132047]:

    1 router.asus.com (192.168.0.1) [] 0.236 ms 0.575 ms 0.673 ms
    2 172.17.0.1 (172.17.0.1) [
    ] 4.399 ms 4.480 ms 4.501 ms
    3 10GE-103-6-148-29.myrepublic.com.sg (103.6.148.29) [AS132132] 5.387 ms 5.294 ms 5.406 ms
    4 snge-b1-link.telia.net (213.248.72.21) [AS1299] 17.580 ms 17.388 ms 17.594 ms
    5 aire-ic-305221-mad-b2.c.telia.net (62.115.40.170) [AS1299] 7.423 ms 7.451 ms 7.992 ms
    6 103.253.144.1 (103.253.144.1) [AS133165] 7.266 ms 5.228 ms 4.782 ms

    HostSG (OAH) [24482]:

    1 116.251.223.241 (116.251.223.241) [AS24482] 0.019 ms 0.009 ms 0.009 ms
    2 edge-1.v33.ntp.sg.gs (203.175.175.33) [AS24482] 0.454 ms 0.527 ms edge-1.v34.ntp.sg.gs (203.175.175.49) [AS24482] 0.628 ms
    3 edge-2.v42.eqix.sg.gs (203.175.175.141) [AS24482] 0.619 ms 0.616 ms 0.612 ms
    4 27.50.33.81 (27.50.33.81) [*] 0.686 ms 0.671 ms 0.769 ms
    5 10ge6-1.core1.hkg1.he.net (184.105.223.189) [AS46841] 34.467 ms 34.609 ms 34.548 ms
    6 10ge3-1.core1.tyo1.he.net (184.105.222.105) [AS46841] 91.910 ms 85.454 ms 85.469 ms
    7 10ge15-2.core1.lax2.he.net (184.105.223.105) [AS46841] 173.946 ms 195.667 ms 195.692 ms
    8 las-b3-link.telia.net (213.248.101.29) [AS1299] 182.891 ms 182.881 ms 182.891 ms
    9 las-bb1-link.telia.net (213.155.134.76) [AS1299] 170.467 ms las-bb1-link.telia.net (213.155.131.82) [AS1299] 171.149 ms las-bb1-link.telia.net (213.155.134.76) [AS1299] 170.450 ms
    10 hnk-b2-link.telia.net (213.155.136.45) [AS1299] 198.756 ms 198.748 ms hnk-b2-link.telia.net (213.155.132.214) [AS1299] 195.897 ms
    11 snge-b1-link.telia.net (213.155.136.119) [AS1299] 198.773 ms 198.767 ms snge-b1-link.telia.net (80.91.245.148) [AS1299] 195.778 ms
    12 aire-ic-305221-mad-b2.c.telia.net (62.115.40.170) [AS1299] 200.415 ms 184.350 ms 184.222 ms
    13 103.253.144.1 (103.253.144.1) [AS133165] 196.451 ms 197.033 ms 200.076 ms

  • PremiumHostPremiumHost Member
    edited January 2014

    Ping from Softlayer Singapore

    PING 103.253.144.1 (103.253.144.1) 56(84) bytes of data.
    64 bytes from 103.253.144.1: icmp_seq=1 ttl=51 time=349 ms
    64 bytes from 103.253.144.1: icmp_seq=2 ttl=51 time=350 ms
    64 bytes from 103.253.144.1: icmp_seq=3 ttl=51 time=349 ms
    64 bytes from 103.253.144.1: icmp_seq=4 ttl=51 time=360 ms
    64 bytes from 103.253.144.1: icmp_seq=5 ttl=51 time=354 ms
    ^C
    --- 103.253.144.1 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4991ms
    rtt min/avg/max/mdev = 349.177/352.735/360.783/4.455 ms
  • Not all the peering is in yet, waiting on some capacity upgrades to get the rest installed. Also telia was having some big issues in the area on the dates you were all testing.

  • @nunim said:
    I hope it's not like SFO where about half the time I go to create a droplet it's either full or there's a DC problem.

    It's getting updated this week, should be a thing of the past for sfo1 very soon.

  • From Philippines:

     3  119.93.255.205 (119.93.255.205)  20.926 ms  20.994 ms  24.496 ms
     4  210.213.130.114.static.pldt.net (210.213.130.114)  24.616 ms 210.213.130.118.static.pldt.net (210.213.130.118)  26.272 ms 210.213.130.114.static.pldt.net (210.213.130.114)  26.868 ms
     5  210.213.130.137.static.pldt.net (210.213.130.137)  26.136 ms 210.213.130.141.static.pldt.net (210.213.130.141)  26.297 ms 210.213.130.137.static.pldt.net (210.213.130.137)  26.638 ms
     6  snge-b1-link.telia.net (62.115.40.37)  74.938 ms  78.269 ms  78.145 ms
     7  aire-ic-305221-mad-b2.c.telia.net (62.115.40.170)  67.347 ms  66.097 ms  66.171 ms
     8  103.253.144.1 (103.253.144.1)  69.615 ms  69.595 ms  70.227 ms
    
  • some more peering came up, not all still but curious to see some more numbers. overall better but need to fix up some horrible over telia default bgp choices.

  • rm_rm_ IPv6 Advocate, Veteran
    edited January 2014

    Yep I see NTT got added! And also for those wondering, a support rep in a ticket confirmed the pricing will be the same as in all other datacenters.

  • when will be launched exatly?

  • @add_iT said:
    when will be launched exatly?

    that's above my paygrade. shouldn't be much longer.

  • They claimed will launched the services within Jan 2014 and they're added NTT too.

  • rm_rm_ IPv6 Advocate, Veteran

    Netxons said: They claimed will launched the services within Jan 2014

    They also claimed they will add IPv6 in September 2013.

    Thanked by 1rds100
  • I assume they'll delay the Singapore too then

  • @Netxons said:
    I assume they'll delay the Singapore too then

    Seems like it unless they announce it within a couple hours.

  • @Setsura said:
    Seems like it unless they announce it within a couple hours.

    I guess not.

  • Lame.

  • Nice..

  • RU location from DO would be interesting

    Thanked by 1k0nsl
  • Any update yet?

  • Singapore, yay!

Sign In or Register to comment.