Lagging only in WoW

[jemd13]

Hello everyone. I'm having a problem. I seem to lag only in WoW. Usually having a latency of around 100-200 (home) and 1k-5k (server) . I did the whole traceroute thing in the support page and I wanted to post the results to see if anyone could help me or point me to where the problem actually is. At one point all packages seem to time out, but not sure where that is. It seems in hop 15 where it starts, but I'm not sure if this means the problem is my ISP or what... I can play other games and load youtube videos just fine though.

(Excuse the spanish. I believe you guys understand this anyway).

Traza a 199.108.62.157 sobre caminos de 30 saltos como max.

 1 32 ms 31 ms 31 ms lms-01-lo78.bras.cantv.net [201.208.224.1] 
 2 32 ms 33 ms 32 ms 172.26.1.97 
 3 * * * Tiempo de espera agotado para esta solicitud.
 4 33 ms 33 ms 33 ms 10.82.1.21 
 5 32 ms 33 ms 38 ms 10.82.1.1 
 6 122 ms 120 ms 127 ms 200.16.71.177 
 7 111 ms 115 ms 111 ms ge5-0-0d0.cir1.miami2-fl.us.xo.net [216.156.104.9] 
 8 140 ms 140 ms 138 ms vb2000d1.rar3.miami-fl.us.xo.net [207.88.13.166] 
 9 137 ms 139 ms 140 ms 207.88.12.79.ptr.us.xo.net [207.88.12.79] 
 10 145 ms 148 ms 168 ms cir1.atlanta6-ga.us.xo.net [207.88.13.49] 
 11 143 ms 144 ms 143 ms 67.111.23.90.ptr.us.xo.net [67.111.23.90] 
 12 153 ms 151 ms 152 ms 12.122.29.54 
 13 * * * Tiempo de espera agotado para esta solicitud.
 14 157 ms 157 ms 157 ms 12.123.250.113 
 15 * * * Tiempo de espera agotado para esta solicitud.
 16 * * * Tiempo de espera agotado para esta solicitud.
 17 * * * Tiempo de espera agotado para esta solicitud.
 18 * * * Tiempo de espera agotado para esta solicitud.
 19 * * * Tiempo de espera agotado para esta solicitud.
 20 * * * Tiempo de espera agotado para esta solicitud.
 21 * * * Tiempo de espera agotado para esta solicitud.
 22 * * * Tiempo de espera agotado para esta solicitud.
 23 * * * Tiempo de espera agotado para esta solicitud.
 24 * * * Tiempo de espera agotado para esta solicitud.
 25 * * * Tiempo de espera agotado para esta solicitud.
 26 * * * Tiempo de espera agotado para esta solicitud.
 27 * * * Tiempo de espera agotado para esta solicitud.
 28 * * * Tiempo de espera agotado para esta solicitud.
 29 * * * Tiempo de espera agotado para esta solicitud.
 30 * * * Tiempo de espera agotado para esta solicitud.

Traza completa.

This is the result of the Blizzard Looking Glass test for my server (Dalaran). My ISP is called Cantv. I live in Venezuela, but this has never been a problem when playing WoW or any other game. So its weird that this starts happening now.

PING:
PING 201.208.234.65 (201.208.234.65) 56(84) bytes of data.
64 bytes from 201.208.234.65: icmp_seq=1 ttl=44 time=269 ms
64 bytes from 201.208.234.65: icmp_seq=2 ttl=44 time=280 ms
64 bytes from 201.208.234.65: icmp_seq=3 ttl=44 time=285 ms
64 bytes from 201.208.234.65: icmp_seq=4 ttl=44 time=294 ms

--- 201.208.234.65 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3293ms
rtt min/avg/max/mdev = 269.847/282.647/294.414/8.938 ms

05/07/2016 01:37:22 UTC
--------------------

PING:
PING 201.208.234.65 (201.208.234.65) 56(84) bytes of data.
64 bytes from 201.208.234.65: icmp_seq=1 ttl=44 time=276 ms
64 bytes from 201.208.234.65: icmp_seq=3 ttl=44 time=286 ms
64 bytes from 201.208.234.65: icmp_seq=4 ttl=44 time=289 ms

--- 201.208.234.65 ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 4001ms
rtt min/avg/max/mdev = 276.047/283.984/289.377/5.731 ms

05/07/2016 01:37:21 UTC
--------------------

TRACEROUTE:
traceroute to 201.208.234.65 (201.208.234.65), 15 hops max, 60 byte packets
 1 Blizzard (Blizzard) 0.847 ms 0.855 ms 0.886 ms
 2 * * *
 3 37.244.1.102 (37.244.1.102) 3.702 ms 3.726 ms 3.731 ms
 4 37.244.1.34 (37.244.1.34) 3.584 ms 3.626 ms 3.628 ms
 5 * * *
 6 100ge3-2.core1.nyc4.he.net (184.105.223.162) 23.845 ms 22.375 ms 22.381 ms
 7 10ge5-1.core1.nyc6.he.net (184.105.222.82) 21.891 ms 20.873 ms 20.885 ms
 8 * * *
 9 200.16.69.0 (200.16.69.0) 127.828 ms 127.541 ms 127.583 ms
10 200.16.71.178 (200.16.71.178) 243.097 ms 243.164 ms 243.007 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 201-208-234-65.genericrev.cantv.net (201.208.234.65) 286.526 ms 287.754 ms 288.756 ms

05/07/2016 01:37:21 UTC
--------------------

TRACEROUTE:
traceroute to 201.208.234.65 (201.208.234.65), 15 hops max, 60 byte packets
 1 Blizzard (Blizzard) 0.463 ms 0.622 ms 0.697 ms
 2 * * *
 3 37.244.1.102 (37.244.1.102) 4.923 ms 4.932 ms 4.932 ms
 4 37.244.1.34 (37.244.1.34) 2.588 ms 2.624 ms 2.690 ms
 5 * * *
 6 100ge3-2.core1.nyc4.he.net (184.105.223.162) 20.876 ms 20.882 ms 20.871 ms
 7 10ge5-1.core1.nyc6.he.net (184.105.222.82) 20.908 ms 20.898 ms 20.904 ms
 8 * * *
 9 200.16.69.0 (200.16.69.0) 125.438 ms 125.274 ms 125.137 ms
10 200.16.71.178 (200.16.71.178) 239.832 ms 239.839 ms 239.794 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 201-208-234-65.genericrev.cantv.net (201.208.234.65) 289.826 ms 290.826 ms 292.089 ms

05/07/2016 01:37:22 UTC
--------------------

PING:
PING 201.208.234.65 (201.208.234.65) 56(84) bytes of data.
64 bytes from 201.208.234.65: icmp_seq=1 ttl=45 time=342 ms
64 bytes from 201.208.234.65: icmp_seq=2 ttl=45 time=348 ms
64 bytes from 201.208.234.65: icmp_seq=3 ttl=45 time=348 ms
64 bytes from 201.208.234.65: icmp_seq=4 ttl=45 time=346 ms

--- 201.208.234.65 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3346ms
rtt min/avg/max/mdev = 342.280/346.370/348.309/2.441 ms

05/07/2016 01:37:27 UTC
--------------------

TRACEROUTE:
traceroute to 201.208.234.65 (201.208.234.65), 15 hops max, 60 byte packets
 1 Blizzard (Blizzard) 0.562 ms 0.590 ms 0.697 ms
 2 * * *
 3 37.244.0.100 (37.244.0.100) 1.763 ms 1.778 ms 1.853 ms
 4 37.244.0.32 (37.244.0.32) 2.759 ms 2.780 ms 2.784 ms
 5 * * *
 6 100ge12-1.core1.ash1.he.net (184.105.80.201) 67.769 ms 73.503 ms 73.485 ms
 7 * * *
 8 200.16.69.0 (200.16.69.0) 191.370 ms 191.266 ms 191.263 ms
 9 200.16.71.178 (200.16.71.178) 306.374 ms 305.798 ms 305.669 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 201-208-234-65.genericrev.cantv.net (201.208.234.65) 339.396 ms 345.193 ms 346.444 ms

05/07/2016 01:37:26 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
 1. Blizzard 0.0% 10 0.6 0.5 0.5 0.6 0.0
 2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 3. 37.244.1.102 0.0% 10 3.6 2.8 2.6 3.6 0.3
 4. 37.244.1.34 0.0% 10 2.5 2.9 2.3 4.2 0.7
 5. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 6. 100ge3-2.core1.nyc4.he.net 0.0% 10 26.9 27.3 20.9 31.8 4.1
 7. 10ge5-1.core1.nyc6.he.net 0.0% 10 28.8 27.8 20.9 33.7 5.1
 8. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 9. 200.16.69.0 10.0% 10 128.1 128.3 123.8 137.6 4.5
 10. 200.16.71.178 10.0% 10 253.7 258.7 241.0 310.0 20.1
 11. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

05/07/2016 01:37:21 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
 1. Blizzard 0.0% 10 0.5 0.9 0.4 2.7 0.9
 2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 3. 37.244.1.102 0.0% 10 3.8 2.8 2.5 3.8 0.5
 4. 37.244.1.34 0.0% 10 2.4 2.7 2.4 3.7 0.5
 5. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 6. 100ge3-2.core1.nyc4.he.net 0.0% 10 66.1 27.5 20.9 66.1 14.2
 7. 10ge5-1.core1.nyc6.he.net 0.0% 10 32.0 23.3 20.9 33.6 5.0
 8. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 9. 200.16.69.0 10.0% 10 130.1 128.7 122.8 138.9 4.9
 10. 200.16.71.178 20.0% 10 252.5 253.1 243.6 274.5 10.6
 11. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

05/07/2016 01:37:21 UTC
--------------------

PING:
PING 201.208.234.65 (201.208.234.65) 56(84) bytes of data.
64 bytes from 201.208.234.65: icmp_seq=1 ttl=45 time=346 ms
64 bytes from 201.208.234.65: icmp_seq=2 ttl=45 time=348 ms
64 bytes from 201.208.234.65: icmp_seq=3 ttl=45 time=351 ms
64 bytes from 201.208.234.65: icmp_seq=4 ttl=45 time=345 ms

--- 201.208.234.65 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3345ms
rtt min/avg/max/mdev = 345.913/347.955/351.522/2.285 ms

05/07/2016 01:37:31 UTC
--------------------

TRACEROUTE:
traceroute to 201.208.234.65 (201.208.234.65), 15 hops max, 60 byte packets
 1 Blizzard (Blizzard) 0.362 ms 0.474 ms 0.617 ms
 2 * * *
 3 37.244.0.100 (37.244.0.100) 1.648 ms 1.750 ms 2.471 ms
 4 37.244.0.32 (37.244.0.32) 2.756 ms 2.773 ms 2.784 ms
 5 * * *
 6 100ge12-1.core1.ash1.he.net (184.105.80.201) 65.907 ms 66.019 ms 66.009 ms
 7 * * *
 8 200.16.69.0 (200.16.69.0) 189.818 ms 189.952 ms 189.953 ms
 9 200.16.71.178 (200.16.71.178) 322.791 ms 305.543 ms 305.688 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 201-208-234-65.genericrev.cantv.net (201.208.234.65) 348.626 ms 349.540 ms 350.789 ms

05/07/2016 01:37:30 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
 1. Blizzard 0.0% 10 0.3 0.4 0.3 0.5 0.1
 2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 3. 37.244.0.100 0.0% 10 1.7 2.0 1.6 3.3 0.5
 4. 37.244.0.32 0.0% 10 2.8 1.9 1.5 3.0 0.5
 5. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 6. 100ge12-1.core1.ash1.he.net 0.0% 10 68.8 70.2 65.9 75.5 3.6
 7. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 8. 200.16.69.0 0.0% 10 184.6 192.9 184.6 224.3 11.3
 9. 200.16.71.178 0.0% 10 309.9 311.1 307.7 314.8 2.2
 10. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

05/07/2016 01:37:26 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
 1. Blizzard 0.0% 10 0.4 0.5 0.4 0.9 0.2
 2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 3. 37.244.0.100 0.0% 10 2.0 1.9 1.7 2.5 0.3
 4. 37.244.0.32 0.0% 10 2.9 1.7 1.5 2.9 0.4
 5. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 6. 100ge12-1.core1.ash1.he.net 0.0% 10 75.2 73.8 66.0 76.9 3.1
 7. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
 8. 200.16.69.0 0.0% 10 191.5 193.8 185.5 231.6 13.4
 9. 200.16.71.178 0.0% 10 318.0 312.5 306.3 318.0 3.3
 10. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

05/07/2016 01:37:27 UTC
--------------------

Can anyone help me?:x Thanks!.

[pkm]

1. Are you using a router or modem by itself?

2. Can you get anyone else from your ISP to run the same tests?

[Tumble]

I had a very similar problem. Looked at everything, eventually the lag turned into disconnects. It wasn't until I noticed my frame rate was super low compared to the normal 120ish on ultra. I turned down the settings and the dcs stopped and the lag went down to around 1k. Turns out I had a faulty power supply, don't ask how or why it was causing that issue, but the moment I replaced it everything went back to normal.

[Blackmist]

Traceroutes often return nothing at certain points. It just means those servers aren't configured to respond to ping requests. It's nothing to worry about and doesn't indicate a problem.

I can't see any issues in the traceroutes you posted. ~300ms seems normal for connecting from where you are.

[jemd13]

1. Are you using a router or modem by itself?

2. Can you get anyone else from your ISP to run the same tests?

1. I'm using a router.

2. I guess I'd have to try. I'd rather not have to call them since, even though they are one of the best ISPs in my country, they are actually pretty bad lol. I'm pretty sure they won't know what I'm talking about if I ask them for this unless they lemme talk to someone with more knowledge.

- - - Updated - - -

I had a very similar problem. Looked at everything, eventually the lag turned into disconnects. It wasn't until I noticed my frame rate was super low compared to the normal 120ish on ultra. I turned down the settings and the dcs stopped and the lag went down to around 1k. Turns out I had a faulty power supply, don't ask how or why it was causing that issue, but the moment I replaced it everything went back to normal.

Might be, but I actually doubt its the power supply (I had a similar problem before where it actually was the PS), since at around 11pm-12am the lag stops and I can play just fine o.o.

[Krieger]

Try installing gentoo, or maybe just reinstalling your WoW install. Make sure all your ports are forwarded.