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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
show us a traceroute?
NTT Singapore congestion.
It's definitely drowning since yesterday - last night was close to 400ms from SG to SG, and today simply just packet losses.
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..
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.1Interestingly 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).
Do you really think this is "another" problem?
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.
i think its stable now , although hop is a bit longer this time.
opps there it goes again. sigh. i think ill have to sleep this one again.
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
@aolee, that is OAH not DO isn't it?
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..
@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:
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.
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!
Pings come from OVH Network ;-)
yes, DigitalOcean server SGP1 now Maintance
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.
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.
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.