QUOTE(yenchenje @ Jan 31 2023, 01:45 AM)
Has anyone in JB area recently experienced big IP changes? Usually my PPPoE assigned IP range is either 115.134.x.x, 60.53.x.x and 175.141.x.x. After restarting I get assigned with one of these 3 IPs under CGNAT. But like yesterday or the day before I get assigned 124.13.x.x, which I have never seen before assigned to me and when I woke up today, checked my IP again and it's back to 175.141.x.x. And with the 124.13 range, everything was just BAD, games were having packet drops(Pings weren't fluctuating), speedtest couldn't be completed and would report internet connection is not available when it clearly was (Was on Twitch at the time), and just bad time in general for any content consumption in house.
Is the 124.13 range more for just testing or fallback for TM when the more "better" ranges are being tweaked or something?
And funnily enough, after connecting to my OVH SG server (OVPN VPN), it fixed packets drop issues in my games (But had ping spikes, but made the game way more playable than random packet drops)
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.
This post has been edited by dev/numb: Jan 31 2023, 05:23 PM