Brand new latency issue

Support Technical Support
1

WoW has been running fine for me until Monday (raid day, of course). I was suddenly getting upwards of 7k MS values, especially during fights. My other internet resources were running just fine. I suspected something graphically might be the problem, since I’d installed an NVIDIA driver earlier. I have since gotten the new driver that came out on Monday (new to me) and for one warfront everything seemed ok. Now it’s back to terrible latency.

In my investigations, I saw a tool to assist with troubleshooting these problems, but I’m not a network guy and really dont know what to do with the information it provides. It does look like the tool automatically removes the last 3 IP jumps. Could someone guide me as to what might be the issue, please? Fallout 76 runs just fine. Streaming movies, facebook, youtube, whatever are all just fine. At this point, the only thing affected appears to be WoW.

PING:
PING 72.48.45.250 (72.48.45.250) 56(84) bytes of data.

— 72.48.45.250 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

05/12/2018 22:40:10 UTC

PING:
PING 72.48.45.250 (72.48.45.250) 56(84) bytes of data.

— 72.48.45.250 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

05/12/2018 22:40:10 UTC

TRACEROUTE:
traceroute to 72.48.45.250 (72.48.45.250), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.356 ms 0.345 ms 0.344 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

05/12/2018 22:40:10 UTC

TRACEROUTE:
traceroute to 72.48.45.250 (72.48.45.250), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.695 ms 0.707 ms 0.714 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

05/12/2018 22:40:10 UTC

TRACEROUTE:
traceroute to 72.48.45.250 (72.48.45.250), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.312 ms 0.274 ms 0.269 ms Blizzard(24.105.18.2) 1.021 ms 1.026 ms 1.024 ms
3 137.221.105.14 (137.221.105.14) 1.035 ms 1.045 ms 1.044 ms
4 137.221.66.18 (137.221.66.18) 1.028 ms 1.029 ms 1.027 ms
5 137.221.83.70 (137.221.83.70) 25.774 ms 25.789 ms 25.792 ms
6 137.221.65.66 (137.221.65.66) 25.608 ms 26.237 ms 26.212 ms
7 137.221.74.32 (137.221.74.32) 25.374 ms 25.618 ms 25.600 ms
8 core01.dllstx.grandecom. com (206.223.118.111) 26.221 ms 27.116 ms 27.241 ms
9 ae1-0.aggr08.crchtx.grandecom. net (24.155.121.85) 36.653 ms 36.660 ms 36.645 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

05/12/2018 22:40:15 UTC

PING:
PING 72.48.45.250 (72.48.45.250) 56(84) bytes of data.

— 72.48.45.250 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3003ms

05/12/2018 22:40:16 UTC

TRACEROUTE:
traceroute to 72.48.45.250 (72.48.45.250), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.256 ms 0.259 ms 0.262 ms Blizzard(24.105.18.2) 0.551 ms 0.690 ms 0.813 ms
3 137.221.105.14 (137.221.105.14) 1.271 ms 1.292 ms 1.311 ms
4 137.221.66.18 (137.221.66.18) 1.273 ms 1.283 ms 1.286 ms
5 137.221.83.70 (137.221.83.70) 26.604 ms 26.623 ms 26.627 ms
6 137.221.65.66 (137.221.65.66) 26.557 ms 25.672 ms 25.666 ms
7 137.221.74.32 (137.221.74.32) 27.015 ms 26.644 ms 26.606 ms
8 core01.dllstx.grandecom. com (206.223.118.111) 26.860 ms 26.408 ms 26.391 ms
9 ae1-0.aggr08.crchtx.grandecom. net (24.155.121.85) 35.139 ms 35.160 ms 35.162 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

05/12/2018 22:40:19 UTC

MTR:
Start: Wed Dec 5 22:40:10 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

05/12/2018 22:40:10 UTC

MTR:
Start: Wed Dec 5 22:40:10 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

05/12/2018 22:40:10 UTC

PING:
PING 72.48.45.250 (72.48.45.250) 56(84) bytes of data.

— 72.48.45.250 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

05/12/2018 22:40:21 UTC

MTR:
Start: Wed Dec 5 22:40:15 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

05/12/2018 22:40:15 UTC

MTR:
Start: Wed Dec 5 22:40:16 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.3 0.0 Blizzard 0.0% 10 0.5 0.9 0.5 3.9 0.9
3.|-- 137.221.105.14 0.0% 10 0.6 0.5 0.4 0.7 0.0
4.|-- 137.221.66.18 0.0% 10 0.7 1.5 0.5 10.0 2.9
5.|-- 137.221.83.70 0.0% 10 54.0 28.5 25.5 54.0 9.0
6.|-- 137.221.65.66 0.0% 10 25.5 25.6 25.5 25.8 0.0
7.|-- 137.221.74.32 0.0% 10 37.8 27.8 25.3 37.8 4.8
8.|-- core01.dllstx.grandecom. com 20.0% 10 33.7 27.0 25.7 33.7 2.7
9.|-- ae1-0.aggr08.crchtx.grandecom. net 20.0% 10 35.1 35.3 35.1 36.1 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

05/12/2018 22:40:16 UTC

2

Grandecom has been having issues routing through a level3 hub in Dallas. That looks to be your isp.

3

Would I take it that during raids or warfronts there is so much data moving that I notice the problem and otherwise, or with other games/videos/sites, there just isn’t the same amount of data so any packet loss is not noticed?

4

I’m having the same issue, with the level 3 hub in Dallas.

Now, I’m using my phone as a hotspot and it actually works well.

5 
i am also having the same issue but only high spikes when in combat or in raid. 

TRACEROUTE:
traceroute to 64.92.41.175 (64.92.41.175), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.266 ms  0.273 ms  0.285 ms Blizzard(24.105.18.2)  1.402 ms  1.412 ms  1.421 ms
 3  137.221.105.14 (137.221.105.14)  0.532 ms  0.721 ms  0.846 ms
 4  137.221.66.18 (137.221.66.18)  0.643 ms  0.685 ms  0.714 ms
 5  137.221.83.70 (137.221.83.70)  25.685 ms  25.745 ms  25.755 ms
 6  137.221.65.66 (137.221.65.66)  25.480 ms  25.699 ms  25.701 ms
 7  137.221.74.32 (137.221.74.32)  25.476 ms  25.487 ms  25.895 ms
 8  de-cix.dallas.consolidated.net (206.53.202.39)  26.086 ms  26.295 ms  26.310 ms
 9  dllstxldhre-207-70-186-102.consolidated.net (207.70.186.102)  36.123 ms  35.906 ms  35.980 ms
10  katytxxchrl-207-70-186-61.consolidated.net (207.70.186.61)  35.774 ms  35.730 ms  36.010 ms
11  katytxxchrc-te0-0-0-2.consolidated.net (207.70.187.208)  36.523 ms  38.514 ms  38.731 ms
12  dsl-dhcp-katytxxchrc-64-92-41-175.consolidated.net (64.92.41.175)  36.272 ms  36.224 ms  36.048 ms


06/12/2018 01:43:45 UTC
--------------------

PING:
PING 64.92.41.175 (64.92.41.175) 56(84) bytes of data.
64 bytes from 64.92.41.175: icmp_seq=1 ttl=53 time=36.3 ms
64 bytes from 64.92.41.175: icmp_seq=2 ttl=53 time=36.3 ms
64 bytes from 64.92.41.175: icmp_seq=3 ttl=53 time=36.0 ms
64 bytes from 64.92.41.175: icmp_seq=4 ttl=53 time=36.2 ms

--- 64.92.41.175 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 36.005/36.219/36.338/0.269 ms


06/12/2018 01:43:45 UTC
--------------------

PING:
PING 64.92.41.175 (64.92.41.175) 56(84) bytes of data.
64 bytes from 64.92.41.175: icmp_seq=1 ttl=53 time=36.0 ms
64 bytes from 64.92.41.175: icmp_seq=2 ttl=53 time=36.1 ms
64 bytes from 64.92.41.175: icmp_seq=3 ttl=53 time=36.0 ms
64 bytes from 64.92.41.175: icmp_seq=4 ttl=53 time=36.0 ms

--- 64.92.41.175 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 36.024/36.080/36.179/0.199 ms


06/12/2018 01:43:45 UTC
--------------------

TRACEROUTE:
traceroute to 64.92.41.175 (64.92.41.175), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.307 ms  0.312 ms  0.319 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * dllstxldhre-207-70-186-102.consolidated.net (207.70.186.102)  37.345 ms  37.376 ms
10  * * *
11  katytxxchrc-te0-0-0-0.consolidated.net (207.70.187.214)  38.358 ms  38.503 ms  38.517 ms
12  dsl-dhcp-katytxxchrc-64-92-41-175.consolidated.net (64.92.41.175)  36.265 ms  36.287 ms  36.074 ms


06/12/2018 01:43:45 UTC
--------------------

PING:
PING 64.92.41.175 (64.92.41.175) 56(84) bytes of data.
64 bytes from 64.92.41.175: icmp_seq=1 ttl=53 time=36.1 ms
64 bytes from 64.92.41.175: icmp_seq=2 ttl=53 time=36.3 ms
64 bytes from 64.92.41.175: icmp_seq=3 ttl=53 time=36.2 ms
64 bytes from 64.92.41.175: icmp_seq=4 ttl=53 time=36.1 ms

--- 64.92.41.175 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 36.153/36.213/36.312/0.061 ms


06/12/2018 01:43:49 UTC
--------------------

TRACEROUTE:
traceroute to 64.92.41.175 (64.92.41.175), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.245 ms  0.316 ms  0.557 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * katytxxchrc-te0-0-0-0.consolidated.net (207.70.187.214)  38.489 ms  38.523 ms
12  dsl-dhcp-katytxxchrc-64-92-41-175.consolidated.net (64.92.41.175)  36.198 ms  36.309 ms  36.210 ms


06/12/2018 01:43:49 UTC
--------------------

TRACEROUTE:
traceroute to 64.92.41.175 (64.92.41.175), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.300 ms  0.304 ms  0.311 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * katytxxchrl-207-70-186-61.consolidated.net (207.70.186.61)  37.326 ms  37.352 ms
11  * katytxxchrc-te0-0-0-0.consolidated.net (207.70.187.214)  36.367 ms  36.534 ms
12  dsl-dhcp-katytxxchrc-64-92-41-175.consolidated.net (64.92.41.175)  36.325 ms  36.553 ms  36.200 ms


06/12/2018 01:43:52 UTC
--------------------

PING:
PING 64.92.41.175 (64.92.41.175) 56(84) bytes of data.
64 bytes from 64.92.41.175: icmp_seq=1 ttl=53 time=36.2 ms
64 bytes from 64.92.41.175: icmp_seq=2 ttl=53 time=36.1 ms

--- 64.92.41.175 ping statistics ---
4 packets transmitted, 2 received, 50% packet loss, time 2999ms
rtt min/avg/max/mdev = 36.111/36.155/36.200/0.195 ms


06/12/2018 01:43:53 UTC
--------------------

MTR:
Start: Thu Dec  6 01:43:45 2018 Blizzard  1.|-- Blizzard    0.0%    10    0.3   0.4   0.2   0.7   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


06/12/2018 01:43:45 UTC
--------------------

MTR:
Start: Thu Dec  6 01:43:46 2018 Blizzard  1.|-- Blizzard    0.0%    10    0.3   0.3   0.2   0.4   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


06/12/2018 01:43:46 UTC
--------------------

MTR:
Start: Thu Dec  6 01:43:45 2018 Blizzard  1.|-- Blizzard                                        0.0%    10    0.3   0.3   0.2   0.4   0.0 Blizzard                0.0%    10    0.6   0.6   0.5   0.8   0.0
  3.|-- 137.221.105.14                                      0.0%    10    1.0   0.7   0.6   1.0   0.0
  4.|-- 137.221.66.18                                       0.0%    10    0.9   0.7   0.6   0.9   0.0
  5.|-- 137.221.83.70                                       0.0%    10   25.7  26.0  25.5  28.9   0.9
  6.|-- 137.221.65.66                                       0.0%    10   36.7  41.2  25.5 169.2  45.1
  7.|-- 137.221.74.32                                      10.0%    10   25.6  25.7  25.3  26.7   0.4
  8.|-- de-cix.dallas.consolidated.net                      0.0%    10   25.9  26.0  25.8  26.2   0.0
  9.|-- dllstxldhre-207-70-186-102.consolidated.net         0.0%    10   36.1  36.0  35.9  36.1   0.0
 10.|-- katytxxchrl-207-70-186-61.consolidated.net          0.0%    10   35.9  36.0  35.8  36.5   0.0
 11.|-- katytxxchrc-te0-0-0-2.consolidated.net              0.0%    10   36.2  37.1  36.1  42.5   1.9
 12.|-- dsl-dhcp-katytxxchrc-64-92-41-175.consolidated.net 10.0%    10   36.4  36.4  36.3  36.6   0.0


06/12/2018 01:43:45 UTC
--------------------

MTR:
Start: Thu Dec  6 01:43:50 2018 Blizzard  1.|-- Blizzard    0.0%    10    0.4   0.3   0.2   0.4   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


06/12/2018 01:43:50 UTC
--------------------
6

Hey all,

We’re currently gathering information and tests on the Level 3 situation over in a dedicated thread for it. To keep the information in the same place, I’m going to lock this thread up. I would definitely encourage posting any reports or tests over in that thread.

-Lantrasau

1 Like