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

Technical Support
409

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.

410 
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.

411

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
412

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…

413

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
414

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
415

checking now, one minute;

edit: working fine now, thank you

416

Blizzard…

Works for me… :slight_smile:

417

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

418

So far, so good over here…

419

it worked for me, thank you

420

Appears to be working for me too. Thank you!

421

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

422

Still doesn’t work. :frowning:

423

Update on this, there is still sub optimal service for some players right now, including packet loss/latency spikes, but for now it seems like most players are at least working around the problem. If you find yourself having connection errors that are not normal for you, I recommend avoiding competitive modes for the time being while the backbone providers work on the core problem - to avoid penalties.

6 Likes
424

Great! however what about those of us playing QP and getting penalized for every connection loss?

I’m happy to be back on but annoyed at the fact that i DC’ed so many times I’m now taking a hit on EXP.

425

Custom games are the best way to avoid penalties of any variety. Ultimately the server is going to penalize regardless of the reason for a disconnect in modes like competitive/quick play/arcade since it still affects your fellow players.

426

The issue is fixed as well for me. thanks.

427

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms 192.168.1.1
2 5 ms 9 ms 10 ms 24.105.62.129

Trace complete.

-------- just created a custom game using one of the workshop aim practice games and things seem to be working fine … -----

-K (Virginia area Verizon user)

428

Been playing for nearly an hour, no drops at all. Thanks to you guys at Blizzard who looked into this.