That is also one of the methods but I'm prefer more to IPvFoo, more visualize.

Ya, but unless you keep monitoring the network, simple is enough for newbie ma.

Thanks, its 45.113.128.155 - getting to *.hkg01.abs.hls.ttvnw.net

This post has been edited by Chiggah: Jun 9 2021, 11:18 PM

Ya, guess twitch fast(?) enough and reroute new users to HK server, after detecting new Malaysia user stutter too much.

Patent should know what to do now.

This one?



This post has been edited by The.Lucas.DaY: Jun 9 2021, 11:27 PM

The blinking is where your streaming origin from.
According to your image, it's from HK server (*.hkg01.abs.hls.ttvnw.net)

Ok, that's smooth in 1080p

Just tried rewatching the video again without VPN just now, and it now plays smoothly. Forgot to capture the IP address back then the first time I watched it.

Lol. Who edit this ? Thats why I got weird traffic to my blogpost.

https://en.wikipedia.org/wiki/Internet_in_Malaysia



This post has been edited by hostingmalaya: Jun 10 2021, 08:06 AM

Nice edit lol to the editors

Memang betul pun wiki edit tu. Masalah routing ni dari zaman Jaring masih wujud lagi. Dulu2 masa takda lagi CDN provider apa semua, kita bandingkan koneksi ke LA atau San Francisco sebab banyak servers kat sana. Bandingkan dengan Jaring punya routing. Tapi, sampai la sekarang TM ni masih bebal bab international routing ni. Bertahun2 punya isu ni sebenarnya. Di sebabkan pandemik dengan kerja dirumah ni ramai sekarang sedar betapa teruknya TM punya kualiti dan routing ni.

This edit is the most accurate thing regarding this issue. Good job to the editors as well as your detailed issue blog post!

This edit accurately shows the bad connectivity for TM. All traffic routing destinated to Malaysia(for Cloudflare or any other CDN) in Malaysia should be, at best effort, confined to Kuala Lumpur (MyIX) and Johor Bahru (JBIX) only.
Especially for traffic destinated to Southern Malaysia/Johor, it should be on JBIX only and not even routing to MyIX or SGIX, let along Osaka or Hong Kong. I had see the other ISPs (4G) routing to KL or SG on my location in JB.

Routing to Singapore is fine (many other ISPs in Malaysia do this) and I had see Celcom routing some of their Cloudflare traffic to Bangkok but however not optimal, since there are more preferable internet exchanges.
Routing to Hong Kong or Osaka, however, is absolutely crazy and disgrace, with frequent loadings for some streaming sites.

This is not to mention that TM already has some traffic congestion and routing issues even before MCO 1.0 (I remembered seeing Hong Kong for Cloudflare CDN while the server is down), which this can be easily solved by taking just 1% of their very huge profits for it + optimal settings for routing.

This post has been edited by shaun_kok: Jun 10 2021, 12:18 PM

Cloudflare is an anycast network, so where you are routed is determined by peering with ISPs. The shortest path geographically isn’t always possible due to peering agreements.

Well, agreed with your statement since it is anycast. Especially when the main Malaysian ISPs peers mainly with SGIX and MyIX and even HKIX and not with JBIX, so this situation can happen.
At this moment, most of the traffic for Cloudflare are routed into SG/JB (for TM) in my area but some to ridiculous HK/Osaka (even when MyIX isn't rerouted) as MyIX is currently rerouted by Cloudflare.



This post has been edited by shaun_kok: Jun 10 2021, 12:44 PM

problem is TM who always have issue with Cloudflare and is not the first time and the last.

since now TM connection to Cloudflare SG and KUL colo all previously via JP now switching to HKG also which routed to free peering from Telstra HKG.

Telstra IP-transit is quite expensive as TM won't pay for such fee's

i also not sure if their gateway infrastructure having (MRTG) to check their network capacity or not.

If TM route to HK, then I better find hosting/VM in HK rather than SG. Correct?

only cloudflare that are affected.. the rest still running the same routing.

TM called me again today, and I said again about the packet loss issue since I saw connection from OVH and also Network SG GS already seems quite good at latency/ping.

But still have high latency to Facebook, Discord. I dont know if its normally like that since I think I managed to get good result before for Facebook and Discord (below 50ms) .

Continue monitor today guys lets see how it goes.