Can't stay connected to game server


#1

I keep getting booted from the game server, before I can even join a game. I just moved into a new apartment so I don’t know if its something at my new place, or if its something on your end. Help would be much appreciated.
TRACEROUTE:
traceroute to 50.30.173.102 (50.30.173.102), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.384 ms 1.365 ms 1.366 ms
2 24.105.18.3 (24.105.18.3) 1.395 ms 1.410 ms 1.421 ms
3 137.221.105.16 (137.221.105.16) 1.390 ms 1.404 ms 1.416 ms
4 137.221.66.22 (137.221.66.22) 1.421 ms 1.437 ms 1.442 ms
5 137.221.83.68 (137.221.83.68) 11.265 ms 11.273 ms 11.278 ms
6 137.221.65.68 (137.221.65.68) 156.659 ms 373.977 ms 373.964 ms
7 137.221.68.32 (137.221.68.32) 6.073 ms 6.333 ms 6.319 ms
8 las-b21-link.telia. net (62.115.178.200) 6.011 ms 6.131 ms 5.930 ms
9 sjp-brdr-05.inet.qwest. net (63.146.27.249) 5.572 ms 5.578 ms 7.156 ms
10 abq-edge-07.inet.qwest. net (67.14.25.50) 26.614 ms 27.607 ms 27.578 ms
11 65.123.146.254 (65.123.146.254) 47.955 ms 48.140 ms 48.313 ms
12 host-172-1.nmlagro.lascruces.nm.us.clients.pavlovmedia. net (50.30.172.1) 54.310 ms 54.419 ms 54.449 ms
13 * * *
14 * * *
15 * * *

19/08/2019 16:26:48 UTC

TRACEROUTE:
traceroute to 50.30.173.102 (50.30.173.102), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.373 ms 0.398 ms 0.412 ms
2 24.105.18.3 (24.105.18.3) 1.187 ms 1.220 ms 1.249 ms
3 137.221.105.16 (137.221.105.16) 1.192 ms 1.223 ms 1.253 ms
4 137.221.66.22 (137.221.66.22) 1.365 ms 1.396 ms 1.412 ms
5 137.221.83.68 (137.221.83.68) 3.479 ms 3.513 ms 3.526 ms
6 137.221.65.68 (137.221.65.68) 356.592 ms 354.556 ms 354.542 ms
7 137.221.68.32 (137.221.68.32) 28.149 ms 27.694 ms 27.696 ms
8 las-b21-link.telia. net (62.115.178.200) 6.097 ms 6.142 ms 5.918 ms
9 los-brdr-02.inet.qwest. net (63.146.27.249) 5.743 ms 5.561 ms 5.683 ms
10 abq-edge-07.inet.qwest. net (67.14.25.50) 26.786 ms 26.594 ms 26.756 ms
11 65.123.146.254 (65.123.146.254) 35.076 ms 34.364 ms 34.534 ms
12 host-172-1.nmlagro.lascruces.nm.us.clients.pavlovmedia. net (50.30.172.1) 40.701 ms 40.591 ms 40.611 ms
13 * * *
14 * * *
15 * * *

19/08/2019 16:26:48 UTC

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

— 50.30.173.102 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3006ms

19/08/2019 16:26:48 UTC

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

— 50.30.173.102 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3009ms

19/08/2019 16:26:49 UTC

MTR:
Start: Mon Aug 19 16:26:48 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 0.8 0.0
2.|-- 24.105.18.3 0.0% 10 0.7 1.1 0.5 3.7 0.8
3.|-- 137.221.105.16 0.0% 10 0.6 0.7 0.5 1.1 0.0
4.|-- 137.221.66.22 0.0% 10 1.1 1.6 1.0 4.2 0.7
5.|-- 137.221.83.68 0.0% 10 1.4 5.8 1.2 24.1 6.8
6.|-- 137.221.65.68 0.0% 10 5.8 43.4 5.6 175.7 63.1
7.|-- 137.221.68.32 0.0% 10 5.9 6.0 5.9 6.4 0.0
8.|-- las-b21-link.telia. net 0.0% 10 5.8 5.8 5.5 6.2 0.0
9.|-- los-brdr-02.inet.qwest. net 0.0% 10 7.4 7.3 5.5 11.3 2.3
10.|-- abq-edge-07.inet.qwest. net 0.0% 10 26.6 26.7 26.6 27.2 0.0
11.|-- 65.123.146.254 0.0% 10 45.1 34.8 31.7 45.1 4.9
12.|-- host-172-1.nmlagro.lascruces.nm.us.clients.pavlovmedia. net 0.0% 10 46.2 41.9 38.1 55.8 6.3
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

19/08/2019 16:26:48 UTC

MTR:
Start: Mon Aug 19 16:26:48 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.6 0.2 3.1 0.7
2.|-- 24.105.18.3 0.0% 10 0.6 0.7 0.5 1.1 0.0
3.|-- 137.221.105.16 0.0% 10 0.5 0.6 0.5 0.7 0.0
4.|-- 137.221.66.22 0.0% 10 1.0 1.1 0.8 1.6 0.0
5.|-- 137.221.83.68 0.0% 10 15.4 5.7 1.0 15.4 4.1
6.|-- 137.221.65.68 0.0% 10 5.8 44.6 5.7 301.6 91.7
7.|-- 137.221.68.32 0.0% 10 7.4 8.0 5.8 20.0 4.4
8.|-- las-b21-link.telia. net 0.0% 10 5.7 5.7 5.5 6.0 0.0
9.|-- sjp-brdr-05.inet.qwest. net 0.0% 10 8.3 8.4 5.6 12.5 2.4
10.|-- abq-edge-07.inet.qwest. net 0.0% 10 26.6 26.9 26.5 28.4 0.3
11.|-- 65.123.146.254 0.0% 10 39.8 35.6 31.6 49.7 6.4
12.|-- host-172-1.nmlagro.lascruces.nm.us.clients.pavlovmedia. net 0.0% 10 38.2 41.5 38.1 54.3 6.3
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

19/08/2019 16:26:48 UTC


#2

I am having the same issue today


#3

Looks to be a known issue they’re investigating.