Teksavy latency issues, peak hours, throughout the night. UNPLAYABLE

Hey all, I’ve been having some seriously bad latency issues with Teksavy, in the Greater Toronto Area.
It’s making the game unplayable pretty much any time after 5pm for me.
Any help would be greatly appreciated.

Here are the results of my traceroute, pathping, and mtr.
Someone, please shed some light on this.

Tracing route to 137.221.105.2 over a maximum of 30 hops

1 2 ms <1 ms 2 ms Linksys08145 [192.168.1.1]
2 14 ms 11 ms 9 ms 10.196.140.1
3 * * * Request timed out.
4 11 ms 19 ms 19 ms xe-0-3-0-0-agg01-tor.teksavvy.[192.171.63.13]
5 31 ms 17 ms 12 ms ae4-0-bdr01-tor.teksavvy. [206.248.155.94]
6 * 10 ms * ae8-0-bdr01-tor2.teksavvy. [206.248.155.9]
7 * * 30 ms eqix-ix-ny8.blizzard. [198.32.118.87]
8 161 ms 90 ms * ae1-br01-eqny8.as57976. net [137.221.71.33]
9 80 ms 82 ms 79 ms et-0-0-2-br02-eqch2.as57976. net [137.221.65.8]
10 76 ms * * et-0-0-29-br01-eqch2.as57976. net [137.221.65.2]
11 86 ms 100 ms 89 ms 137.221.65.132
12 117 ms 75 ms 77 ms et-0-0-31-pe02-swlv10.as57976. net [137.221.83.69]
13 76 ms 77 ms 88 ms las-swlv10-ia-bons-04.as57976 .net [137.221.66.23]
14 101 ms 130 ms 92 ms 137.221.105.2

Trace complete.

Tracing route to 137.221.105.2 over a maximum of 30 hops

0 Decepticons [192.168.1.127]
1 Linksys08145 [192.168.1.1]
2 10.196.140.1
3 * * *
Computing statistics for 50 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Decepticons [192.168.1.127]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% Linksys08145 [192.168.1.1]
100/ 100 =100% |
2 — 100/ 100 =100% 0/ 100 = 0% 10.196.140.1

Trace complete.

TRACEROUTE:
traceroute to 107.190.97.22 (107.190.97.22), 15 hops max, 60 byte packets
1 Blizzard Blizzard 5.846 ms 8.589 ms 8.619 ms
2 24.105.18.3 (24.105.18.3) 8.630 ms 8.640 ms 8.658 ms
3 137.221.105.12 (137.221.105.12) 11.885 ms 11.908 ms 11.920 ms
4 137.221.66.16 (137.221.66.16) 11.930 ms 11.938 ms 11.947 ms
5 137.221.83.66 (137.221.83.66) 43.671 ms 43.711 ms 43.725 ms
6 137.221.65.133 (137.221.65.133) 126.643 ms 116.427 ms 116.411 ms
7 137.221.69.32 (137.221.69.32) 39.507 ms 39.106 ms 39.122 ms
8 eqix-ch1-ix.teksavvy. com (208.115.136.65) 49.061 ms 49.693 ms 49.694 ms
9 ae1-0-agg01-tor2.teksavvy. com (206.248.155.14) 58.997 ms 59.135 ms 59.127 ms
10 69-196-175-74.dsl.teksavvy. com (69.196.175.74) 61.879 ms 61.960 ms 61.943 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

12/01/2020 06:07:11 UTC

TRACEROUTE:
traceroute to 107.190.97.22 (107.190.97.22), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.362 ms 0.360 ms 0.349 ms
2 24.105.18.3 (24.105.18.3) 1.016 ms 1.030 ms 1.031 ms
3 137.221.105.12 (137.221.105.12) 1.015 ms 1.020 ms 1.020 ms
4 137.221.66.16 (137.221.66.16) 1.087 ms 1.094 ms 1.095 ms
5 137.221.83.66 (137.221.83.66) 38.089 ms 38.103 ms 38.106 ms
6 137.221.65.133 (137.221.65.133) 37.955 ms 38.023 ms 38.128 ms
7 137.221.69.32 (137.221.69.32) 38.081 ms 37.961 ms 38.476 ms
8 eqix-ch1-ix.teksavvy. com (208.115.136.65) 48.073 ms 48.089 ms 48.087 ms
9 ae1-0-agg01-tor2.teksavvy. com (206.248.155.14) 58.907 ms 59.181 ms 59.168 ms
10 69-196-175-74.dsl.teksavvy. com (69.196.175.74) 62.313 ms 61.976 ms 62.211 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

12/01/2020 06:07:11 UTC

TRACEROUTE:
traceroute to 107.190.97.22 (107.190.97.22), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.351 ms 0.310 ms 0.340 ms
2 24.105.18.131 (24.105.18.131) 1.042 ms 1.046 ms 1.046 ms
3 137.221.105.16 (137.221.105.16) 1.043 ms 1.040 ms 1.038 ms
4 137.221.66.22 (137.221.66.22) 1.174 ms 1.193 ms 1.192 ms
5 137.221.83.68 (137.221.83.68) 38.520 ms 38.537 ms 38.539 ms
6 137.221.65.133 (137.221.65.133) 1143.538 ms 1140.435 ms 1360.686 ms
7 137.221.69.32 (137.221.69.32) 38.391 ms 38.259 ms 38.328 ms
8 eqix-ch1-ix.teksavvy. com (208.115.136.65) 48.059 ms 48.247 ms 48.227 ms
9 ae8-0-bdr01-tor2.teksavvy. com (206.248.155.9) 59.798 ms 59.327 ms 59.376 ms
10 ae3-0-agg01-tor2.teksavvy .com (206.248.155.93) 59.028 ms 59.015 ms 58.995 ms
11 69-196-175-182.cpe.teksavvy. com (69.196.175.182) 51.327 ms 51.085 ms 51.043 ms
12 * * *
13 * * *
14 * * *
15 * * *

12/01/2020 06:07:14 UTC

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

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

12/01/2020 06:07:11 UTC

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

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

12/01/2020 06:07:11 UTC

TRACEROUTE:
traceroute to 107.190.97.22 (107.190.97.22), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.858 ms 0.860 ms 0.865 ms
2 24.105.18.131 (24.105.18.131) 2.616 ms 2.621 ms 2.625 ms
3 137.221.105.16 (137.221.105.16) 2.611 ms 2.616 ms 2.619 ms
4 137.221.66.22 (137.221.66.22) 75.220 ms 75.244 ms 75.251 ms
5 137.221.83.68 (137.221.83.68) 42.524 ms 42.531 ms 42.538 ms
6 137.221.65.133 (137.221.65.133) 146.981 ms 143.530 ms 143.489 ms
7 137.221.69.32 (137.221.69.32) 38.953 ms 38.175 ms 38.165 ms
8 eqix-ch1-ix.teksavvy. com (208.115.136.65) 48.165 ms 48.141 ms 48.151 ms
9 ae8-0-bdr01-tor2.teksavvy. com (206.248.155.9) 61.054 ms 73.482 ms 73.484 ms
10 ae3-0-agg01-tor2.teksavvy. com (206.248.155.93) 59.029 ms 59.198 ms 59.214 ms
11 69-196-175-182.cpe.teksavvy. com (69.196.175.182) 51.068 ms 51.164 ms 50.979 ms
12 * * *
13 * * *
14 * * *
15 * * *

12/01/2020 06:07:16 UTC

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

— 107.190.97.22 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3007ms

12/01/2020 06:07:16 UTC

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

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

12/01/2020 06:07:19 UTC

TRACEROUTE:
traceroute to 107.190.97.22 (107.190.97.22), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.313 ms 0.313 ms 0.382 ms
2 24.105.18.131 (24.105.18.131) 0.610 ms 0.695 ms 0.833 ms
3 137.221.105.16 (137.221.105.16) 0.921 ms 0.936 ms 0.940 ms
4 137.221.66.22 (137.221.66.22) 1.050 ms 1.121 ms 2.605 ms
5 137.221.83.68 (137.221.83.68) 38.192 ms 38.214 ms 38.235 ms
6 137.221.65.133 (137.221.65.133) 38.052 ms 38.141 ms 38.089 ms
7 137.221.69.32 (137.221.69.32) 38.349 ms 38.184 ms 38.215 ms
8 eqix-ch1-ix.teksavvy. com (208.115.136.65) 48.151 ms 48.363 ms 48.336 ms
9 ae8-0-bdr01-tor2.teksavvy. com (206.248.155.9) 62.702 ms 62.447 ms 62.441 ms
10 ae3-0-agg01-tor2.teksavvy. com (206.248.155.93) 59.009 ms 58.915 ms 58.964 ms
11 69-196-175-182.cpe.teksavvy. com (69.196.175.182) 51.217 ms 51.240 ms 50.912 ms
12 * * *
13 * * *
14 * * *
15 * * *

12/01/2020 06:07:24 UTC

MTR:
Start: Sun Jan 12 06:07:11 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.4 0.0
2.|-- 24.105.18.3 0.0% 10 15.9 6.0 0.5 19.8 7.5
3.|-- 137.221.105.12 0.0% 10 0.9 1.1 0.8 2.9 0.6
4.|-- 137.221.66.16 0.0% 10 1.3 4.9 0.9 35.9 10.9
5.|-- 137.221.83.66 0.0% 10 38.1 45.1 37.8 74.3 12.7
6.|-- 137.221.65.133 0.0% 10 63.0 603.8 63.0 1429. 442.9
7.|-- 137.221.69.32 0.0% 10 38.3 40.4 37.9 61.1 7.2
8.|-- eqix-ch1-ix.teksavvy .com 0.0% 10 49.5 48.6 48.0 50.7 0.7
9.|-- ae1-0-agg01-tor2.teksavvy. com 0.0% 10 58.9 59.1 58.9 59.3 0.0
10.|-- 69-196-175-74.dsl.teksavvy. com 0.0% 10 62.2 62.1 61.8 62.4 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

12/01/2020 06:07:11 UTC

MTR:
Start: Sun Jan 12 06:07:11 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.4 0.0
2.|-- 24.105.18.3 0.0% 10 0.5 0.6 0.5 1.2 0.0
3.|-- 137.221.105.12 0.0% 10 0.7 1.2 0.7 4.3 1.1
4.|-- 137.221.66.16 0.0% 10 0.9 5.2 0.9 41.6 12.8
5.|-- 137.221.83.66 0.0% 10 38.0 45.2 37.9 75.0 15.1
6.|-- 137.221.65.133 0.0% 10 224.0 627.8 49.6 1370. 423.8
7.|-- 137.221.69.32 0.0% 10 38.1 46.4 38.0 83.9 17.0
8.|-- eqix-ch1-ix.teksavvy. com 0.0% 10 48.3 49.8 48.1 62.2 4.3
9.|-- ae1-0-agg01-tor2.teksavvy. com 0.0% 10 59.0 59.0 58.9 59.2 0.0
10.|-- 69-196-175-74.dsl.teksavvy. com 0.0% 10 62.0 62.4 61.8 65.0 0.7
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

12/01/2020 06:07:11 UTC

TRACEROUTE:
traceroute to 107.190.97.22 (107.190.97.22), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.301 ms 0.313 ms 0.427 ms
2 24.105.18.131 (24.105.18.131) 1.046 ms 1.101 ms 1.218 ms
3 137.221.105.16 (137.221.105.16) 1.227 ms 1.234 ms 1.241 ms
4 137.221.66.22 (137.221.66.22) 1.181 ms 1.209 ms 1.217 ms
5 137.221.83.68 (137.221.83.68) 38.128 ms 38.353 ms 38.378 ms
6 137.221.65.133 (137.221.65.133) 37.894 ms 38.017 ms 38.014 ms
7 137.221.69.32 (137.221.69.32) 38.176 ms 38.051 ms 38.028 ms
8 eqix-ch1-ix.teksavvy. com (208.115.136.65) 48.108 ms 48.132 ms 48.135 ms
9 ae8-0-bdr01-tor2.teksavvy. com (206.248.155.9) 60.232 ms 60.332 ms 60.465 ms
10 ae3-0-agg01-tor2.teksavvy. com (206.248.155.93) 59.944 ms 58.876 ms 58.980 ms
11 69-196-175-182.cpe.teksavvy. com (69.196.175.182) 50.997 ms 51.364 ms 51.125 ms
12 * * *
13 * * *
14 * * *
15 * * *

12/01/2020 06:07:27 UTC

MTR:
Start: Sun Jan 12 06:07:14 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- 24.105.18.3 0.0% 10 0.5 0.6 0.5 0.7 0.0
3.|-- 137.221.105.12 0.0% 10 0.8 0.9 0.7 1.1 0.0
4.|-- 137.221.66.16 0.0% 10 11.5 2.0 0.8 11.5 3.3
5.|-- 137.221.83.66 0.0% 10 37.9 38.6 37.9 44.6 2.0
6.|-- 137.221.65.133 0.0% 10 38.0 408.3 38.0 1269. 416.3
7.|-- 137.221.69.32 0.0% 10 38.3 40.2 37.9 57.9 6.2
8.|-- eqix-ch1-ix.teksavvy. com 0.0% 10 54.0 48.9 48.0 54.0 1.8
9.|-- ae1-0-agg01-tor2.teksavvy. com 0.0% 10 60.7 59.1 58.9 60.7 0.5
10.|-- 69-196-175-74.dsl.teksavvy. com 0.0% 10 62.3 62.1 61.8 62.3 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

12/01/2020 06:07:14 UTC

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

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

12/01/2020 06:07:26 UTC

MTR:
Start: Sun Jan 12 06:07:16 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.6 0.0
2.|-- 24.105.18.131 0.0% 10 0.8 2.0 0.6 12.3 3.6
3.|-- 137.221.105.16 0.0% 10 1.0 1.0 0.8 1.1 0.0
4.|-- 137.221.66.22 0.0% 10 10.3 8.3 0.9 60.5 18.6
5.|-- 137.221.83.68 0.0% 10 39.1 40.4 38.1 59.6 6.7
6.|-- 137.221.65.133 0.0% 10 38.1 254.2 38.0 841.2 323.1
7.|-- 137.221.69.32 0.0% 10 38.2 41.6 38.2 69.1 9.7
8.|-- eqix-ch1-ix.teksavvy. com 0.0% 10 48.6 48.7 48.1 52.3 1.1
9.|-- ae8-0-bdr01-tor2.teksavvy. com 0.0% 10 59.4 61.4 59.0 76.9 5.5
10.|-- ae3-0-agg01-tor2.teksavvy. com 0.0% 10 59.8 58.4 51.5 59.8 2.4
11.|-- 69-196-175-182.cpe.teksavvy. com 10.0% 10 51.2 51.9 51.0 57.1 1.9
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

12/01/2020 06:07:16 UTC

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

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

12/01/2020 06:07:29 UTC

MTR:
Start: Sun Jan 12 06:07:22 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.6 0.0
2.|-- 24.105.18.131 0.0% 10 0.8 0.6 0.5 0.8 0.0
3.|-- 137.221.105.16 0.0% 10 1.0 1.4 0.8 4.5 1.1
4.|-- 137.221.66.22 0.0% 10 1.1 3.6 1.0 19.1 5.6
5.|-- 137.221.83.68 0.0% 10 38.1 41.7 37.8 62.6 8.3
6.|-- 137.221.65.133 10.0% 10 5221. 1208. 38.0 5221. 1971.2
7.|-- 137.221.69.32 0.0% 10 38.3 39.9 38.0 55.0 5.3
8.|-- eqix-ch1-ix.teksavvy. com 0.0% 10 48.2 48.8 48.0 53.4 1.6
9.|-- ae8-0-bdr01-tor2.teksavvy. com 0.0% 10 70.8 60.7 59.1 70.8 3.5
10.|-- ae3-0-agg01-tor2.teksavvy. com 0.0% 10 59.1 58.4 51.4 60.0 2.4
11.|-- 69-196-175-182.cpe.teksavvy. com 20.0% 10 51.5 51.4 50.9 52.3 0.4
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

12/01/2020 06:07:21 UTC

MTR:
Start: Sun Jan 12 06:07:27 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.6 0.3 2.6 0.6
2.|-- 24.105.18.131 0.0% 10 22.9 5.1 0.5 22.9 8.3
3.|-- 137.221.105.16 0.0% 10 0.7 1.2 0.7 3.6 0.7
4.|-- 137.221.66.22 0.0% 10 1.0 6.5 1.0 50.5 15.5
5.|-- 137.221.83.68 0.0% 10 55.4 40.7 38.0 55.4 5.6
6.|-- 137.221.65.133 40.0% 10 8435. 4778. 117.6 8435. 3003.8
7.|-- 137.221.69.32 0.0% 10 38.0 42.3 38.0 70.6 10.1
8.|-- eqix-ch1-ix.teksavvy. com 0.0% 10 48.1 50.2 48.0 56.0 2.6
9.|-- ae8-0-bdr01-tor2.teksavvy. com 0.0% 10 59.4 60.2 59.3 62.4 0.7
10.|-- ae3-0-agg01-tor2.teksavvy. com 0.0% 10 63.0 59.4 58.9 63.0 1.2
11.|-- 69-196-175-182.cpe.teksavvy. com 0.0% 10 51.3 51.3 50.9 52.2 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

12/01/2020 06:07:27 UTC

Please, anything is appreciated. I’m getting to the point of telling Teksavy off.

I have all the required ports forwarded as well.

Hey Skeltah,

If the issue is only happening in the evening “prime time” hours then it’s likely a congestion issue somewhere between the ISP and the Blizzard network. It could be in the Teksavy network but it may not be. I see some signs of packet loss on the Teksavvy network, but it’s not totally conclusive in order to tell you where exactly the issue is occurring based off the connection data you provided. It does sound like some kind of congestion is happening which is causing the high latency.

Have you tried testing a different network connection? Using a mobile tether or hotspot? Or perhaps connecting through a free VPN to test and see if the issues go away? If a mobile data connection or a VPN works around the issue that is generally a solid method to determine if it’s only affecting your home ISP connection.

Thanks for the advice. I’ll check tonight and get back with the results.

Wasn’t able to tether my phone, however, the vpn did not work.
My ping was incredibly high last night. 1700ms. Not sure what else to do, short of cancelling my service and waiting the 2 weeks for a new isp to come around.

1 Like

Skeltah,

If you’d like we can take a look at the current connection path from you to us instead. Using your normal connection, run WinMTR while having issues - it’ll let us see if anything interesting shows up during the period the issues are happening. You want to restart the test every 10-15 minutes until you catch one of these problems. Once you’ve caught one red handed, run the test for about 5 more minutes. This will let us look for problems between your house and our servers which may cause this.

If you have problems with posting it due to a link error, go ahead and copy paste this into your next post, and replace “WinMTR goes here” with your test.

~~~~
WinMTR goes here
~~~~

I have fixed the problem.
It turns out, the lines running outside my place, on the street were losing signal.
The isp sent someone to repair them, and everything is holding steady.
Thanks for your help.