Seems like the issue is “resolved” now
Oracle change NTT to Tata
but i guess just because now morning the traffic is reduced maybe ?
Lets see tomorrow how


Or maybe its cloudflare side optimisations
https://www.cloudflarestatus.com/incidents/591h9b09wjhm

This post has been edited by Sam Leong: Dec 26 2021, 07:52 AM

unifi Alert still is ongoing but they removed the ETTR haha. Now you know you cannot fix submarine cable fault in a few hours. Probably interns doing the updates lol

more likely oracle ingress traffic still using NTT. the ping still 170++

NTT has divert HK traffic to JPY but still unable cope the huge traffic flow.

TM has changed most route over He.net using SG link.

latency has stabilize so far... need wait till tonight peak hours to test again.

Usually it's a matter of days, but for us, thanks to Minister Weebotage, it'll probably be weeks/months.

at least the speed is back around 100Mbps + when i test to my server
yesterday the speed reaches 0.09 mbps with a 1000ms+ ping



from JP osaka - TIME
https://www.speedtest.net/result/c/8c36dd90...24-27ae51396736

This post has been edited by Sam Leong: Dec 26 2021, 12:05 PM

normal for NTT cos they depend single cable to HKG or JPY

once cable fault.. then.... BOOM

lucky now hurricane electric got different back up cable.. otherwise same as NTT

Hope TM sufficient with 2 HE.net SG link (both at 100G)

hope so... wait tonight see how it goes...

TM always get overloaded with HE.net SG before,so dont keep big hope on it.

I still cannot access to Sucuri based websites, got a connection reset error on browser.

some loss packet 10-20% over US west using He.net via SG starting at 7:30pm

This post has been edited by heLL_bOy: Dec 26 2021, 08:03 PM

HKG/JP also loss packet... oh my

Connection to Japan totally packet loss for awhile.


Traceroute from my JP vps:
traceroute to 147.158.255.254 (147.158.255.254), 30 hops max, 60 byte packets
1 tokyoVPS (41.216.180.X) 0.053 ms 0.014 ms 0.011 ms
2 180.149.230.X (180.149.230.X) 0.162 ms 0.209 ms 0.214 ms
3 180.149.230.255 (180.149.230.255) 0.447 ms 0.557 ms 0.636 ms
4 unn-138-199-1-194.cdn77.com (138.199.1.194) 0.182 ms 0.238 ms 0.244 ms
5 vl250.tyo-eq8-core-1.cdn77.com (138.199.0.216) 0.206 ms 0.220 ms 0.249 ms
6 tky-b1-link.ip.twelve99.net (62.115.189.145) 0.244 ms 0.227 ms 0.247 ms
7 * * *
8 snge-b5-link.ip.twelve99.net (62.115.142.86) 138.229 ms 138.241 ms *
9 * * *
10 * * *
11 147.158.255.254 (147.158.255.254) 146.314 ms 146.333 ms 146.348 ms

(JP Pingable to MY,but MY ping to JP not working)


This post has been edited by go626201: Dec 26 2021, 09:17 PM

When this show up in their alert page, we shall feel the slowness.

lol Telia also gone case

i think all the TM link over are congested or rate limit

Quite normal la... TM unifi route with Telia congestion problem already few years.
Few years ago,TM using Telia route to US,and half of the time also having alot of packet loss.

I think there might also be having some internal congestion issue within TM network.

This post has been edited by go626201: Dec 26 2021, 09:23 PM

previously i got one US server using Telia back to TM via SG no loss packet issue even peak hours.

sad .. we duno when it will be fixed right?

With this climate typhoon and all I don't think the cables will be fixed in a these few days.