say i ping the server and get 300ms latency. Does this means when i play i should roughly get around 300ms latency also?

Because i tried to ping the frostmourne server and i got ~300ms, and when i actually logged in to WoW i got >1500ms :/

The weird thing is that in my apartment i have a friend living in the same block with me (just different floor) and i almost got no problem playing there (latency is mostly below 800ms).

Hi Guys,

Just want to share what I have. I made tracert result to WoW Realm and then forward the result to Teleglobe.net support personnel.

They replied and mentioning that I should talk to TMNET to have better load balancing. Maybe we all can try this, and send the feedback to TMNET 2nd line support to request for improvement.

This is the tool that i use to make Trace Route to WoW Realm : http://winmtr.sourceforge.net/
==============================================

Hi,

It appears that one of TM NET interface with us is saturating while the other
is not. TM NET should be able to better load balance their traffic with us
to provide a better customer experience.

Best regards,

Charles.

> Hi Support,
>
> I am World of Warcraft online game player from Malaysia and recently I been un-pleased with high latency in game
>
> Following is my Trace Route Result and the bottleneck start from Teleglobe.net which hop number 12.
>
> Please do something to improve the network else we are suffer at here. I been contacting my broadband Internet ISP which is TM NET (or Telekom Malaysia) and according to their finding, the problem start from Global Internet line.
>
> Based on the result, I believe you can clearly see that the slow ping start from HOP 12 which is  "12. hop: 216.6.84.49 (if-13-0-0.mcore3.LAA-LosAngeles.teleglobe.net): 291 ms"
>
>
>
> Host information for "12-129-225-14.attens.net":
>   Host name:    12-129-225-14.attens.net
>   IP address:   12.129.225.14
>   Country:      US (UNITED STATES)
>
> Trace route to "12.129.225.14" over a maximum of 30 hops:
>
>    1. hop: 192.168.1.1 (login.router): 0 ms
>    2. hop: 219.93.218.177: 13 ms
>    3. hop: 219.93.219.21: 7 ms
>    4. hop: 58.27.103.73: 7 ms
>    5. hop: 58.27.103.66: 7 ms
>    6. hop: 58.27.103.106: 7 ms
>    7. hop: 210.187.142.5: 8 ms
>    8. hop: 203.106.240.202: 8 ms
>    9. hop: 58.27.113.30: 166 ms
>   10. hop: 58.27.124.58: 8 ms
>   11. hop: 219.93.174.84: 8 ms
>   12. hop: 216.6.84.49 (if-13-0-0.mcore3.LAA-LosAngeles.teleglobe.net): 291 ms
>   13. hop: 216.6.84.114 (Vlan42.icore1.LAA-LosAngeles.teleglobe.net): 291 ms
>   14. hop: 192.205.35.129: 292 ms
>   15. hop: 12.122.90.66 (tbr2.la2ca.ip.att.net): 293 ms
>   16. hop: 12.127.3.189: 215 ms
>   17. hop: 12.122.255.74: 216 ms
>   18. hop: 12.129.193.242 (mdf001c7613r0003-gig-10-1.lax1.attens.net): 215 ms
>   19. hop: 12.129.209.99: 214 ms
>   20. hop: timed out.
>   21. hop: 12.129.225.14 (12-129-225-14.attens.net): 294 ms

============================================