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

I am also unable to get into the menu screen, i login and it says “entering game” for a couple minutes then quits back to login screen. I am playing on the Americas region.

Guys your ISP means SFA… happening to all australians also… = verizon has 0 to do with it /facepalm… it is blizzards mess as usual

1 Like
Traza a 25.105.30.129 sobre caminos de 30 saltos como m ximo.

  1    <1 ms    <1 ms    <1 ms  192.168.1.1 
  2     *        *        *     Tiempo de espera agotado para esta solicitud.
  3     *        *        *     Tiempo de espera agotado para esta solicitud.
  4     *        *        *     Tiempo de espera agotado para esta solicitud.
  5    14 ms    15 ms    15 ms  250-165-89-200.fibertel.com.ar [200.89.165.250] 
  6     *        *        *     Tiempo de espera agotado para esta solicitud.
  7     *        *        *     Tiempo de espera agotado para esta solicitud.
  8     *        *        *     Tiempo de espera agotado para esta solicitud.
  9     *        *        *     Tiempo de espera agotado para esta solicitud.
 10     *        *        *     Tiempo de espera agotado para esta solicitud.
 11     *        *        *     Tiempo de espera agotado para esta solicitud.
 12     *        *        *     Tiempo de espera agotado para esta solicitud.
 13     *        *        *     Tiempo de espera agotado para esta solicitud.
 14     *        *        *     Tiempo de espera agotado para esta solicitud.
 15     *        *        *     Tiempo de espera agotado para esta solicitud.
 16     *        *        *     Tiempo de espera agotado para esta solicitud.
 17     *        *        *     Tiempo de espera agotado para esta solicitud.
 18     *        *        *     Tiempo de espera agotado para esta solicitud.
 19     *        *        *     Tiempo de espera agotado para esta solicitud.
 20     *        *        *     Tiempo de espera agotado para esta solicitud.
 21     *        *        *     Tiempo de espera agotado para esta solicitud.
 22     *        *        *     Tiempo de espera agotado para esta solicitud.
 23     *        *        *     Tiempo de espera agotado para esta solicitud.
 24     *        *        *     Tiempo de espera agotado para esta solicitud.
 25     *        *        *     Tiempo de espera agotado para esta solicitud.
 26     *        *        *     Tiempo de espera agotado para esta solicitud.
 27     *        *        *     Tiempo de espera agotado para esta solicitud.
 28     *        *        *     Tiempo de espera agotado para esta solicitud.
 29     *        *        *     Tiempo de espera agotado para esta solicitud.
 30     *        *        *     Tiempo de espera agotado para esta solicitud.

Traza completa.

It’s just Kaplan these days d/t ppl leaving…he’s doing another YouTube video so he’s not available right now for the ppl that pay his bills…sorry, maybe try another game.

1 Like

Can confirm it’s happening across South India as well, a friend from a city further up north texted. It has to be Blizz tho right? It’s happening in 3 different continents lol

From Philadelphia, PA.   
  
Tracing route to 24.105.30.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1 
  2     2 ms     1 ms     2 ms  24.105.30.129 

Trace complete.

LOOKING GLASS - 

TRACEROUTE:
traceroute to 173.49.169.58 (173.49.169.58), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.328 ms  0.357 ms  1.415 ms
 2  24.105.18.131 (24.105.18.131)  0.615 ms  0.767 ms  0.793 ms
 3  137.221.105.12 (137.221.105.12)  1.436 ms  1.457 ms  1.507 ms
 4  137.221.66.20 (137.221.66.20)  1.527 ms  1.578 ms  2.097 ms
 5  137.221.83.68 (137.221.83.68)  5.520 ms  5.564 ms  5.945 ms
 6  137.221.65.68 (137.221.65.68)  5.942 ms  5.763 ms  5.775 ms
 7  137.221.68.32 (137.221.68.32)  67.748 ms  67.762 ms  67.775 ms
 8  las-b21-link.telia.net (62.115.178.200)  5.925 ms  5.958 ms  5.986 ms
 9  xe-5-3-2.BR3.LAX15.ALT`Preformatted text`ER.NET (152.179.21.77)  5.708 ms  5.890 ms  5.902 ms
10  * * *
11  ae204-0.PHLAPA-VFTTP-324.verizon-gni.net (130.81.26.67)  62.840 ms  62.740 ms  62.931 ms
12  pool-173-49-169-58.phlapa.fios.verizon.net (173.49.169.58)  66.420 ms  66.000 ms  65.908 ms


19/08/2019 16:29:04 UTC
--------------------

MTR:
Start: Mon Aug 19 16:29:04 2019 Blizzard  1.|-- Blizzard                               0.0%    10    0.3   0.4   0.3   0.6   0.0
  2.|-- 24.105.18.131                               0.0%    10    0.5   2.1   0.5  11.6   3.6
  3.|-- 137.221.105.12                              0.0%    10    0.5   0.7   0.5   1.2   0.0
  4.|-- 137.221.66.20                               0.0%    10    1.0   3.1   1.0  20.6   6.1
  5.|-- 137.221.83.68                               0.0%    10    1.1   6.9   1.1  14.5   4.9
  6.|-- 137.221.65.68                               0.0%    10    5.7  51.1   5.6 297.1  91.5
  7.|-- 137.221.68.32                               0.0%    10    7.6   6.4   5.9   8.0   0.5
  8.|-- las-b21-link.telia.net                      0.0%    10    5.7   5.8   5.5   6.6   0.0
  9.|-- xe-5-3-2.BR3.LAX15.ALTER.NET                0.0%    10    5.7   7.7   5.6  15.6   3.9
 10.|-- ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- ae204-0.PHLAPA-VFTTP-324.verizon-gni.net    0.0%    10   62.9  65.1  62.8  79.9   5.4
 12.|-- pool-173-49-169-58.phlapa.fios.verizon.net  0.0%    10   65.3  66.4  64.4  73.4   2.5


19/08/2019 16:29:04 UTC
--------------------

East Coast Verizon here and can confirm same issue. Get ‘Connection to Server lost’ repeatedly.

The Looking Glass run for me is below. Two things I noticed…node 6 has a massive spike in the range of packet transmission.

HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
6.|-- 137.221.65.68 0.0% 10 6.5 86.2 5.8 291.5 126.3

With a range of 5.8 to 291.5, averaging 86.2 ms. This is a node in Netherlands.

and

My ping jumps from ~10 ms to ~60-70 ms somewhere on Verizon’s lines.

HOST: Blizzzard Loss% Snt Last [Avg] Best Wrst StDev
9.|-- xe-5-3-2.BR3.LAX15.ALTER.NET_0.0% 10 5.7 [10.3] 5.6 28.3 9.4
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae203-0.WASHDC-VFTTP-351.verizon-gni.net_0.0% 10 61.6 [61.8] 61.6 62.8 0.0
12.|-- pool-71-255-226-215.washdc.east.verizon.net_0.0% 10 69.9 [70.4] 66.9 73.9 2.3

Hope this helps solve the problem…


TRACEROUTE:
traceroute to 71.255.226.215 (71.255.226.215), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.774 ms 1.785 ms 1.794 ms
2 24.105.18.3 (24.105.18.3) 2.190 ms 2.232 ms 2.260 ms
3 137.221.105.16 (137.221.105.16) 2.024 ms 2.233 ms 2.576 ms
4 137.221.66.22 (137.221.66.22) 20.353 ms 20.402 ms 20.414 ms
5 137.221.83.68 (137.221.83.68) 2.581 ms 2.590 ms 2.848 ms
6 137.221.65.68 (137.221.65.68) 173.976 ms 387.308 ms 673.722 ms
7 137.221.68.32 (137.221.68.32) 6.916 ms 6.952 ms 6.620 ms
8 las-b21-link.telia.net_(62.115.178.200) 5.425 ms 5.462 ms 5.523 ms
9 xe-5-3-2.BR3.LAX15.ALTER.NET_(152.179.21.77) 5.689 ms 5.725 ms 5.723 ms
10 * * *
11 ae203-0.WASHDC-VFTTP-351.verizon-gni.net_(100.41.220.85) 62.030 ms 61.808 ms 61.808 ms
12 pool-71-255-226-215.washdc.east.verizon.net_(71.255.226.215) 69.153 ms 67.303 ms 67.217 ms

19/08/2019 15:56:01 UTC

PING:
PING 71.255.226.215 (71.255.226.215) 56(84) bytes of data.
64 bytes from 71.255.226.215: icmp_seq=1 ttl=47 time=74.7 ms
64 bytes from 71.255.226.215: icmp_seq=2 ttl=47 time=70.2 ms
64 bytes from 71.255.226.215: icmp_seq=3 ttl=47 time=64.9 ms
64 bytes from 71.255.226.215: icmp_seq=4 ttl=47 time=69.5 ms

— 71.255.226.215 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 64.998/69.861/74.726/3.463 ms

19/08/2019 15:56:01 UTC

MTR:
Start: Mon Aug 19 15:56:01 2019 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.7 2.8 0.5 22.4 6.8
3.|-- 137.221.105.16 0.0% 10 0.7 1.0 0.5 4.0 1.0
4.|-- 137.221.66.22 0.0% 10 1.0 3.9 0.9 29.2 8.9
5.|-- 137.221.83.68 0.0% 10 4.1 8.7 0.8 44.3 12.7
6.|-- 137.221.65.68 0.0% 10 6.5 86.2 5.8 291.5 126.3
7.|-- 137.221.68.32 0.0% 10 5.9 10.6 5.9 49.3 13.6
8.|-- las-b21-link.telia.net_0.0% 10 5.7 6.1 5.6 8.8 0.8
9.|-- xe-5-3-2.BR3.LAX15.ALTER.NET_0.0% 10 5.7 10.3 5.6 28.3 9.4
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae203-0.WASHDC-VFTTP-351.verizon-gni.net_0.0% 10 61.6 61.8 61.6 62.8 0.0
12.|-- pool-71-255-226-215.washdc.east.verizon.net_0.0% 10 69.9 70.4 66.9 73.9 2.3

19/08/2019 15:56:01 UTC


I enjoy having Verizon FIOS but from my experience, they have a lot of routing issues. Also, tracert is worthless for Verizon FIOS customers because they are removing TTL or something in the layer 3 packet when it passes through their upstream router. That is why there is only two hops shown in tracert when Verizon customers try running it.

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     7 ms     6 ms     6 ms  24.105.30.129
1 Like

Also, tracert is worthless for Verizon FIOS customers because they are removing TTL or something in the layer 3 packet when it passes through their upstream router

Seeing the same thing here. And yes, usually I’m quite happy with Verizon internet

1 Like

Exact same thing happening to me, I joined a game and got kicked out for “connection lost”, I restart the game, check my internet, and try to launch again and search for another game but it kicks me again while searching for “connection lost”.

I thought this issue was happening to me only but its looks super common and it makes me want to stop playing the game I hope blizzard can fix

1 Like

Connected from Mendoza, Argentina
Tracing route to 24.105.30.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.3.1
2 4 ms 5 ms 3 ms 172.16.10.1
3 10 ms 8 ms 5 ms 10.1.111.1
4 6 ms 15 ms 5 ms 138.117.16.1
5 19 ms 23 ms 47 ms 200-63-158-113.speedy.com.ar [200.63.158.113]
6 31 ms 32 ms 26 ms 209.13.168.145
7 40 ms 45 ms 41 ms 213.140.39.118
8 172 ms 179 ms 176 ms 5.53.5.62
9 186 ms 189 ms 186 ms 94.142.124.105
10 179 ms 186 ms 197 ms 81.173.106.21
11 256 ms 244 ms 240 ms [137.221.72.33]
12 269 ms 274 ms 272 ms et-0-0-2-[137.221.65.13]
13 269 ms 268 ms 267 ms 137.221.65.132
14 250 ms 376 ms 440 ms [137.221.65.68]
15 246 ms 242 ms 244 ms [137.221.68.69]
16 242 ms 244 ms 244 ms 24.105.30.129

Trace complete.

hurry the FFFF up blizz and fix your garbage… one night off work this month and looking like i may as well go to bed… close to 3am and have not been able to play in 4 hours… lmao… small companies i work for have better servers and better techs :’)

Cant even log in on my side…Apex it is!

I’m in FL and I’m connecting to NA.

indent preformatted text by 4 spaces
Tracing route to 24.105.30.129 over a maximum of 30 hops

  1     3 ms     3 ms     3 ms  gateway.home [192.168.254.254]
  2     7 ms     8 ms     7 ms  47.205.70.1
  3    12 ms    14 ms    14 ms  172.99.42.172
  4    20 ms    19 ms    20 ms  ae8---0.scr02.mias.fl.frontiernet.net [74.40.3.73]
  5    21 ms    19 ms    20 ms  ae1---0.cbr01.mias.fl.frontiernet.net [74.40.1.126]
  6     *       18 ms    19 ms  lag-101.ear3.Miami2.Level3.net [4.15.156.29]
  7     *        *        *     Request timed out.
  8    20 ms    19 ms    17 ms  BLIZZARD-EN.ear2.Miami1.Level3.net [4.16.176.198]
  9    75 ms    77 ms    77 ms  ae1-br01-eqmi2.as57976.net [137.221.76.33]
 10    78 ms    77 ms    76 ms  xe-0-0-1-1-br01-eqda6.as57976.net [137.221.65.62]
 11    77 ms    77 ms    77 ms  et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
 12    76 ms    80 ms    75 ms  137.221.65.122
 13    79 ms    79 ms    78 ms  et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
 14    78 ms    77 ms    75 ms  be1-pe02-eqla1.as57976.net [137.221.68.69]
 15    78 ms    80 ms    81 ms  24.105.30.129

Trace complete.

Also, I can connect to EU and am able to get into Practice Range (it says ORD1, so it’s putting me on US Central), but it does give Connection Lost after a few minutes.

Buenos Aires, Argentina
Traza a 24.105.30.129 sobre caminos de 30 saltos como máximo.

1 <1 ms <1 ms <1 ms 192.168.0.1
2 12 ms 10 ms 16 ms [190.245.38.1]
3 * * * Tiempo de espera agotado para esta solicitud.
4 * * * Tiempo de espera agotado para esta solicitud.
5 19 ms 13 ms 14 ms [200.89.165.150]
6 12 ms 14 ms 13 ms [185.70.203.22]
7 135 ms 136 ms 137 ms [89.221.41.171]
8 137 ms 140 ms 137 ms [154.54.9.17]
9 184 ms 140 ms 138 ms [154.54.47.17]
10 137 ms 136 ms 139 ms [154.54.6.86]
11 144 ms 143 ms 136 ms [154.24.43.46]
12 134 ms 135 ms 140 ms [38.104.90.5]
13 182 ms 180 ms 185 ms [137.221.76.33]
14 183 ms 177 ms 178 ms [137.221.65.62]
15 181 ms 188 ms 180 ms [137.221.65.67]
16 187 ms 179 ms 178 ms 137.221.65.122
17 178 ms 179 ms 189 ms [137.221.65.68]
18 178 ms 180 ms 176 ms [137.221.68.69]
19 181 ms 178 ms 178 ms [137.221.66.7]
20 180 ms 202 ms 181 ms 24.105.30.129

Traza completa.

small companies i work for have better servers and better techs

As someone who works in tech I find your comments incredibly offensive and ignorant here. Small companies also have a lot smaller network footprint and customer base. Troubleshooting an issue as widescale as this, especially one that appears to be a routing issue, is incredibly difficult to resolve. I highly doubt the techs your small companies have exceed the collective experience of the network operations team required to support games of the scale that Blizzard does.

6 Likes

My connection is fine. Can play any other online game. Speed Test by Ookla fine…>100mbps.

oh dear god did i offend you? Noooo OMG!!! tehehe yeah a multi billion dollar company would have such massive issues… login servers are so damn complex :’)

I honestly don’t get people like you. It’s so off topic, flaming won’t do anyone any good. You have to realize the devs are human too not genies :stuck_out_tongue: they’re obviously working on it.

3 Likes