IP pool rarely makes a difference now. I’m in JB as well (Mt. Austin), and have been assigned all the IP ranges you listed, including the obscure ones like 124.13.xxx or 1.32.xxx and it seldom makes much of a difference. On bad days, basically there will be a period every hour that lasts anywhere between 5 - 30 minutes where certain peering routes get overloaded and TM will do traffic shaping or load balancing of some sort (I don’t know the exact technical term, sorry). The only difference your assigned IP pool makes is the time it occurs, but it almost definitely will occur once every hour for all these IPs.

Like you say, a VPN helps, but there are limitations. If the route to your VPN is through one of these overloaded peering providers, then it makes no difference. For example, for your VPN’s SG servers, it would depend on which datacenter they’re housed in and what peering hops are taken back to your TM IP address. In my experience, M247 and DataPacket/DataCamp servers in certain datacenters rely on PCCW, which is completely f@#ked when this issues happen. M247-Level3 is much more reliable. If what you say is true and OVPN relies on OVH, then you’re already in a quite good situation since (according to a poster here) OVH has a private peering agreement set up with TM.

Anyway, it’s a good idea to do proper traceroutes to any commercial VPN provider’s servers in the region before you commit to a subscription. Even then, it’s better to pay a bit more for a monthly sub rather than discounted yearly deals, since TMs peering situation may change at any time. Obviously rolling your own on a VPS is also great,  ut those have their own limitations like reduced privacy (because most require CC details) and data caps.

Hmm, another crash at 0 AM and now heavy packet drop on 10.233 to 10.55, most oversea line force disconnect, guess another CGNAT issues?

Strange that it happen sharp 0 AM again lol, guess someone setup a bot or spider to send a lot of traffic + TCP half-open line during 0 AM.

And another is, the Malaysia going out/in is crashing.

Like lazada now, the static CDN server is at Malaysia Akamai, it take 21s for loading, and telling the browser it is CDN server loading/downloading from main server at SG.
So, even local CDN making it worst....  

IP range is nothing as long as it give the good route, but it is not, that's the problem.

Even UniFi Mobile is better than UniFi fiber.... 

At least back to normal for me now, gonna see how long will it last.

Based on record, a quick and silent disconnect happen around 10 PM 25th, kicked me to 124.13.x.x, while route #3 also changed from 10.233.97.55 to 10.233.33.88.



If you still got issues on Lazada, u may try can get 124.x.x.x IP range or not, if lazada fine and ping Google DNS 8.8.8.8 also fine, that's normal oversea line issues lol.

You also under CGNAT, or under higher plan which got public IP?
If public IP, then it means TM fxxk up for all customers lol, IP just nothing for them.

At least can pay maxis to get public IP lol.

Guess only me waiting RM 69 30M lol, gonna see lower QoS or not.

Ya, better split it out, never put eggs into same bucket lol.

Maxis even got 4G as backup, lol.

Most of fiber downtime just midnight, should not be a issues I guess?

Nice name for ur router.
Based on third hop is fine respond to ping, so I guess this is overload of CGNAT.    

No seeing problem on my end. Try download with download software. Google chrome is not design use for downloading.


Edited:
France server slower but still okay.



Edited 2:
SJC server okay.



My humble opinion:
Do not use google chrome to download any file that bigger than 100mb.(when u need to download a Big file please use a Download software to download)