See latency spike(s) on looking glass, now what?

Technical Support
1

Was having major lag spikes, so I used looking glass (really useful tool), and got this output. I see where there are spikes along the route, but is there anything I can do about it? Not only that, there’s 100% packet loss on pings. TIA

TRACEROUTE:
traceroute to 70.114.98.31 (70.114.98.31), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.390 ms  0.370 ms  0.368 ms
 2  37.244.23.131 (37.244.23.131)  0.548 ms  0.596 ms  0.662 ms
 3  24.105.62.152 (24.105.62.152)  0.927 ms  0.931 ms  0.943 ms
 4  137.221.66.10 (137.221.66.10)  27.108 ms  27.122 ms  27.123 ms
 5  137.221.69.52 (137.221.69.52)  769.853 ms  769.886 ms  769.890 ms
 6  137.221.69.34 (137.221.69.34)  2.114 ms  2.044 ms  1.992 ms
 7  24.30.201.80 (24.30.201.80)  2.028 ms  2.087 ms  2.076 ms
 8  66.109.5.224 (66.109.5.224)  24.344 ms  24.243 ms  24.248 ms
 9  107.14.19.196 (107.14.19.196)  26.265 ms  26.426 ms  26.404 ms
10  107.14.19.193 (107.14.19.193)  24.448 ms  24.472 ms  24.620 ms
11  agg2.dllatxl301r.texas.rr.com (66.109.6.53)  209.598 ms  190.670 ms  190.731 ms
12  agg1.crtntxjt01r.texas.rr.com (24.175.49.1)  33.884 ms  31.892 ms  28.697 ms
13  agg1.plantxmp01r.texas.rr.com (24.175.36.176)  31.038 ms  30.849 ms  30.808 ms
14  agg1.allntx3901h.texas.rr.com (24.175.49.222)  37.417 ms  46.731 ms  46.624 ms
15  agg1.allntx3902m.tx.rr.com (24.28.89.230)  26.216 ms  26.196 ms  26.130 ms


10/08/2021 15:28:47 UTC
--------------------

TRACEROUTE:
traceroute to 70.114.98.31 (70.114.98.31), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.402 ms  0.384 ms  0.383 ms
 2  24.105.18.130 (24.105.18.130)  0.722 ms  0.831 ms  1.022 ms
 3  137.221.105.14 (137.221.105.14)  0.962 ms  0.976 ms  1.022 ms
 4  137.221.66.18 (137.221.66.18)  1.517 ms  1.534 ms  1.536 ms
 5  137.221.83.82 (137.221.83.82)  599.908 ms  599.941 ms  906.030 ms
 6  * * *
 7  137.221.68.32 (137.221.68.32)  5.903 ms  5.943 ms  6.329 ms
 8  24.30.201.94 (24.30.201.94)  5.675 ms  5.690 ms  5.421 ms
 9  66.109.5.240 (66.109.5.240)  35.321 ms  32.899 ms  32.872 ms
10  66.109.5.229 (66.109.5.229)  32.992 ms  33.007 ms  32.631 ms
11  66.109.1.217 (66.109.1.217)  32.900 ms  32.909 ms  32.927 ms
12  agg1.crtntxjt01r.texas.rr.com (24.175.49.1)  38.996 ms  40.955 ms  40.948 ms
13  agg1.plantxmp01r.texas.rr.com (24.175.36.176)  36.495 ms  36.444 ms  36.435 ms
14  agg1.allntx3901h.texas.rr.com (24.175.49.222)  50.318 ms  50.104 ms  49.923 ms
15  agg1.allntx3902m.tx.rr.com (24.28.89.230)  34.209 ms  34.259 ms  34.213 ms


10/08/2021 15:28:47 UTC
--------------------

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

--- 70.114.98.31 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3000ms



10/08/2021 15:28:47 UTC
--------------------

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

--- 70.114.98.31 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms



10/08/2021 15:28:47 UTC
--------------------

MTR:
Start: Tue Aug 10 15:28:47 2021 Blizzard  1.|-- Blizzard                  0.0%    10    0.3   0.3   0.3   0.3   0.0
  2.|-- 24.105.18.130                  0.0%    10    0.5   0.5   0.5   0.6   0.0
  3.|-- 137.221.105.14                 0.0%    10    1.0   0.9   0.8   1.1   0.0
  4.|-- 137.221.66.18                  0.0%    10    0.6   5.7   0.4  53.1  16.6
  5.|-- 137.221.83.82                  0.0%    10  330.8 583.3 189.6 1333. 445.8
  6.|-- 137.221.65.68                 80.0%    10  12695 12736 12695 12776  57.3
  7.|-- 137.221.68.32                  0.0%    10   34.2  12.1   5.9  34.2  10.0
  8.|-- 24.30.201.94                   0.0%    10    5.8   6.7   5.4  14.4   2.7
  9.|-- 66.109.5.240                   0.0%    10   35.4  35.1  31.8  38.3   2.2
 10.|-- 66.109.5.229                   0.0%    10   33.3  32.4  32.2  33.3   0.0
 11.|-- 66.109.1.217                   0.0%    10   32.9  59.2  32.8 228.8  60.5
 12.|-- agg1.crtntxjt01r.texas.rr.com  0.0%    10   37.3  38.7  34.4  42.0   2.3
 13.|-- agg1.plantxmp01r.texas.rr.com  0.0%    10   41.1  38.3  35.0  41.1   2.2
 14.|-- agg1.allntx3901h.texas.rr.com  0.0%    10   52.6  51.9  47.5  56.4   2.6
 15.|-- agg1.allntx3902m.tx.rr.com     0.0%    10   34.3  34.3  34.2  34.8   0.0
 16.|-- ???                           100.0    10    0.0   0.0   0.0   0.0   0.0


10/08/2021 15:28:47 UTC
--------------------

MTR:
Start: Tue Aug 10 15:28:48 2021 Blizzard  1.|-- Blizzard                  0.0%    10    1.2   0.4   0.3   1.2   0.0
  2.|-- 37.244.23.131                  0.0%    10    0.5   0.5   0.4   0.5   0.0
  3.|-- 24.105.62.152                  0.0%    10    0.8   0.9   0.7   1.1   0.0
  4.|-- 137.221.66.10                  0.0%    10    1.9   5.1   1.8  33.1   9.8
  5.|-- 137.221.69.52                  0.0%    10  801.6 775.8 489.9 1052. 199.4
  6.|-- 137.221.69.34                  0.0%    10    2.1   3.9   1.9  10.2   3.3
  7.|-- 24.30.201.80                   0.0%    10    2.0   3.3   1.9  14.3   3.8
  8.|-- 66.109.5.224                   0.0%    10   37.0  25.6  24.1  37.0   4.0
  9.|-- 107.14.19.196                  0.0%    10   20.2  20.4  20.1  21.0   0.0
 10.|-- 107.14.19.193                  0.0%    10   24.5  24.3  24.1  25.1   0.0
 11.|-- agg2.dllatxl301r.texas.rr.com  0.0%    10   24.6  24.4  24.2  24.6   0.0
 12.|-- agg1.crtntxjt01r.texas.rr.com  0.0%    10   33.1  29.9  26.5  33.2   2.4
 13.|-- agg1.plantxmp01r.texas.rr.com  0.0%    10   30.0  30.2  26.7  32.9   2.2
 14.|-- agg1.allntx3901h.texas.rr.com  0.0%    10   38.8  41.5  38.8  46.5   2.4
 15.|-- agg1.allntx3902m.tx.rr.com     0.0%    10   26.2  26.3  26.2  26.9   0.0
 16.|-- ???                           100.0    10    0.0   0.0   0.0   0.0   0.0


10/08/2021 15:28:47 UTC
--------------------
2

The looking glass test looks normal, except for the ping 100% loss when trying to reach your computer. Take notice that the spikes early in the test don’t transfer throughout, meaning they aren’t actually lag, just the ICMP request being ignored by the server (it does this to prevent DDoS attacks).

Instead, make sure to use the suggested WinMTR to capture a connection issue.

3

Thanks for the response Nicole!

So the 80% packet loss at hop 6 on the MTR, and the big jumps on 5 & 6 are nothing to worry about? It’s just a ping issue on those two servers? I guess I wasn’t sure how to read that correctly.

I downloaded WinMTR per your message, and it’s great. I’ll make sure to use it when I’m next able to play.

Thanks again for your help.

4

Heya Luffy,

At 80% packet loss the game would be disconnecting fully not just having latency spikes. Typically these types of results displaying in a single log line that does not continue on later nodes in the chain is the result of network configurations that either ignore or block the test data. It should be safe to ignore those two nodes since the problem does not continue beyond them. Sort of like if google maps said there was a 15 minute delay in traffic ahead but you still got to your destination on-time since the traffic had already cleared and did not actually hinder the drive.

Definitely let us know how things go with this. Cheers!