QUOTE(hidden830726 @ Mar 1 2012, 09:44 AM)
Tm gonna stop streamyx soon, their resources now all on unifi. So I'm not suprise streamyx problem. Wowtaiwan with unifi no latency prob
That's not the case. You understood it wrongly. The problem lies because TM decides to route a specific carrier to Los Angeles before rerouting it to Taiwan. So
Malaysia -> Los Angeles -> Taiwan
In addition to that, not only Streamyx users are affected. UniFi too. We lagged alot during one of the raids simultaneously which proofs my point that this is backbone problem from TM and not just Streamyx. Other ISP providers like Maxis directly routes our traffic to Singapore -> Taiwan, which reduces the latency and overhead. You can ask BuBu for further information too.
Basically it makes no difference playing in WoW Oceanic Server (Which is hosted in Los Angeles).
I disagree that TMNet is trying to stop Streamyx. It probably won't happen for the next 10 years, because their UniFi coverage is still not strong.
Here is a traceroute proving my point:
CODE
Tracing route to 203.66.119.32 on port 80
Over a maximum of 30 hops.
1 2 ms 2 ms 2 ms 192.168.1.1
2 50 ms 61 ms 38 ms 219.93.218.177
3 59 ms 59 ms 54 ms 124.13.60.149
4 59 ms 58 ms 48 ms 10.55.32.110
5 251 ms 215 ms * 216.6.84.49 [if-4-0-0.mcore3.LAA-LosAngeles.as6453.net]
6 234 ms 254 ms 234 ms 66.110.59.97 [if-11-3-2-13.tcore1.LVW-LosAngeles.as6453.net]
7 270 ms 248 ms 290 ms 64.86.252.98
8 317 ms 320 ms 292 ms 152.63.115.89 [0.ae1.XL3.LAX15.ALTER.NET]
9 323 ms 311 ms 320 ms 152.63.10.10 [0.ge-5-0-0.XT1.SCL2.ALTER.NET]
10 312 ms 329 ms 299 ms 152.63.50.189 [TenGigE0-4-0-3.GW5.SCL2.ALTER.NET]
11 320 ms 228 ms 254 ms 152.179.112.182 [chtglobal-gw.customer.alter.net]
12 373 ms * 349 ms 211.21.116.114 [r4002-s2.tp.hinet.net]
13 395 ms 380 ms 385 ms 220.128.6.86 [220-128-6-86.HINET-IP.hinet.net]
14 202 ms 246 ms 221 ms 220.128.7.162 [TPDT-3012.hinet.net]
15 247 ms 250 ms 231 ms 220.128.2.57 [TYFO-3012.hinet.net]
16 227 ms 247 ms 246 ms 220.128.8.193 [TYFO-3302.hinet.net]
17 243 ms 237 ms 254 ms 211.22.226.13 [211-22-226-13.HINET-IP.hinet.net]
18 203.69.188.9 reports: NO ROUTE
Trace Complete.
As you can see, the total hops is 18. Which is ridiculous as we live in the Asian region. The route exchange can be seen on hop number 5 where it redirects us to Los Angeles node, and finally back to HINet which is a taiwan carrier.
My assumption why TMnet is doing this is probably because of a carrier break down, or probably they ran out of traffic for that particular carrier to Singapore. Anyway this is just an assumption.
This post has been edited by Zepx: Mar 1 2012, 10:07 AM