Can confirm Penang area connection has been really shitty since 8+ pm

Is there a templated complain letter that we can use to report to MCMC?
A proper letter to explain what's happening behind the scene and the possible cause of slowdown

I believe a lot of us are experiencing slow down with unifi but we are not well versed enough in trying to explain or figure out what's happening behind the scene.
Most of the time we can only do a generic complain of internet slowdown without understanding the real issue and TM's only solution is reset port reset port. When this happens, our general non-technical complain will be brushed away/neglected with the tidak apa attitude.

I suppose if more of us could report to MCMC with the proper details using a template, things might move in our favor?
Just my 2 cent

Any idea what's wrong with cloudfare CDN server?
http://a6f8b63db610.ap.ngrok.io/smokeping/?target=CDN.CDN-9

Anyone using WeVPN here? How's the performance?
I'm trying to see how's the routing performance for this particular VPN and is it affected by the nightly slowdown on unifi

go626201 any possibility of adding this to your smokeping site?

Thanks for the feedback
They seems to be quite popular in reddit for streaming purposes

Hmmm does one need to be well versed in networking to set this up?
I'm gonna try googling and read up on what I can find
Thanks for the tips 😁

The default router provided by TM is not exactly the best in its class
In a way that might or will become a bottleneck to your mesh network

By connecting deco directly to the TM modem (BTU), you are reducing the amount of unnecessary devices - save power, less chance of things going wrong and less headache trying to troubleshoot them and a tad better latency for your local network?

That's really ridiculous - it's been discussed thoroughly here - https://forum.lowyat.net/topic/5149798

it seems that TM's routing fked up
if fast.com isn't loading, netflix will definitely be affected

on VPN, everything seems fine tho

What's your unifi IP range?
Apparently some IP range are excluded from the routing issue

fast.com is working for me now