Update : China Telecom also experiencing same problem
KUL - HK Vodafone - US Vodafone - CT CN



TIME to China Unicom is using Singtel route straight away from SG to Guangzhou thats why can reach ping below 100ms and not like TM route to US dulu

Got charge u RM53 or not?
The reason why i lazy to report to TM,is because There is a chance that tm will charge rm53 for technician coming...

btw now tm tech team really action very fast,unlike 5-10 years ago need wait few days to them to assign tech to solve personal issue.

Hope this helps. I have both Unifi and Time. Here are tests from both of them to down.weidown.com.
Note that I'm connecting from my Unifi house to the VPN in my TIME house. A few extra hops there.

weird , last time i traceroute from time to CU is through Singtel then go Guangzhou
below 100ms

Do you have an address for CU that I can try?

v26.douyinvod.com or 219.158.6.86

v26.douyinvod.com or 219.158.6.86

Actually if you really have patience to play around with tm and mcmc.
The problem will be fix and smooth for longer time.
Because few days ago,i search for the similar problem that happens last year about high latency spikes and packet loss to OVH Singapore.
That guy that keep report every 2-3 days to tm and mcmc, finally get contact with tm higher level person and the problem become smaller. (but need patience bcs need few months time to waste with them)

See this link,this guy keep report to tm for forcing TM to fix the problem.
https://amirazman.my/masalah-sambungan-unifi-ke-ovh-hosting/

But of course the problem came back again every night at 9.30-10.30pm for about 5-20min every night.
But I am satisfied for only have short time problem... Better than 2 years ago that time the happens time is very randomly and more serious than now.
This is the OVH smokeping to TM IP by OVH SG DC.


And also u can also report to Amazon Web Services. I don't have service on aws,so cant report..haha
The reason why i suggest to report AWS, is because they are the server provider, they can contact TM to solve the problem easily than us.
They can contact the traffic IX to reduce the problem.

Too many service that hosted on AWS is using US East location,so this is really a big big problem.

https://share.pingplotter.com/4zpEGFL3PhW
Speechless

Lol. Thats mine. Thats why suddenly my post got replied after a few months. Haha.

Yeah last time it happens so much, I cannot bear anymore because I got servers SG and its too near and they have issue to optimize the connection. I have discussed with a few server owner/founder such as ServerFreak about this before.

A few weeks ago, happens within 24 hours, right now I saw it happens everyday but still acceptable.

** At my blogpost, scroll down, read the comments from 'Shah' and guess who is it. Why suddenly a 'normal reader' would comments with quite good details like that ?

When I looked at your post comment,i also think that is a TM internal guy,want to convince you to stop report about the problem, they also don't have the permanent resolution.
But i think if all of us report to TM and MCMC together with really a group of people, this may be change in the future as MCMC get in to force TM to solve the issue.
(As long as TM not expanding the pipe or finding new peering involve, the problem will never be fix...)

I also lazy to report,give out already,Now OVH SG everyday problematic for 5-30min okay lah, just hope the problem not getting serious is enough for us..haha

Ya bro, if happens 1 hour already problematic for us. I think this issue not occurred for a quite long time, more than 6~8 month and suddenly occur again since last month. Maybe in here I can gather all the details and bring this up so that they can take this as a very serious issue.

Last time im quite depressed with this situation though because it seems like im fighting alone for this issue .

1. They didnt take this serious because minimal user having this issue.
2. Got a few people knows about it but cant do much also, because need 'cable' to connect/contact the insiders to settle this.
3. As far as I remember, I tried also with University servers which having a premium network from TM to let them know, even subscribing premium network also will have this issue.

But since I saw some community here also having this issue and realized about it, I think this is good then. We can provide details for them to fix it seriously.

** Thinking about that too. Because I dont think 'normal user' will get attracted with that issue. And he continued to reply for a quite long time though. But he stopped replied after the issue gone. Haha.

Can pm me your OVH SG ip? I will talk to them to reroute to traffic.

Can pm me your OVH SG ip? I will talk to them to reroute to traffic.

OVH Hosting having the issue but it doesnt affect much right now. I could say its quite acceptable.

Smokeping OVH : http://sgp.smokeping.ovh.net/smokeping?target=APAC.AS4788

IP : 139.99.21 || 139.99.65 || 139.99.6 (around this IP range).

But I replied to this because of 'Sam Leong' reply about AWS US issue : https://forum.lowyat.net/topic/5081177/+1320 and seems like hes having a very hard time now.

Will check tomorrow with TM

Will check tomorrow with TM

Please also inform tm to check the us east problem. Already weeks.
AWS East almost 50 percent of time is unable to access or packet loss.
Thanks.

From TM Unifi to AWS East

this 1 need change routing cos TM via Equinix Ashburn only have 10Gbps which already max out.

which i posted earlier.