8/19 - Connection to server lost / Unable to connect

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.8.1
2 * * * Request timed out.
3 45 ms 34 ms 41 ms 10.98.15.5
4 66 ms 41 ms 35 ms 10.98.22.25
5 * * * Request timed out.
6 52 ms 30 ms 38 ms 192.168.20.2
7 45 ms 34 ms 51 ms 192.168.20.30
8 44 ms 57 ms 172 ms 200.29.35.1
9 50 ms 48 ms 61 ms 213.140.39.160
10 133 ms 153 ms 135 ms 94.142.122.31
11 192 ms 179 ms 181 ms 5.53.4.135
12 244 ms 184 ms 167 ms 81.173.106.21
13 * * * Request timed out.
14 * 191 ms 184 ms et-0-0-2-br01-eqch2.as57976.net [137.221.65.13]
15 238 ms 181 ms 175 ms be1-pe01-eqch2.as57976.net [137.221.69.67]
16 199 ms 176 ms 185 ms 24.105.62.129

Trace complete.

TRACEROUTE:
traceroute to 106.51.20.37 (106.51.20.37), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.659 ms 0.649 ms 0.648 ms
2 24.105.18.131 (24.105.18.131) 18.370 ms 18.385 ms 18.385 ms
3 137.221.105.16 (137.221.105.16) 0.597 ms 1.481 ms 1.499 ms
4 137.221.66.18 (137.221.66.18) 1.505 ms 1.509 ms 1.509 ms
5 137.221.83.66 (137.221.83.66) 4.458 ms 4.472 ms 4.474 ms
6 137.221.65.68 (137.221.65.68) 184.409 ms 182.814 ms 182.800 ms
7 137.221.68.32 (137.221.68.32) 6.206 ms 6.201 ms 6.199 ms
8 las-b21 -link.telia.net (62.115.178.200) 6.115 ms 6.109 ms 6.107 ms
9 las-b24 -link.telia.net (62.115.136.47) 5.797 ms 7.166 ms 7.161 ms
10 80.239.128.215 (80.239.128.215) 5.935 ms 5.759 ms 6.654 ms
11 if-ae -2-2.tcore2.lvw-los-angeles.as6453.net (66.110.59.2) 178.441 ms 178.481 ms 178.496 ms
12 if- ae-7-2.tcore 2.svw-singa pore.as6 453. net (180.87.15.25) 185.994 ms 186.024 ms 184.918 ms
13 180.87.84.79 (180.87.84.79) 230.872 ms 230.897 ms 231.080 ms
14 * * *
15 14.141.145.94.static-Bangalore.vsnl.net.in (14.141.145.94) 240.278 ms 247.360 ms 247.467 ms

19/08/2019 21:32:02 UTC

TRACEROUTE:
traceroute to 106.51.20.37 (106.51.20.37), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.461 ms 0.440 ms 0.429 ms
2 24.105.18.131 (24.105.18.131) 4.269 ms 4.322 ms 4.347 ms
3 137.221.105.16 (137.221.105.16) 4.295 ms 4.320 ms 4.345 ms
4 137.221.66.18 (137.221.66.18) 12.062 ms 12.066 ms 12.076 ms
5 137.221.83.66 (137.221.83.66) 5.107 ms 5.130 ms 5.138 ms
6 137.221.65.68 (137.221.65.68) 407.058 ms 405.015 ms 405.016 ms
7 137.221.68.32 (137.221.68.32) 7.668 ms 6.488 ms 6.513 ms
8 las-b21-l ink.telia.ne t (62.115.178.200) 6.477 ms 6.502 ms 6.160 ms
9 las-b24-link.telia.ne t (62.115.136.47) 6.222 ms 6.241 ms 6.261 ms
10 80.239.128.215 (80.239.128.215) 6.178 ms 6.191 ms 7.185 ms
11 if-ae-2-2.tcore2.lvw-los-angeles.as6453.ne t (66.110.59.2) 177.612 ms 177.314 ms 177.340 ms
12 if-ae-7-2.tcore2.svw-singapore.as6453.ne t (180.87.15.25) 185.975 ms 186.004 ms 185.995 ms
13 180.87.84.79 (180.87.84.79) 230.877 ms 230.889 ms 231.016 ms
14 * * *
15 14.141.145.94.static-Bangalore.vsnl.net.in (14.141.145.94) 243.859 ms 256.815 ms 256.536 ms

19/08/2019 21:32:02 UTC

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

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

19/08/2019 21:32:02 UTC

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

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

19/08/2019 21:32:02 UTC

MTR:
Start: Mon Aug 19 21:32:01 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.5 0.6 0.5 0.8 0.0
3.|-- 137.221.105.16 0.0% 10 0.4 0.6 0.4 0.8 0.0
4.|-- 137.221.66.18 0.0% 10 1.2 1.3 0.9 2.6 0.3
5.|-- 137.221.83.66 0.0% 10 7.2 13.2 4.1 49.5 13.8
6.|-- 137.221.65.68 0.0% 10 5.8 91.6 5.7 538.4 164.1
7.|-- 137.221.68.32 0.0% 10 6.3 21.7 5.8 119.8 35.8
8.|-- las-b21-link.telia.ne t 0.0% 10 5.7 6.1 5.6 8.6 0.7
9.|-- las-b24-link.telia.ne t 0.0% 10 5.8 8.2 5.5 27.3 6.7
10.|-- 80.239.128.215 0.0% 10 5.7 5.7 5.6 5.9 0.0
11.|-- if-ae-2-2.tcore2.lvw-los-angeles.as6453.ne t 0.0% 10 177.3 177.5 177.3 177.9 0.0
12.|-- if-ae-7-2.tcore2.svw-singapore.as6453.ne t 0.0% 10 185.0 185.0 184.9 185.3 0.0
13.|-- 180.87.84.79 0.0% 10 230.9 230.9 230.8 231.2 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- 14.141.145.94.static-Bangalore.vsnl.net.in 0.0% 10 253.9 241.4 238.7 253.9 4.9
16.|-- broadband.actcorp.in 0.0% 10 239.3 239.0 238.8 239.6 0.0
17.|-- broadband.actcorp.in 0.0% 10 239.0 238.8 238.6 239.3 0.0
18.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

19/08/2019 21:32:01 UTC

MTR:
Start: Mon Aug 19 21:32:02 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.5 0.3 1.8 0.3
2.|-- 24.105.18.131 0.0% 10 0.6 5.2 0.5 47.3 14.8
3.|-- 137.221.105.16 0.0% 10 0.6 0.9 0.5 2.7 0.6
4.|-- 137.221.66.18 0.0% 10 0.9 5.0 0.9 38.8 11.9
5.|-- 137.221.83.66 0.0% 10 104.7 17.5 0.9 104.7 31.3
6.|-- 137.221.65.68 0.0% 10 102.7 72.5 5.8 423.5 131.4
7.|-- 137.221.68.32 0.0% 10 6.1 6.0 5.8 6.3 0.0
8.|-- las-b21-link.telia.ne t 0.0% 10 6.0 5.9 5.6 6.7 0.0
9.|-- las-b24-link.telia.ne t 0.0% 10 5.6 6.1 5.6 9.4 1.0
10.|-- 80.239.128.215 0.0% 10 5.6 6.1 5.6 6.8 0.0
11.|-- if-ae-2-2.tcore2.lvw-los-angeles.as6453.ne t 90.0% 10 177.5 177.5 177.5 177.5 0.0
12.|-- if-ae-7-2.tcore2.svw-singapore.as6453.ne t 0.0% 10 184.9 185.3 184.9 187.7 0.7
13.|-- 180.87.84.79 0.0% 10 230.9 234.4 230.8 260.1 9.2
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- 14.141.145.94.static-Bangalore.vsnl.net.in 0.0% 10 238.9 239.2 238.7 241.0 0.3
16.|-- broadband.actcorp.in 0.0% 10 238.7 239.0 238.6 240.2 0.0
17.|-- broadband.actcorp.in 0.0% 10 238.8 238.9 238.3 240.7 0.5
18.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

19/08/2019 21:32:02 UTC

Hope you guys manage to figure this out…
(I have added an * to the end of urls so I can post this)

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 4 ms 2 ms 3 ms 192.168.0.1
2 12 ms 10 ms 15 ms 71-38-192-254.lsv2.qwest.net [71.38.192.254]
3 13 ms 10 ms 13 ms lsv2-agw1.inet.qwest.ne
t [75.160.224.1]
4 12 ms 11 ms 14 ms 75-163-31-254.lsv2.qwest.net [75.163.31.254]
5 * * * Request timed out.
6 16 ms 17 ms 17 ms BLIZZARD-EN.ear3.LosAngeles1.Level3.ne
t [4.71.135.106]
7 19 ms 21 ms 17 ms ae1-br02-eqla1.as57976.net [137.221.68.35]
8 18 ms 19 ms 21 ms be2-pe01-eqla1.as57976.ne
t [137.221.68.71]
9 18 ms 24 ms 18 ms 24.105.30.129

Trace complete.

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.17.75.1
2 <1 ms <1 ms <1 ms 10.6.20.1
3 8 ms 6 ms 7 ms 47.200.0.1
4 9 ms 10 ms 8 ms 172.99.44.28
5 16 ms 16 ms 16 ms [74.40.3.73]
6 16 ms 13 ms 19 ms [74.40.1.126]
7 * * * Request timed out.
8 * * 14 ms [4.69.207.21]
9 13 ms 16 ms 18 ms [4.16.176.198]
10 * * * Request timed out.
11 * * * Request timed out.
12 * 80 ms 100 ms [137.221.65.46]
13 51 ms 48 ms 50 ms [137.221.69.71]
14 51 ms 49 ms 50 ms 24.105.62.129

Trace complete.

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 188 ms 184 ms 184 ms 24.105.62.129

Trace complete.

Hey all,

Just to provide some more information and a work around, we’ve identified that this is an ISP issue and we’re doing everything we can on our end to fix it. Because it is an ISP issue rather than a server issue, most players can connect using a VPN client (or mobile hotspot/tether). We can’t recommend any or support this directly because they can cause other connection errors of their own, but if you’re itching to get in ASAP, there are plenty out there you can try.

Thanks for all the tests and reports so far, either way!

2 Likes

Hi there, I’ve done the trace-route thing but I think that is not the Issue, I’ve done some debugging on my own by using an internal VPN (I’m the IT support guy for my company so I have a VPN), the results are as follows:

  1. At 3:56 GMT-5 (Bogota’s time) tried to connect using the normal connection (from IP 200.71.58.157), I can get into the menu but after a few seconds I got disconnected so I did the traceroute:

    Tracing route to 24.105.62.129 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 192.168.10.1
    2 18 ms 54 ms 21 ms [200.71.58.1]
    3 19 ms 36 ms 21 ms 172.21.16.98
    4 60 ms 60 ms 56 ms 10.14.18.25
    5 87 ms 89 ms 85 ms [213.248.70.68]
    6 * * 98 ms [62.115.113.48]
    7 86 ms 86 ms 88 ms [62.115.113.24]
    8 108 ms 113 ms 106 ms [62.115.113.19]
    9 110 ms 112 ms 140 ms [62.115.178.249]
    10 117 ms 114 ms 110 ms [137.221.69.33]
    11 122 ms 121 ms 120 ms [137.221.69.69]
    12 112 ms 129 ms 111 ms [137.221.66.15]
    13 112 ms 114 ms 115 ms 24.105.62.129

    Trace complete.

After trying this I realized it might be an issue with blizzard servers so I decided to connect with the aforementioned VPN, so let’s go straight to the second point.

  1. At 04:30 PM GMT-5, I’ve got connected through the VPN (with IP 201.184.76.130), so not only I was able to get into the menu but also I played a QP game and after that game ended I did the same traceroute with this result:

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 103 ms 101 ms 104 ms 192.168.1.120
2 * * * Request timed out.
3 * * * Request timed out.
4 105 ms 107 ms 170 ms 10.166.10.14
5 124 ms 115 ms 135 ms 10.166.10.13
6 122 ms 127 ms 126 ms [200.24.34.86]
7 157 ms 169 ms 156 ms [200.24.33.90]
8 152 ms 150 ms 153 ms 206.41.108.97
9 183 ms 183 ms 196 ms [137.221.76.33]
10 179 ms 183 ms 179 ms [137.221.65.50]
11 187 ms 187 ms 185 ms [137.221.65.46]
12 189 ms 190 ms 185 ms [137.221.69.73]
13 214 ms 219 ms 186 ms 24.105.62.129

Trace complete.

so after this test, I’m almost secure the issue is with the firewall on the server or the anti-cheating or anti-hacking system which somehow is disconnecting me when I connect with the 1st method I’ve mentioned here.

btw if needed, I was logging in with my other account lordsaitama#1919.

I could try to play with the VPN but I can’t because the ping goes by 200+ms so it won’t be an enjoyable experience.

Thanks. (hope someone from support staff reads this).

UK servers are working fine for me. Just not US servers

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms modem.domain [192.168.0.1]
2 22 ms 22 ms 22 ms cosp-dsl-gw12.cosp.qwestnet [184.99.0.12]
3 23 ms 21 ms 23 ms cosp-agw1.inet.qwestnet [184.99.1.89]
4 26 ms 26 ms 26 ms dvr3-brdr-01.inet.qwestnet [208.168.152.130]
5 * * * Request timed out.
6 * * * Request timed out.
7 41 ms 42 ms 41 ms BLIZZARD-EN.ear3.Dallas1.Level3net [4.15.45.54]
8 60 ms 61 ms 61 ms ae1-br02-eqda6.as57976net [137.221.74.35]
9 58 ms 61 ms 60 ms et-0-0-2-br02-swlv10.as57976net [137.221.65.67]
10 315 ms 187 ms 224 ms 137.221.65.122
11 88 ms 118 ms 221 ms et-0-0-2-br01-eqla1.as57976net [137.221.65.68]
12 59 ms 58 ms 58 ms be1-pe01-eqla1.as57976net [137.221.68.67]
13 60 ms 59 ms 61 ms 24.105.30.129

Trace complete.

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms modem.Home [192.168.0.1]
2 3 ms 2 ms 2 ms phn4-dsl-gw06.phn4.qwest.ne t [71.32.112.6]
3 18 ms 16 ms 14 ms 71-32-113-41.phn4.qwest.ne t [71.32.113.41]
4 3 ms 3 ms 3 ms 209.181.128.2
5 * * * Request timed out.
6 15 ms 13 ms 14 ms BLIZZARD-EN.ear3.LosAngeles1.Level3.ne t [4.71.135.106]
7 * * 3165 ms ae1-br01-eqla1.as57976.ne t [137.221.68.33]
8 * * * Request timed out.
9 49 ms 81 ms * 137.221.65.133
10 51 ms 50 ms 49 ms be1-pe02-eqch2.as57976.ne t [137.221.69.69]
11 50 ms 50 ms 50 ms chi-eqch2-ia-bons-04.as57976.ne t [137.221.66.15]
12 54 ms 52 ms 52 ms 24.105.62.129

Trace complete.

Can you identify the ISP… Level3, Frontier, Charter…? Who do “we” need to call? I have zero lost packets to your “servers” 24.105.62.129, sure it not on your end?

Ping statistics for 24.105.62.129:
Packets: Sent = 745, Received = 745, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 60ms, Average = 50ms

2 Likes

Wondering if there is potentially a HOST file edit we can use temporarily to maintain a persistent connection? Like…

> #      127.0.0.1       localhost
> #      ::1             localhost
> blizz.auth             24.105.62.129

Stabbing in the dark…

Level 3 Communications Issue?

Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  ----- 
  2    14 ms    24 ms     7 ms  eug2-dsl-gw01.eug2.qwest.net [65.100.6.1]
  3     9 ms     7 ms     7 ms  eug2-agw1.inet.qwest.net [65.100.7.1]
  4    14 ms    17 ms    13 ms  sea-brdr-03.inet.qwest.net [67.14.41.154]
  5     *        *        *     Request timed out.
  6    14 ms    13 ms    13 ms  ae-2-3613.edge1.Seattle3.Level3.net [4.69.160.73]
  7    14 ms    14 ms    14 ms  BLIZZARD-EN.edge1.Seattle3.Level3.net [4.59.232.146]
  8    62 ms    61 ms    63 ms  ae1-br02-eqse2.as57976.net [137.221.73.35]
  9    62 ms    62 ms     *     xe-0-0-1-1-br02-eqch2.as57976.net [137.221.65.42]
 10    62 ms    62 ms    62 ms  be2-pe01-eqch2.as57976.net [137.221.69.71]
 11    63 ms    63 ms    65 ms  chi-eqch2-ia-bons-02.as57976.net [137.221.66.11]
 12    63 ms    63 ms    64 ms  24.105.62.129

Hey all,

We made another modification a few minutes ago to try to get affected players off of the overloaded backbone provider that was causing the issue. How are things for you all now? If it’s not immediately improved, sit tight for a few minutes - sometimes when we make a change like this it takes a bit for ISPs to pick up the modification.

9 Likes

checking now, one minute;

edit: working fine now, thank you

Blizzard…

Works for me… :slight_smile:

I just played a full game in Arcade. So, whatever you did I think has worked, for me at least. Thank you!

So far, so good over here…

it worked for me, thank you

Appears to be working for me too. Thank you!

Working here as well, thanks for the updates and persistence!
gg