High latency issues in World of Warcraft.

[Etched]

I have just switched over internet connections from maxnet to orcon. Over the last 2 weeks I have been sitting on a minimum of 500 ms in game. From around 8pm through to after midnight this increases to 800-1000+ ms and it gets as bad as 2k ms.

I have done a trace route and these are the results:

1 sx763 (192.168.2.1) 2.835 ms 1.009 ms 8.586 ms
2 lo1.ras1.nct.orcon.net.nz (60.234.8.201) 9.580 ms 7.376 ms 25.489 ms
3 ge-0-0-4-0.cre1.nct.orcon.net.nz (121.98.9.1) 6.284 ms 6.597 ms 5.962 ms
4 xe-1-0-0.cre2.nct.orcon.net.nz (121.98.9.14) 5.773 ms 5.177 ms 6.251 ms
5 ae3.bdr2.nct.orcon.net.nz (121.98.9.146) 7.005 ms 6.685 ms 7.245 ms
6 xe-1-1-0-401.bdr1.nct.orcon.net.nz (203.192.167.34) 12.332 ms 7.863 ms 7.008 ms
7 Gi10-0-0-401.GW1.AKL1.asianetcom.net (203.192.167.33) 7.259 ms 9.784 ms 8.091 ms
8 ge-0-0-0-0.gw1.akl2.asianetcom.net (203.192.185.45) 10.086 ms 7.127 ms 7.064 ms
9 po8-1.gw1.sjc1.asianetcom.net (203.192.185.50) 162.145 ms 162.759 ms 162.333 ms
10 12.126.40.25 (12.126.40.25) 139.812 ms 138.492 ms 139.318 ms
11 cr2.sffca.ip.att.net (12.122.136.62) 174.877 ms 188.606 ms 173.199 ms
12 cr2.la2ca.ip.att.net (12.122.31.133) 174.629 ms 176.484 ms 172.614 ms
13 cr2.dlstx.ip.att.net (12.122.28.177) 172.837 ms 172.051 ms 172.942 ms
14 gar23.dlstx.ip.att.net (12.122.138.157) 193.866 ms 171.582 ms 205.227 ms
15 12-122-254-154.attens.net (12.122.254.154) 173.175 ms 172.182 ms 172.413 ms
16 mdf001c7613r0003-gig-12-1.dal1.attens.net (63.241.193.22) 177.344 ms 174.510 ms 183.352 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * *

I'm not really too sure how to read this but I don't see any particularly high numbers, yet while I ran this trace route my in game ms was sitting on 1400.

 

[Sambo110]

This screams an ISP problem. Maybe your ISP just sucks for gaming? Do an online speedtest, it will tell you what your latency is.

 

[huntercr]

I have just switched over internet connections from maxnet to orcon. Over the last 2 weeks I have been sitting on a minimum of 500 ms in game. From around 8pm through to after midnight this increases to 800-1000+ ms and it gets as bad as 2k ms.

I have done a trace route and these are the results:

1 sx763 (192.168.2.1) 2.835 ms 1.009 ms 8.586 ms
2 lo1.ras1.nct.orcon.net.nz (60.234.8.201) 9.580 ms 7.376 ms 25.489 ms
3 ge-0-0-4-0.cre1.nct.orcon.net.nz (121.98.9.1) 6.284 ms 6.597 ms 5.962 ms
4 xe-1-0-0.cre2.nct.orcon.net.nz (121.98.9.14) 5.773 ms 5.177 ms 6.251 ms
5 ae3.bdr2.nct.orcon.net.nz (121.98.9.146) 7.005 ms 6.685 ms 7.245 ms
6 xe-1-1-0-401.bdr1.nct.orcon.net.nz (203.192.167.34) 12.332 ms 7.863 ms 7.008 ms
7 Gi10-0-0-401.GW1.AKL1.asianetcom.net (203.192.167.33) 7.259 ms 9.784 ms 8.091 ms
8 ge-0-0-0-0.gw1.akl2.asianetcom.net (203.192.185.45) 10.086 ms 7.127 ms 7.064 ms
9 po8-1.gw1.sjc1.asianetcom.net (203.192.185.50) 162.145 ms 162.759 ms 162.333 ms
10 12.126.40.25 (12.126.40.25) 139.812 ms 138.492 ms 139.318 ms
11 cr2.sffca.ip.att.net (12.122.136.62) 174.877 ms 188.606 ms 173.199 ms
12 cr2.la2ca.ip.att.net (12.122.31.133) 174.629 ms 176.484 ms 172.614 ms
13 cr2.dlstx.ip.att.net (12.122.28.177) 172.837 ms 172.051 ms 172.942 ms
14 gar23.dlstx.ip.att.net (12.122.138.157) 193.866 ms 171.582 ms 205.227 ms
15 12-122-254-154.attens.net (12.122.254.154) 173.175 ms 172.182 ms 172.413 ms
16 mdf001c7613r0003-gig-12-1.dal1.attens.net (63.241.193.22) 177.344 ms 174.510 ms 183.352 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * *

I'm not really too sure how to read this but I don't see any particularly high numbers, yet while I ran this trace route my in game ms was sitting on 1400.

I would say thats about right for general purpose traffic coming from New Zealand to the USA. Your worst hop recorded was under 200ms. If there was really something wrong, you'd see 1000+ on some of these.

I would double check you don't have any BitTorrent, or any other clients running in the background. Even if they're idle, it will affect your ping rate within a game, this is because the game server only polls this in distinct intervals and even though your actual bandwidth might be available most of the time, it's going to look like it isn't.

This will also happen if you have any other computers sharing this internet connection. Despite being allowed to plug more than one computer into a DSL/Cable modem switch, there is no active parcelling of bandwidth on most devices... who ever asks for the bandwidth gets it and must constantly fight with other systems.

If this ends up being the problem, and you really feel you need to have your background apps running, there's an alternative...
You could buy a better Cable/DSL router that has packet prioritization and QoS packet a management and tune it to give WoW high priority.

Of course I could be way off... but I hope this helps!