I agree with you on the over-congestion of 219.xxx but not the tweaking.
It's more likely that Streamyx screwed up on one of their infrastructure upgrades. This affected the 219, not the 218 because the upgrade was for 219s. Over the past 2 months, there's been a high subscription to Streamyx - hence the first problem.
The new problem, technically, should not improve WoW situation as it's not exclusive to Streamyx. However if Streamyx put the effort into their piping then WoW should be fine because it'll help the congestion. I doubt this will happen because new pipes means spending. And TMNet is all about max profit.
Our Problem: WoW - over subscription
New Problem: Int'l problem - Malaysiawide
Get Jaring, Maxis or ISDN. I played 5 toons on EQ using ISDN. Ping was 350 max and that's during raids (with 65 people in 1 zone).
QUOTE(LoStBoYz @ Apr 7 2005, 11:23 PM)
I don't the problem we're facing is related to the current TMNet problem.
I do hope they fix ours when they got that fixed, but seriously, I don't think so.
The current problem is due to a international cable problem which affect Jaring and TMnet. The problem we have affects only streamyx ppl with IP219 range.
The only theory I can think of is that IP219 is congested hence the latency. IP218 and IP60 might have a smaller population hence the relatively free lag. This also could explain why the ping time for IP219 during the early mornings are low and steadly increases to the evening.
I also suspect TMNet is implementing so kind of throttling on P2P user. Those users that is on BT or Emule might notice huge drop in download speed the last few weeks. I also believe certain ports related to P2P are throttled to prevent P2P users hogging all the bandwidth. The reason I know this is because if you switch to other port other than the default one in your P2P software, the download speed goes back to normal.
I do not know if 'tweaking' done by TMnet affects the ports used by WoW.
All the above is just a theory, please welcome to shoot it down.
