Latency - Thrall

Support Technical Support
1

Happy Holidays everyone! :santa:

I have been experiencing a lot of lag when it comes to playing WoW, this has been going on for months now. I am getting anywhere from 100 to 800ms in both Home and World I am starting to think it is my ISP but I wanted to see what real professionals think before I call a call centre.

I see that when I use the MTR tool there is no listing for the server that I play on (Thrall) so I used the WinMTR tool. Also, I don’t know if it makes a difference with US Central or the Chicago Centre but I got them both. I also avoid downloading anything while playing.

If someone could tell me please where the problem is and if or how I can tell my ISP with sounding like I kind of know what the problem is.

Oh, and all periods from addresses have been replaced by commas.

So, the details:

  • ISP - Cogeco
  • Cable/Fiber Mix
  • Canada, Ontario, Trenton
  • Windows 10 Version 1903 - OS Build 18362.535
  • Hard Wired - NOT Wireless

Pathping to 24.105.62.129 (US Central).

Summary

Tracing route to 24.105.62.129 over a maximum of 30 hops

0 DESKTOP-D4O9QEN.cgocable,net [192.168.0.139]
1 10.73.192.1
2 10.73.192.1
3 10.0.73.109
4 * 10.0.18.78
5 * 10.0.18.29
6 4.59.214.141
7 * 4.69.142.178
8 * BLIZZARD-EN.ear7.Chicago2.Level3,net [4.7.196.134]
9 ae1-br02-eqch2.as57976,net [137.221.69.35]
10 be2-pe1-eqch2.as57976,net [137.221.69.71]
11 chi-eqch2-ia-bons-02.as57976,net [137.221.66.11]
12 24.105.62.129

Computing statistics for 300 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-D4O9QEN.cgocable,net [192.168.0.139]
0/ 100 = 0% |
1 — 100/ 100 =100% 100/ 100 =100% 10.73.192.1
0/ 100 = 0% |
2 — 100/ 100 =100% 100/ 100 =100% 10.73.192.1
0/ 100 = 0% |
3 — 100/ 100 =100% 100/ 100 =100% 10.0.73.109
0/ 100 = 0% |
4 — 100/ 100 =100% 100/ 100 =100% 10.0.18.78
0/ 100 = 0% |
5 — 100/ 100 =100% 100/ 100 =100% 10.0.18.29
0/ 100 = 0% |
6 29ms 0/ 100 = 0% 0/ 100 = 0% 4.59.214.141
0/ 100 = 0% |
7 30ms 0/ 100 = 0% 0/ 100 = 0% 4.69.142.178
0/ 100 = 0% |
8 29ms 0/ 100 = 0% 0/ 100 = 0% BLIZZARD-EN.ear7.Chicago2.Level3,net [4.7.196.134]
0/ 100 = 0% |
9 27ms 0/ 100 = 0% 0/ 100 = 0% ae1-br02-eqch2.as57976,net [137.221.69.35]
0/ 100 = 0% |
10 24ms 0/ 100 = 0% 0/ 100 = 0% be2-pe1-eqch2.as57976,net [137.221.69.71]
5/ 100 = 5% |
11 — 100/ 100 =100% 95/ 100 = 95% chi-eqch2-ia-bons-02.as57976,net [137.221.66.11]
0/ 100 = 0% |
12 28ms 5/ 100 = 5% 0/ 100 = 0% 24.105.62.129

Trace complete.

Trace Route to 24.105.62.129 (US Central).

Summary

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 10 ms 8 ms 9 ms 10.73.192.1
2 8 ms 9 ms 10 ms 10.73.192.1
3 28 ms 24 ms 22 ms 10.0.73.109
4 26 ms 16 ms 17 ms 10.0.18.78
5 25 ms 29 ms 21 ms 10.0.18.29
6 24 ms 24 ms 23 ms 4.59.214.141
7 32 ms 31 ms 33 ms 4.69.142.178
8 28 ms 29 ms 30 ms BLIZZARD-EN.ear7.Chicago2.Level3,net [4.7.196.134]
9 29 ms 27 ms 28 ms ae1-br02-eqch2.as57976,net [137.221.69.35]
10 30 ms 28 ms 29 ms be2-pe1-eqch2.as57976,net [137.221.69.71]
11 29 ms 29 ms 35 ms chi-eqch2-ia-bons-02.as57976,net [137.221.66.11]
12 34 ms 29 ms 29 ms 24.105.62.129

Trace complete.

Pathping to 63.240.161.189 (Chicago - Thrall).

Summary

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 DESKTOP-D4O9QEN.cgocable,net [192.168.0.139]
1 Cogeco.local [192.168.0.1]
2 10.73.192.1
3 10.0.73.73
4 10.0.18.78
5 hu0-1-0-0.rcr21.yhm01.atlas.cogentco,com [38.122.17.81]
6 be3317.rcr21.buf02.atlas.cogentco,com [154.54.2.178]
7 be3156.ccr21.cle04.atlas.cogentco,com [154.54.29.201]
8 be2717.ccr41.ord01.atlas.cogentco,com [154.54.6.221]
9 be2765.ccr41.ord03.atlas.cogentco,com [154.54.45.18]
10 att.ord03.atlas.cogentco,com [154.54.12.86]
11 cgcil22crs.ip.att,net [12.122.132.122]
12 gar3.cgcil.ip.att,net [12.122.132.213]
13 12.122.251.22
14 * * *
Computing statistics for 325 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-D4O9QEN.cgocable,net [192.168.0.139]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% Cogeco.local [192.168.0.1]
0/ 100 = 0% |
2 — 100/ 100 =100% 100/ 100 =100% 10.73.192.1
0/ 100 = 0% |
3 — 100/ 100 =100% 100/ 100 =100% 10.0.73.73
0/ 100 = 0% |
4 — 100/ 100 =100% 100/ 100 =100% 10.0.18.78
0/ 100 = 0% |
5 23ms 0/ 100 = 0% 0/ 100 = 0% hu0-1-0-0.rcr21.yhm01.atlas.cogentco,com [38.122.17.81]
0/ 100 = 0% |
6 17ms 0/ 100 = 0% 0/ 100 = 0% be3317.rcr21.buf02.atlas.cogentco,com [154.54.2.178]
0/ 100 = 0% |
7 27ms 0/ 100 = 0% 0/ 100 = 0% be3156.ccr21.cle04.atlas.cogentco,com [154.54.29.201]
0/ 100 = 0% |
8 34ms 0/ 100 = 0% 0/ 100 = 0% be2717.ccr41.ord01.atlas.cogentco,com [154.54.6.221]
0/ 100 = 0% |
9 34ms 0/ 100 = 0% 0/ 100 = 0% be2765.ccr41.ord03.atlas.cogentco,com [154.54.45.18]
0/ 100 = 0% |
10 33ms 0/ 100 = 0% 0/ 100 = 0% att.ord03.atlas.cogentco,com [154.54.12.86]
100/ 100 =100% |
11 — 100/ 100 =100% 0/ 100 = 0% cgcil22crs.ip.att,net [12.122.132.122]
0/ 100 = 0% |
12 — 100/ 100 =100% 0/ 100 = 0% gar3.cgcil.ip.att,net [12.122.132.213]
0/ 100 = 0% |
13 — 100/ 100 =100% 0/ 100 = 0% 12.122.251.22

Trace complete.

Trace Route to 63.240.161.189 (Chicago - Thrall).

Summary

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 1 ms 2 ms 1 ms Cogeco.local [192.168.0.1]
2 13 ms 9 ms 16 ms 10.73.192.1
3 25 ms 24 ms 22 ms 10.0.73.73
4 21 ms 18 ms 16 ms 10.0.18.78
5 23 ms 21 ms 23 ms hu0-1-0-0.rcr21.yhm01.atlas.cogentco,com [38.122.17.81]
6 20 ms 19 ms 20 ms be3317.rcr21.buf02.atlas.cogentco,com [154.54.2.178]
7 26 ms 25 ms 27 ms be3156.ccr21.cle04.atlas.cogentco,com [154.54.29.201]
8 35 ms 36 ms 38 ms be2717.ccr41.ord01.atlas.cogentco,com [154.54.6.221]
9 36 ms 38 ms 35 ms be2765.ccr41.ord03.atlas.cogentco,com [154.54.45.18]
10 35 ms 30 ms 31 ms att.ord03.atlas.cogentco,com [154.54.12.86]
11 34 ms 32 ms 31 ms cgcil22crs.ip.att,net [12.122.132.122]
12 71 ms 58 ms 59 ms gar3.cgcil.ip.att,net [12.122.132.213]
13 31 ms * * 12.122.251.22
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

MTR to 24.105.62.129 (US Central).

Summary

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
Cogeco.local - 0 1883 1883 0 9 42 9
10.73.192.1 - 2 1789 1765 7 12 27 10
10.0.73.109 - 2 1789 1765 19 24 52 25
10.0.18.78 - 2 1789 1765 15 20 53 17
10.0.18.29 - 2 1789 1765 20 26 61 24
4.59.214.141 - 2 1789 1765 21 28 90 24
4.69.142.178 - 33 821 556 0 32 46 32
BLIZZARD-EN.ear7.Chicago2.Level3,net - 2 1789 1765 26 36 465 30
ae1-br02-eqch2.as57976,net - 2 1789 1765 26 35 188 32
be2-pe1-eqch2.as57976,net - 2 1789 1765 27 32 68 30
chi-eqch2-ia-bons-02.as57976,net - 2 1789 1765 28 33 61 32
24.105.62.129 - 2 1777 1750 26 30 44 30
________________________________________________ ______ ______ ______ ______ ______ ______

MTR to 63.240.161.189 (Chicago -Thrall).

Summary

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
Cogeco.local - 0 24 24 1 11 18 11
10.73.192.1 - 0 24 24 8 12 21 11
10.0.73.73 - 0 24 24 20 23 27 23
10.0.18.78 - 0 24 24 15 20 27 18
hu0-1-0-0.rcr21.yhm01.atlas.cogentco,com - 0 24 24 23 25 30 26
be3317.rcr21.buf02.atlas.cogentco,com - 0 24 24 18 21 30 20
be3156.ccr21.cle04.atlas.cogentco,com - 0 24 24 24 26 33 26
be2717.ccr41.ord01.atlas.cogentco,com - 0 24 24 37 40 44 40
be2765.ccr41.ord03.atlas.cogentco,com - 0 24 24 34 38 43 37
att.ord03.atlas.cogentco,com - 0 24 24 29 33 39 32
cgcil22crs.ip.att,net - 0 24 24 30 34 42 34
gar3.cgcil.ip.att,net - 0 24 24 27 52 120 33
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
No response from host - 100 4 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

Thanks for all the help everyone. If there is anything I need to add just let me know.

Have a Happy New Year! :beers: :clinking_glasses:

1 Like
2

Did you use the Wow Looking Glass MTR because that does list all servers once you use the drop-down list and select World of Warcraft

us-looking-glass-battle-net/ replace the two - with .

3

Unless I am blind, I do not see Thrall anywhere…

4

Looks like Blizz screwed up there but since it is in the same Chicago datacenter as Bleeding Hollow so that MTR would show the same route. Yeah I know sort of nuts the EST Servers are no longer in NY.

5

Here is Bleeding Hollow with the lack of Thrall. :grin:

Summary

TRACEROUTE:
traceroute to 67.193.69.110 (67.193.69.110), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.341 ms 0.343 ms 0.343 ms
2 24.105.18.3 (24.105.18.3) 0.556 ms 0.620 ms 0.720 ms
3 137.221.105.12 (137.221.105.12) 1.310 ms 1.339 ms 1.340 ms
4 137.221.66.20 (137.221.66.20) 1.339 ms 1.339 ms 1.337 ms
5 137.221.83.68 (137.221.83.68) 6.397 ms 6.417 ms 6.417 ms
6 137.221.65.68 (137.221.65.68) 5.794 ms 5.867 ms 5.819 ms
7 137.221.68.32 (137.221.68.32) 5.928 ms 6.357 ms 6.368 ms
8 las-b21-link.telia./net (62.115.178.200) 5.853 ms 6.206 ms 6.195 ms
9 * * dls-b23-link.telia./net (62.115.123.136) 35.585 ms
10 kanc-b1-link.telia./net (213.155.130.179) 68.864 ms 66.896 ms 65.968 ms
11 chi-b21-link.telia./net (213.155.130.176) 48.070 ms 48.141 ms 48.098 ms
12 toro-b2-link.telia./net (62.115.118.101) 64.176 ms 63.640 ms 63.623 ms
13 toro-b3-link.telia./net (62.115.117.228) 63.449 ms 63.060 ms 63.040 ms
14 cogeco-ic-337940-toro-b1.c.telia./net (62.115.54.235) 62.920 ms 57.963 ms 57.924 ms
15 * * *

01/01/2020 01:53:30 UTC

TRACEROUTE:
traceroute to 67.193.69.110 (67.193.69.110), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.393 ms 0.405 ms 0.403 ms
2 24.105.18.3 (24.105.18.3) 1.522 ms 1.557 ms 1.572 ms
3 137.221.105.12 (137.221.105.12) 0.903 ms 0.940 ms 0.968 ms
4 137.221.66.20 (137.221.66.20) 1.220 ms 1.318 ms 2.966 ms
5 137.221.83.68 (137.221.83.68) 6.736 ms 6.773 ms 6.785 ms
6 137.221.65.68 (137.221.65.68) 5.776 ms 6.332 ms 6.330 ms
7 137.221.68.32 (137.221.68.32) 6.331 ms 6.341 ms 6.351 ms
8 las-b21-link.telia./net (62.115.178.200) 5.852 ms 5.907 ms 5.927 ms
9 dls-b23-link.telia./net (62.115.123.136) 35.574 ms * *
10 kanc-b1-link.telia./net (213.155.130.179) 48.069 ms 47.869 ms 48.064 ms
11 chi-b21-link.telia./net (213.155.130.176) 48.168 ms 48.044 ms 48.142 ms
12 toro-b2-link.telia./net (62.115.118.101) 58.050 ms 58.222 ms 57.765 ms
13 toro-b3-link.telia./net (62.115.117.228) 58.256 ms 57.929 ms *
14 cogeco-ic-337940-toro-b1.c.telia./net (62.115.54.235) 57.925 ms 57.882 ms 57.921 ms
15 * * *

01/01/2020 01:53:30 UTC

PING:
PING 67.193.69.110 (67.193.69.110) 56(84) bytes of data.
64 bytes from 67.193.69.110: icmp_seq=1 ttl=51 time=78.1 ms
64 bytes from 67.193.69.110: icmp_seq=2 ttl=51 time=74.7 ms
64 bytes from 67.193.69.110: icmp_seq=3 ttl=51 time=74.4 ms
64 bytes from 67.193.69.110: icmp_seq=4 ttl=51 time=74.9 ms

— 67.193.69.110 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 74.405/75.558/78.105/1.483 ms

01/01/2020 01:53:30 UTC

PING:
PING 67.193.69.110 (67.193.69.110) 56(84) bytes of data.
64 bytes from 67.193.69.110: icmp_seq=1 ttl=51 time=79.5 ms
64 bytes from 67.193.69.110: icmp_seq=2 ttl=51 time=75.2 ms
64 bytes from 67.193.69.110: icmp_seq=3 ttl=51 time=77.4 ms
64 bytes from 67.193.69.110: icmp_seq=4 ttl=51 time=74.5 ms

— 67.193.69.110 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 74.545/76.709/79.558/1.984 ms

01/01/2020 01:53:30 UTC

TRACEROUTE:
traceroute to 67.193.69.110 (67.193.69.110), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.263 ms 0.346 ms 0.411 ms
2 24.105.18.3 (24.105.18.3) 0.978 ms 1.114 ms 1.143 ms
3 137.221.105.12 (137.221.105.12) 1.624 ms 1.692 ms 1.706 ms
4 137.221.66.20 (137.221.66.20) 1.713 ms 1.724 ms 1.734 ms
5 137.221.83.68 (137.221.83.68) 5.822 ms 5.892 ms 5.908 ms
6 137.221.65.68 (137.221.65.68) 19.458 ms 21.982 ms 21.982 ms
7 137.221.68.32 (137.221.68.32) 5.887 ms 5.762 ms 5.763 ms
8 las-b21-link.telia./net (62.115.178.200) 5.717 ms 5.741 ms 5.748 ms
9 * * *
10 kanc-b1-link.telia./net (213.155.130.179) 58.608 ms 57.018 ms 57.000 ms
11 chi-b21-link.telia./net (213.155.130.176) 56.965 ms 54.263 ms 53.919 ms
12 toro-b2-link.telia./net (62.115.118.101) 67.810 ms 67.872 ms 67.548 ms
13 toro-b3-link.telia./net (62.115.117.228) 67.430 ms 62.662 ms 58.520 ms
14 cogeco-ic-337940-toro-b1.c.telia./net (62.115.54.235) 58.678 ms 60.736 ms 60.731 ms
15 * * *

01/01/2020 01:53:33 UTC

TRACEROUTE:
traceroute to 67.193.69.110 (67.193.69.110), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.341 ms 0.349 ms 0.355 ms
2 24.105.18.3 (24.105.18.3) 0.491 ms 0.643 ms 0.747 ms
3 137.221.105.12 (137.221.105.12) 0.898 ms 0.928 ms 0.953 ms
4 137.221.66.20 (137.221.66.20) 0.959 ms 0.968 ms 0.975 ms
5 137.221.83.68 (137.221.83.68) 6.669 ms 6.700 ms 6.710 ms
6 137.221.65.68 (137.221.65.68) 25.780 ms 41.191 ms 41.207 ms
7 137.221.68.32 (137.221.68.32) 5.873 ms 5.992 ms 6.000 ms
8 las-b21-link.telia./net (62.115.178.200) 5.812 ms 5.833 ms 5.931 ms
9 * * dls-b23-link.telia./net (62.115.123.136) 35.593 ms
10 kanc-b1-link.telia./net (213.155.130.179) 47.966 ms 49.513 ms 49.676 ms
11 chi-b21-link.telia./net (213.155.130.176) 47.969 ms 48.046 ms 49.369 ms
12 toro-b2-link.telia./net (62.115.118.101) 58.100 ms 58.110 ms 57.949 ms
13 toro-b3-link.telia./net (62.115.117.228) 58.352 ms 57.849 ms 57.933 ms
14 cogeco-ic-337940-toro-b1.c.telia./net (62.115.54.235) 58.769 ms 58.139 ms 58.102 ms
15 * * *

01/01/2020 01:53:35 UTC

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

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

01/01/2020 01:53:34 UTC

PING:
PING 67.193.69.110 (67.193.69.110) 56(84) bytes of data.
64 bytes from 67.193.69.110: icmp_seq=1 ttl=51 time=77.0 ms
64 bytes from 67.193.69.110: icmp_seq=2 ttl=51 time=76.8 ms

— 67.193.69.110 ping statistics —
4 packets transmitted, 2 received, 50% packet loss, time 2997ms
rtt min/avg/max/mdev = 76.821/76.955/77.090/0.308 ms

01/01/2020 01:53:37 UTC

TRACEROUTE:
traceroute to 67.193.69.110 (67.193.69.110), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.353 ms 0.361 ms 0.397 ms
2 24.105.18.3 (24.105.18.3) 0.560 ms 0.652 ms 0.739 ms
3 137.221.105.12 (137.221.105.12) 0.844 ms 0.860 ms 0.988 ms
4 137.221.66.20 (137.221.66.20) 1.127 ms 1.172 ms 1.312 ms
5 137.221.83.68 (137.221.83.68) 32.583 ms 32.614 ms 32.623 ms
6 137.221.65.68 (137.221.65.68) 5.736 ms 5.899 ms 5.896 ms
7 137.221.68.32 (137.221.68.32) 6.195 ms 5.869 ms 5.884 ms
8 las-b21-link.telia./net (62.115.178.200) 5.485 ms 5.624 ms 5.605 ms
9 * dls-b23-link.telia./net (62.115.123.136) 35.396 ms 35.397 ms
10 kanc-b1-link.telia./net (213.155.130.179) 48.503 ms 48.213 ms 48.410 ms
11 chi-b21-link.telia./net (213.155.130.176) 48.152 ms 48.473 ms 48.289 ms
12 toro-b2-link.telia./net (62.115.118.101) 58.067 ms 58.081 ms 57.903 ms
13 toro-b3-link.telia./net (62.115.117.228) 58.012 ms 58.089 ms 58.092 ms
14 cogeco-ic-337940-toro-b1.c.telia./net (62.115.54.235) 58.082 ms 58.090 ms 58.097 ms
15 * * *

01/01/2020 01:53:41 UTC

MTR:
Start: Wed Jan 1 01:53:30 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.7 0.0
2.|-- 24.105.18.3 0.0% 10 0.7 0.7 0.5 1.0 0.0
3.|-- 137.221.105.12 0.0% 10 1.1 0.9 0.6 1.1 0.0
4.|-- 137.221.66.20 0.0% 10 1.2 11.7 1.1 88.7 27.5
5.|-- 137.221.83.68 0.0% 10 3.4 10.8 0.9 65.7 19.6
6.|-- 137.221.65.68 0.0% 10 5.8 9.5 5.8 28.8 7.1
7.|-- 137.221.68.32 0.0% 10 6.0 30.1 6.0 199.7 60.5
8.|-- las-b21-link.telia./net 0.0% 10 5.7 6.4 5.6 11.9 1.8
9.|-- dls-b23-link.telia./net 60.0% 10 35.6 35.5 35.5 35.6 0.0
10.|-- kanc-b1-link.telia./net 0.0% 10 48.8 48.9 48.1 51.6 0.9
11.|-- chi-b21-link.telia./net 0.0% 10 48.6 48.3 48.1 48.6 0.0
12.|-- toro-b2-link.telia./net 0.0% 10 58.1 58.1 58.0 58.3 0.0
13.|-- toro-b3-link.telia./net 0.0% 10 58.1 58.6 57.9 60.9 0.7
14.|-- cogeco-ic-337940-toro-b1.c.telia./net 0.0% 10 58.1 59.1 57.9 67.4 2.8
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- d67-193-69-110.home3.cgocable./net 20.0% 10 76.3 78.0 74.5 85.7 3.6

01/01/2020 01:53:30 UTC

MTR:
Start: Wed Jan 1 01:53:30 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 1.2 0.0
2.|-- 24.105.18.3 0.0% 10 0.5 2.1 0.5 15.7 4.7
3.|-- 137.221.105.12 0.0% 10 0.9 1.2 0.8 3.2 0.7
4.|-- 137.221.66.20 0.0% 10 1.0 7.2 0.9 28.1 11.0
5.|-- 137.221.83.68 0.0% 10 5.6 7.9 3.4 31.0 8.2
6.|-- 137.221.65.68 0.0% 10 5.8 10.2 5.7 44.6 12.2
7.|-- 137.221.68.32 0.0% 10 5.9 28.8 5.9 137.3 42.4
8.|-- las-b21-link.telia./net 0.0% 10 5.7 5.8 5.5 6.0 0.0
9.|-- dls-b23-link.telia./net 80.0% 10 35.7 35.6 35.5 35.7 0.0
10.|-- kanc-b1-link.telia./net 0.0% 10 48.4 50.6 48.1 64.2 5.0
11.|-- chi-b21-link.telia./net 0.0% 10 48.2 48.4 48.0 50.9 0.8
12.|-- toro-b2-link.telia./net 0.0% 10 58.0 58.6 58.0 63.0 1.4
13.|-- toro-b3-link.telia./net 0.0% 10 57.9 58.9 57.9 65.4 2.2
14.|-- cogeco-ic-337940-toro-b1.c.telia./net 0.0% 10 58.0 58.2 57.9 58.4 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- d67-193-69-110.home3.cgocable./net 60.0% 10 74.4 76.1 74.4 79.4 2.2

01/01/2020 01:53:30 UTC

MTR:
Start: Wed Jan 1 01:53:33 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.2 1.3 0.2 8.8 2.6
2.|-- 24.105.18.3 0.0% 10 0.5 1.8 0.5 8.1 2.4
3.|-- 137.221.105.12 0.0% 10 0.9 1.0 0.8 1.3 0.0
4.|-- 137.221.66.20 0.0% 10 1.1 3.2 1.0 20.5 6.1
5.|-- 137.221.83.68 0.0% 10 25.4 7.5 1.0 25.4 7.4
6.|-- 137.221.65.68 0.0% 10 5.9 10.4 5.7 47.6 13.1
7.|-- 137.221.68.32 0.0% 10 5.9 29.7 5.8 238.9 73.5
8.|-- las-b21-link.telia./net 0.0% 10 5.9 5.8 5.4 6.1 0.0
9.|-- dls-b23-link.telia./net 70.0% 10 35.5 35.8 35.5 36.0 0.0
10.|-- kanc-b1-link.telia./net 0.0% 10 48.2 49.1 48.1 52.2 1.2
11.|-- chi-b21-link.telia./net 0.0% 10 48.0 48.1 48.0 48.3 0.0
12.|-- toro-b2-link.telia./net 0.0% 10 58.0 58.2 58.0 58.9 0.0
13.|-- toro-b3-link.telia./net 0.0% 10 58.1 58.1 57.8 58.3 0.0
14.|-- cogeco-ic-337940-toro-b1.c.telia./net 0.0% 10 58.3 58.1 57.8 58.4 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- d67-193-69-110.home3.cgocable./net 20.0% 10 77.0 77.1 74.8 86.4 3.8

01/01/2020 01:53:32 UTC

TRACEROUTE:
traceroute to 67.193.69.110 (67.193.69.110), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.310 ms 0.305 ms 0.314 ms
2 24.105.18.3 (24.105.18.3) 10.939 ms 11.216 ms 11.346 ms
3 137.221.105.12 (137.221.105.12) 1.010 ms 1.061 ms 1.071 ms
4 137.221.66.20 (137.221.66.20) 1.194 ms 1.213 ms 1.233 ms
5 137.221.83.68 (137.221.83.68) 4.872 ms 4.906 ms 5.147 ms
6 137.221.65.68 (137.221.65.68) 5.762 ms 5.831 ms 6.025 ms
7 137.221.68.32 (137.221.68.32) 6.033 ms 6.039 ms 6.305 ms
8 las-b21-link.telia./net (62.115.178.200) 5.941 ms 5.976 ms 5.982 ms
9 dls-b23-link.telia./net (62.115.123.136) 36.938 ms * 35.380 ms
10 kanc-b1-link.telia./net (213.155.130.179) 48.511 ms 48.455 ms 48.082 ms
11 chi-b21-link.telia./net (213.155.130.176) 48.045 ms 48.219 ms 48.337 ms
12 toro-b2-link.telia./net (62.115.118.101) 57.990 ms 58.012 ms 58.134 ms
13 toro-b3-link.telia./net (62.115.117.228) 58.018 ms 58.090 ms 58.109 ms
14 cogeco-ic-337940-toro-b1.c.telia./net (62.115.54.235) 58.178 ms 58.363 ms 57.995 ms
15 * * *

01/01/2020 01:53:46 UTC

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

— 67.193.69.110 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3001ms

01/01/2020 01:53:44 UTC

MTR:
Start: Wed Jan 1 01:53:34 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 24.105.18.3 0.0% 10 0.7 5.6 0.5 50.9 15.9
3.|-- 137.221.105.12 0.0% 10 0.8 0.9 0.7 1.5 0.0
4.|-- 137.221.66.20 0.0% 10 0.8 10.8 0.8 85.0 26.3
5.|-- 137.221.83.68 0.0% 10 6.4 5.2 1.1 9.2 2.8
6.|-- 137.221.65.68 0.0% 10 6.3 9.6 5.6 16.4 4.9
7.|-- 137.221.68.32 0.0% 10 6.0 36.6 5.8 255.6 78.9
8.|-- las-b21-link.telia./net 0.0% 10 6.1 5.8 5.5 6.1 0.0
9.|-- dls-b23-link.telia./net 60.0% 10 35.4 35.5 35.4 35.6 0.0
10.|-- kanc-b1-link.telia./net 0.0% 10 48.7 48.5 48.0 49.4 0.0
11.|-- chi-b21-link.telia./net 0.0% 10 48.2 48.3 48.1 49.4 0.3
12.|-- toro-b2-link.telia./net 0.0% 10 58.0 58.4 58.0 60.8 0.7
13.|-- toro-b3-link.telia./net 0.0% 10 58.4 58.1 57.9 58.4 0.0
14.|-- cogeco-ic-337940-toro-b1.c.telia./net 0.0% 10 58.5 58.2 57.8 58.5 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- d67-193-69-110.home3.cgocable./net 70.0% 10 76.8 77.6 76.8 78.4 0.0

01/01/2020 01:53:34 UTC

PING:
PING 67.193.69.110 (67.193.69.110) 56(84) bytes of data.
64 bytes from 67.193.69.110: icmp_seq=1 ttl=51 time=77.9 ms
64 bytes from 67.193.69.110: icmp_seq=2 ttl=51 time=78.7 ms
64 bytes from 67.193.69.110: icmp_seq=3 ttl=51 time=82.3 ms
64 bytes from 67.193.69.110: icmp_seq=4 ttl=51 time=80.3 ms

— 67.193.69.110 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 77.975/79.843/82.308/1.688 ms

01/01/2020 01:53:48 UTC

MTR:
Start: Wed Jan 1 01:53:39 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.5 0.0
2.|-- 24.105.18.3 0.0% 10 0.5 1.1 0.5 6.3 1.8
3.|-- 137.221.105.12 0.0% 10 1.2 1.0 0.8 1.2 0.0
4.|-- 137.221.66.20 0.0% 10 2.5 5.2 0.9 41.0 12.6
5.|-- 137.221.83.68 0.0% 10 6.5 11.7 3.1 55.6 16.1
6.|-- 137.221.65.68 0.0% 10 5.7 5.8 5.7 6.5 0.0
7.|-- 137.221.68.32 0.0% 10 7.0 6.7 5.9 11.2 1.5
8.|-- las-b21-link.telia./net 0.0% 10 6.2 5.8 5.6 6.2 0.0
9.|-- dls-b23-link.telia./net 70.0% 10 35.3 35.5 35.3 35.6 0.0
10.|-- kanc-b1-link.telia./net 10.0% 10 49.3 49.6 48.2 55.3 2.1
11.|-- chi-b21-link.telia./net 0.0% 10 49.1 48.2 48.0 49.1 0.0
12.|-- toro-b2-link.telia./net 10.0% 10 59.4 58.2 57.9 59.4 0.4
13.|-- toro-b3-link.telia./net 0.0% 10 58.1 58.3 57.9 60.5 0.7
14.|-- cogeco-ic-337940-toro-b1.c.telia./net 0.0% 10 57.8 58.0 57.8 58.4 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

01/01/2020 01:53:39 UTC

MTR:
Start: Wed Jan 1 01:53:46 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 1.4 0.3
2.|-- 24.105.18.3 0.0% 10 0.5 0.6 0.4 0.9 0.0
3.|-- 137.221.105.12 0.0% 10 0.8 0.9 0.6 1.1 0.0
4.|-- 137.221.66.20 0.0% 10 0.9 4.2 0.9 32.4 9.9
5.|-- 137.221.83.68 0.0% 10 16.5 5.9 1.8 16.5 4.0
6.|-- 137.221.65.68 0.0% 10 5.9 6.5 5.7 12.3 2.0
7.|-- 137.221.68.32 0.0% 10 6.3 9.0 5.9 35.6 9.3
8.|-- las-b21-link.telia./net 0.0% 10 5.7 5.7 5.4 6.1 0.0
9.|-- dls-b23-link.telia./net 50.0% 10 35.7 39.3 35.3 54.5 8.5
10.|-- kanc-b1-link.telia./net 10.0% 10 48.1 49.0 48.1 51.4 1.2
11.|-- chi-b21-link.telia./net 10.0% 10 48.5 48.3 48.0 49.4 0.4
12.|-- toro-b2-link.telia./net 0.0% 10 58.2 58.6 58.0 63.0 1.5
13.|-- toro-b3-link.telia./net 0.0% 10 58.2 58.2 57.9 59.1 0.0
14.|-- cogeco-ic-337940-toro-b1.c.telia./net 0.0% 10 58.2 58.9 58.0 65.1 2.1
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- d67-193-69-110.home3.cgocable./net 0.0% 10 80.9 80.4 76.5 84.0 2.7

01/01/2020 01:53:46 UTC

Just want to add, that this lag I’ve been seeing goes beyond what is happening tonight.

6

Are you in Europe because the major loss seems to be happening at Telia nodes?

7

No, not at all…

This is weird. Telia seems to have locations all over the world.

I am assuming there is nothing I can do?

Edit: Wait why is my traffic being routed through Switzerland???

8

So when I run from my end the Trace route to 63.240.161.189 (Chicago) it doesn’t go through Switzerland. However, when the Blizzard server comes to me, with the Look Glass Tool it goes through Amsterdam then to Switzerland back to North America…

Why is this happening?

9

I am getting so confused, why are trace routes going from New York to France? Amsterdam and Switzerland?

Why is traffic being routed this way? North America to Europe then back to North America?

10

There looks to be some packet loss happening between the router and the “10.73.192.1” device. If your router and modem are separate that would be the modem. Or if you’re only using a single networking device within the home, then that may be a network switch (common in apartments and some smaller neighborhoods) outside of the home.

The latency itself doesn’t seem to be very high in any of these so I don’t think it’s a routing issue of any kind. Instead I’m thinking this packet loss is causing the game to have to redo a lot of send/receive data which results in increased numbers in-game.

If you have access to the second hop there I might recommend a power cycle. Alternatively if that device is not within your home it would be best to contact the ISP to see who manages that node (sometimes it’s the apartment complex or similar instead of the ISP).

11
Summary

There looks to be some packet loss happening between the router and the “10.73.192.1” device. If your router and modem are separate that would be the modem. Or if you’re only using a single networking device within the home, then that may be a network switch (common in apartments and some smaller neighborhoods) outside of the home.

The latency itself doesn’t seem to be very high in any of these so I don’t think it’s a routing issue of any kind. Instead I’m thinking this packet loss is causing the game to have to redo a lot of send/receive data which results in increased numbers in-game.

If you have access to the second hop there I might recommend a power cycle. Alternatively if that device is not within your home it would be best to contact the ISP to see who manages that node (sometimes it’s the apartment complex or similar instead of the ISP).

I am already expecting a call back from a real tech from my ISP to talk about it. Thanks for the suggestion and I will let you guys know ASAP.