Keep disconnecting after several games

Hi there,

Recently, I kept disconnecting from the server after playing several games. Normally I can have two to three games with no lag. But somehow, I will suddenly not be able to connect to a server when finding a game. Then I get banned for 15 mins and -50 pts. Today I get banned for 60 mins and again -50pts…

It’s really annoying.

I found a test to do by searching in Google and here are the test results:

TRACEROUTE:
traceroute to 70.27.213.36 (70.27.213.36), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.368 ms 0.373 ms 0.381 ms
2 24.105.18.130 (24.105.18.130) 1.341 ms 1.368 ms 1.393 ms
3 137.221.105.14 (137.221.105.14) 1.363 ms 1.374 ms 1.375 ms
4 137.221.66.18 (137.221.66.18) 0.806 ms 0.836 ms 0.848 ms
5 137.221.83.82 (137.221.83.82) 55.134 ms 275.056 ms 275.102 ms
6 * * *
7 137.221.65.1 (137.221.65.1) 203.853 ms 203.887 ms 203.901 ms
8 137.221.65.7 (137.221.65.7) 30.167 ms 38.077 ms 38.079 ms
9 137.221.65.116 (137.221.65.116) 38.024 ms 31.375 ms 31.376 ms
10 137.221.65.41 (137.221.65.41) 30.146 ms 30.088 ms 30.123 ms
11 137.221.73.32 (137.221.73.32) 30.437 ms 30.455 ms 30.405 ms
12 bx5-seattle_be10.net.bell.ca (184.150.180.234) 30.415 ms 30.140 ms 30.150 ms
13 tcore4-seattle_bundle-ether4.net.bell.ca (64.230.125.246) 81.235 ms 84.488 ms 84.183 ms
14 tcore4-vancouverbg_hundredgige0-5-0-0.net.bell.ca (64.230.79.99) 80.225 ms 82.960 ms 82.974 ms
15 tcore4-toronto63_hundredgige1-3-0-0.net.bell.ca (64.230.79.60) 81.435 ms 81.442 ms 81.753 ms

28/10/2020 00:57:53 UTC

TRACEROUTE:
traceroute to 70.27.213.36 (70.27.213.36), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.426 ms 0.404 ms 0.400 ms
2 37.244.23.131 (37.244.23.131) 0.675 ms 0.705 ms 0.871 ms
3 24.105.62.152 (24.105.62.152) 4.130 ms 4.152 ms 4.153 ms
4 137.221.66.10 (137.221.66.10) 2.128 ms 2.148 ms 2.149 ms
5 * * *
6 137.221.69.34 (137.221.69.34) 2.188 ms 2.381 ms 2.352 ms
7 bx6-chicagodt_be14.net.bell.ca (184.150.181.56) 2.405 ms 2.764 ms 2.840 ms
8 tcore4-chicagocp_0-10-0-0.net.bell.ca (64.230.79.86) 30.761 ms 30.772 ms 30.774 ms
9 tcore4-toronto63_hundredgige1-2-0-0.net.bell.ca (64.230.79.154) 29.206 ms 29.231 ms 24.444 ms
10 tcore4-montreal02_1-2-0-0.net.bell.ca (64.230.79.37) 33.235 ms 28.871 ms 28.839 ms
11 dis75-montreal02_7-1-0.net.bell.ca (64.230.91.45) 26.452 ms 26.473 ms 26.474 ms
12 * * *
13 mtrlpq4385w-70-27-212-1.dsl.bell.ca (70.27.212.1) 25.050 ms 25.736 ms 25.773 ms
14 * * *
15 * * *

28/10/2020 00:57:53 UTC

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

— 70.27.213.36 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3010ms

28/10/2020 00:57:53 UTC

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

— 70.27.213.36 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2997ms

28/10/2020 00:57:53 UTC

MTR:
Start: Wed Oct 28 00:57:53 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.6 0.0
2.|-- 37.244.23.131 0.0% 10 0.5 0.6 0.4 0.9 0.0
3.|-- 24.105.62.152 0.0% 10 0.9 0.9 0.6 1.2 0.0
4.|-- 137.221.66.10 0.0% 10 1.9 2.0 1.8 2.5 0.0
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.34 0.0% 10 2.0 6.9 1.9 39.3 11.9
7.|-- bx6-chicagodt_be14.net.bell.ca 0.0% 10 2.1 2.3 2.1 2.6 0.0
8.|-- tcore4-chicagocp_0-10-0-0.net.bell.ca 0.0% 10 30.8 30.9 28.0 34.0 2.0
9.|-- tcore4-toronto63_hundredgige1-2-0-0.net.bell.ca 0.0% 10 29.4 28.3 24.9 32.0 2.5
10.|-- tcore4-montreal02_1-2-0-0.net.bell.ca 0.0% 10 30.6 30.6 27.9 33.8 2.1
11.|-- dis75-montreal02_7-1-0.net.bell.ca 0.0% 10 24.0 24.0 23.8 24.1 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- mtrlpq4385w-70-27-212-1.dsl.bell.ca 0.0% 10 25.3 25.2 25.0 25.3 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

28/10/2020 00:57:53 UTC

MTR:
Start: Wed Oct 28 00:57:53 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.5 0.0
2.|-- 24.105.18.130 0.0% 10 0.6 0.7 0.6 1.1 0.0
3.|-- 137.221.105.14 0.0% 10 1.0 1.0 0.9 1.2 0.0
4.|-- 137.221.66.18 0.0% 10 0.5 5.1 0.5 45.4 14.1
5.|-- 137.221.83.82 0.0% 10 949.2 763.2 58.8 1296. 349.1
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.65.1 0.0% 10 418.6 196.0 56.1 418.6 121.6
8.|-- 137.221.65.7 0.0% 10 30.5 32.5 30.0 52.4 7.0
9.|-- 137.221.65.116 0.0% 10 30.4 33.5 30.0 48.4 6.9
10.|-- 137.221.65.41 0.0% 10 31.3 37.0 30.2 75.6 15.0
11.|-- 137.221.73.32 0.0% 10 30.4 35.7 30.3 60.6 10.8
12.|-- bx5-seattle_be10.net.bell.ca 0.0% 10 30.5 30.7 30.2 31.9 0.3
13.|-- tcore4-seattle_bundle-ether4.net.bell.ca 0.0% 10 84.3 83.8 79.9 86.9 2.1
14.|-- tcore4-vancouverbg_hundredgige0-5-0-0.net.bell.ca 0.0% 10 82.8 81.6 79.5 83.7 1.1
15.|-- tcore4-toronto63_hundredgige1-3-0-0.net.bell.ca 0.0% 10 82.7 80.8 79.3 82.7 0.9
16.|-- tcore4-montreal02_1-2-0-0.net.bell.ca 0.0% 10 80.3 78.6 76.9 80.3 0.9
17.|-- dis75-montreal02_7-1-0.net.bell.ca 0.0% 10 79.1 79.1 78.9 79.5 0.0
18.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
19.|-- mtrlpq4385w-70-27-212-1.dsl.bell.ca 0.0% 10 77.6 77.6 77.3 78.3 0.0
20.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

28/10/2020 00:57:53 UTC

Thanks in advance,

ErgA

Unfortunately, this test only monitors what is happening the moment you run it. The majority of it looks okay, but the ping statistics are a bit concerning. Instead, you’d want to use the WinMTR mentioned in the pinned threads.

I think with the WinMTR we’ll see some lag spikes on your ISP network, since the first test hints at some larger ping values than the later tests do.