Howdy, Stranger!

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


Digital Ocean Singapore drowning?
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.

Digital Ocean Singapore drowning?

Last night and again now (as i type). DO - Singapore, experiencing High Latency? Sigh... How to develop at times like this. doesn't seem like developer friendly VPS. Hope they can solve it asap.

Comments

  • blackblack Member

    show us a traceroute?

  • NTT Singapore congestion.

  • eLohkCalbeLohkCalb Member
    edited March 2014

    It's definitely drowning since yesterday - last night was close to 400ms from SG to SG, and today simply just packet losses.

    3   208 ms   160 ms   163 ms  202.166.119.97
    4    21 ms    54 ms    31 ms  xe-2-0-0-3600.tp-ar09.singnet.com.sg [202.166.124.149]
    5    84 ms    23 ms    23 ms  xe-1-1-0.singha.singnet.com.sg [202.166.122.253]
    6    60 ms    23 ms    27 ms  ae5-0.beck.singnet.com.sg [202.166.126.41]
    7    39 ms    78 ms    24 ms  203.208.190.57
    8    27 ms    32 ms   139 ms  ge-2-0-0-0.nycec-cr1.ix.singtel.com [203.208.151.217]
    9    75 ms    58 ms    54 ms  so-3-0-1-0.hkgcw-cr3.ix.singtel.com [203.208.151.82]
    10    57 ms    70 ms    60 ms  203.208.171.53
    11    57 ms    60 ms    53 ms  203.208.152.6
    12    57 ms    60 ms    57 ms  203.208.152.194
    13    57 ms    60 ms    58 ms  as-0.r21.tkokhk01.hk.bb.gin.ntt.net [129.250.6.124]
    14    57 ms    56 ms    60 ms  as-0.r21.tkokhk01.hk.bb.gin.ntt.net [129.250.6.124]
    15   124 ms    59 ms   107 ms  as-7.r21.sngpsi02.sg.bb.gin.ntt.net [129.250.6.9]
    16     *      295 ms   137 ms  ae-7.r20.sngpsi05.sg.bb.gin.ntt.net [129.250.6.46]
    17   100 ms    95 ms    97 ms  ae-7.r20.sngpsi05.sg.bb.gin.ntt.net [129.250.6.46]
    18   114 ms   156 ms    97 ms  ae-4.r21.sngpsi02.sg.bb.gin.ntt.net [129.250.3.183]
    19     *        *        *     Request timed out.
    20     *        *        *     Request timed out.
    
  • They are aware about this situation, and they still investigating.
    btw, I got another problem. my server are slow. typing in ssh are little bit lagging. and reboot take about 10minutes to complete..

  • rm_rm_ IPv6 Advocate, Veteran
    edited March 2014

    Ping 2x from the normal, 70-80% packet loss over NTT:

    to DO
     Host                                   Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. hosted-by.i3d.net                    0.0%    71    7.6  10.0   0.2 111.1  20.4
     2. 80ge.cr0-br2-br3.smartdc.rtd.i3d.ne  0.0%    71    0.2   4.9   0.2  45.0   8.6
     3. xe-0-2-0-10.r02.amstnl02.nl.bb.gin.  0.0%    70    1.5   1.7   1.4   4.9   0.5
     4. ae-2.r22.amstnl02.nl.bb.gin.ntt.net  0.0%    70    1.4   4.6   1.3  60.9   9.7
     5. as-2.r22.tokyjp01.jp.bb.gin.ntt.net  0.0%    70  222.4 252.3 222.2 350.2  31.3
        as-0.r25.tokyjp05.jp.bb.gin.ntt.net
     6. ae-6.r22.tokyjp01.jp.bb.gin.ntt.net  0.0%    70  287.8 279.2 263.3 326.7  13.4
        as-6.r21.sngpsi02.sg.bb.gin.ntt.net
     7. as-1.r21.sngpsi02.sg.bb.gin.ntt.net  1.4%    70  283.8 308.3 280.1 347.3  25.0
        ae-4.r20.sngpsi02.sg.bb.gin.ntt.net
     8. ae-1.r00.sngpsi02.sg.bb.gin.ntt.net  0.0%    70  328.3 312.2 282.0 344.7  25.4
        ae-6.r00.sngpsi02.sg.bb.gin.ntt.net
     9. 116.51.27.150                       71.0%    70  394.5 340.2 292.1 394.6  41.3
    10. 103.253.144.242                     63.8%    70  293.2 331.7 291.2 395.1  42.8
    11. xxxxxxxxxxxxxxxxx                   79.7%    70  288.2 322.1 286.5 394.5  46.1
    
    from DO
     Host                                   Loss%   Snt   Last   Avg  Best  Wrst StDev
     1. 128.199.255.254                      0.0%    37    0.4   0.6   0.4   3.8   0.5
     2. 103.253.144.237                      0.0%    37    0.5   2.3   0.4  57.6   9.4
     3. 103.253.144.249                      0.0%    37    2.1   1.5   0.3  24.6   4.0
     4. 116.51.27.149                       97.2%    37   53.9  53.9  53.9  53.9   0.0
     5. ae-1.r21.sngpsi02.sg.bb.gin.ntt.net 61.1%    37    5.9  42.9   5.9  68.0  23.8
        129.250.4.142
     6. as-6.r23.tokyjp01.jp.bb.gin.ntt.net 77.1%    36  139.1  89.2  71.5 139.1  28.3
        as-0.r24.tokyjp05.jp.bb.gin.ntt.net
     7. ae-9.r25.tokyjp05.jp.bb.gin.ntt.net 65.7%    36  123.5  98.4  70.9 123.5  24.6
        ae-1.r25.tokyjp05.jp.bb.gin.ntt.net
     8. 129.250.3.78                        82.9%    36  389.2 358.4 285.8 401.3  53.6
     9. ae-1.r02.amstnl02.nl.bb.gin.ntt.net 80.0%    36  287.4 291.3 287.2 301.8   5.0
    10. i3d.r02.amstnl02.nl.ce.gin.ntt.net  45.7%    36  382.7 390.0 382.7 399.8   5.1
    11. 188.122.95.93                       79.4%    35  337.5 339.1 331.4 347.5   5.6
    12. xxxxxxxxxxxxxxxx                    68.6%    35  302.2 324.2 288.0 403.7  41.1
    

    Interestingly HE.net have also disabled their direct Paris <> Singapore route, now it goes around the world. However local peering of DO SG to HE.net is nto affected, hence if you had a HE.net IPv6 tunnel set up on your droplet, it should be accessible perfectly over IPv6 with lower ping and zero packet loss (that's how I am able to take the 2nd trace).

  • rm_rm_ IPv6 Advocate, Veteran
    edited March 2014

    psycholyzern said: I got another problem. my server are slow. typing in ssh are little bit lagging.

    Do you really think this is "another" problem?

    and reboot take about 10minutes to complete..

    That's because their panel runs in the US and has to communicate with the actual SG servers over the same congested/problematic/lossy network link, maybe this fails or it just takes longer.

  • aoleeaolee Member
    edited March 2014

    i think its stable now , although hop is a bit longer this time.

  • aoleeaolee Member

    opps there it goes again. sigh. i think ill have to sleep this one again.

  • @rm_ said:
    That's because their panel runs in the US and has to communicate with the actual SG servers over the same congested/problematic/lossy network link, maybe this fails or it just takes longer.

    ohh.. so it's all about their network. sorry, newbie is here :)
    btw, I started to realise this situation yesterday. hope they can fix it fast. I am using it for openvpn, because it has low latency to my location :)

  • eLohkCalbeLohkCalb Member
    edited March 2014

    @aolee, that is OAH not DO isn't it?

    Thanked by 1aolee
  • aoleeaolee Member

    lol yah sorry wrong server , that was my OAH server.

  • Singtel refuse to peer locally hence the silly NTT let's meet half way in HK. The only solution for DO in this regard is to purchase SingTel transit, which I believe they currently are. This along with Equinix perering and transit from NTT, Telia and TATA (next week) make it a pretty damn good solution. Patience..

    Thanked by 1aolee
  • rm_rm_ IPv6 Advocate, Veteran

    @nonuby I'm sorry sir but I am not sure wtf are you going on about, or to be more precise, how your tirade even has anything at all to do with the situation at hand:

  • eLohkCalbeLohkCalb Member
    edited March 2014

    nonuby said: Equinix perering

    Their Equinix peering is in HK. I doubt that's going to help anything at all.

    And so far I have not seen Singtel transit as their upstream, hopefully it's like what you said: soon-to-add.

  • aoleeaolee Member

    @eLohkCalb said:
    And so far I have not seen Singtel transit as their upstream, hopefully it's like what you said: soon-to-add.

    Crossing my fingers on this one! hope this soon-to-add transit wont jack up the pricing, as you all know, everything is expensive in Singapore!

  • d0wnd0wn Member

    Pings come from OVH Network ;-)

  • yes, DigitalOcean server SGP1 now Maintance

  • nonubynonuby Member
    edited March 2014

    @eLohkCalb said:
    Their Equinix peering is in HK

    DigitialOcean definitely have peering now in Equinix SG (common to see p133165.sgw.equinix.com in traceroute) . E.g. peering with CAT IG, 1-Net etc..

    Im pretty confident that their network will eventually turn out to pretty stellar, these are the initial rough few weeks.

    This was ~2 weeks ago:

    We're talking to singtel about better local connectivity.

    Thanks,
    Bryan

  • Sg seems fine to me.

  • rm_ said: @nonuby I'm sorry sir but I am not sure wtf are you going on about, or to be more precise, how your tirade even has anything at all to do with the situation at hand:

    It had everything to do with the situation at hand, if you want to try re-reading it.

    Makes sense to people used to asshattery from Singtel / Starhub in the Singapore market.

  • nonuby said: DigitialOcean definitely have peering now in Equinix SG (common to see p133165.sgw.equinix.com in traceroute) . E.g. peering with CAT IG, 1-Net etc..

    Do you have the full traceroute result?

  • eLohkCalb said: Do you have the full traceroute result?

    DO has been on the Singapore Equinix Exchange for around a month if not more now.

    Try tracing to any providers who are also available on the Equinix RR, and you'll see traffic being routed appropriately.

    Traceroute shows DO's path selection to CAT (TH)'s L2 transport circuit into Equinix SG.

    
    traceroute to www.cattelecom.com (202.47.243.36), 30 hops max, 60 byte packets
     1  128.199.255.253 (128.199.255.253)  0.345 ms  0.674 ms  0.591 ms
     2  103.253.144.241 (103.253.144.241)  0.499 ms  0.487 ms  0.439 ms
     3  103.253.144.250 (103.253.144.250)  0.408 ms  0.639 ms  0.593 ms
     4  9931.sgw.equinix.com (202.79.197.104)  31.177 ms  31.187 ms  31.147 ms
     5  202.47.247.101 (202.47.247.101)  31.559 ms 202.47.247.97 (202.47.247.97)  31.501 ms  31.441 ms
     6  202.47.247.70 (202.47.247.70)  31.999 ms 202.47.247.62 (202.47.247.62)  31.391 ms  31.323 ms
     7  202.47.236.227 (202.47.236.227)  32.841 ms 202.47.236.195 (202.47.236.195)  35.410 ms 202.47.236.227 (202.47.236.227)  32.783 ms
     8  122.155.128.106 (122.155.128.106)  31.601 ms  32.010 ms  31.713 ms
     9  202.6.107.225 (202.6.107.225)  31.238 ms  31.396 ms  31.345 ms
    
    
    Thanked by 1eLohkCalb
Sign In or Register to comment.