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

Can it be an ISP issue if I have no trouble connecting to other game servers? It seems to be just Bliz servers having this issue

2 Likes

TRACEROUTE:
traceroute to 100.34.91.195 (100.34.91.195), 15 hops max, 60 byte packets
1 Blizzard Blizzard 5.319 ms 5.319 ms 5.328 ms
2 24.105.18.3 (24.105.18.3) 5.415 ms 5.409 ms 5.445 ms
3 137.221.105.16 (137.221.105.16) 5.411 ms 5.434 ms 5.444 ms
4 137.221.66.22 (137.221.66.22) 5.483 ms 5.495 ms 5.507 ms
5 137.221.83.68 (137.221.83.68) 5.557 ms 5.564 ms 5.570 ms
6 137.221.65.68 (137.221.65.68) 7.165 ms 6.809 ms 6.790 ms
7 137.221.68.32 (137.221.68.32) 6.791 ms 7.249 ms 7.232 ms
8 las-b21-link.telia. net (62.115.178.200) 7.070 ms 6.304 ms 6.267 ms
9 xe-5-3-2.BR3.LAX15.ALTER. NET (152.179.21.77) 6.266 ms 6.014 ms 5.999 ms
10 * * *
11 ae203-0.PHLAPA-VFTTP-308.verizon-gni. net (130.81.171.1) 104.028 ms 103.623 ms 101.225 ms
12 pool-100-34-91-195.phlapa.fios.verizon. net (100.34.91.195) 68.382 ms 66.941 ms 66.923 ms

Also having lost connection issues. East Coast/xfi customer.

Just played a game of Hearthstone, and did a D3 run. No issues at all. Its just OW.

1 Like

Lost connection to game server, unable to log in. Southwest/Century Link customer. I tried resetting my pc, and my router and modem, and reinstalling the game. Still the same issue.

Blizzard CS just tweeted out they are investigating login issues for both Overwatch and WoW. https://twitter.com/BlizzardCS/status/1163466873037631489

1 Like

Support needs to see this now! US-East Coast, playing in comp and got booted, said whatever and tried to rejoin and wouldn’t let me. Booted me off again, logged back on only to find I am suspended and I lost SR because of it.

Same thing here in Argentina, WOW if affected too.

Tracing route to 24.105.30.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    12 ms    12 ms    14 ms  86-165-89-200.fibertel.com.ar [200.89.165.86]
  6     9 ms    10 ms     8 ms  ae6.baires3.bai.seabone.net [185.70.203.22]
  7   133 ms   133 ms   147 ms  et0-3-0.miami19.mia.seabone.net [89.221.41.161]
  8   132 ms   135 ms   133 ms  be6762.ccr21.mia03.atlas.cogentco.com [154.54.9.17]
  9   127 ms   127 ms   128 ms  be3400.ccr21.mia01.atlas.cogentco.com [154.54.47.17]
 10   133 ms   132 ms   133 ms  be3410.rcr21.b002802-2.mia01.atlas.cogentco.com [154.54.6.86]
 11   135 ms   135 ms   155 ms  te0-0-2-3.nr11.b002802-1.mia01.atlas.cogentco.com [154.24.43.42]
 12   133 ms   133 ms   133 ms  gi0-0-0-18.205.nr11.b002802-1.mia01.atlas.cogentco.com [38.104.90.5]
 13   195 ms   194 ms   195 ms  ae1-br01-eqmi2.as57976.net [137.221.76.33]
 14   198 ms   197 ms   197 ms  xe-0-0-1-1-br01-eqda6.as57976.net [137.221.65.62]
 15   214 ms   229 ms   204 ms  et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
 16   202 ms   200 ms   200 ms  137.221.65.122
 17   202 ms   207 ms   199 ms  et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
 18   197 ms   197 ms   197 ms  be1-pe01-eqla1.as57976.net [137.221.68.67]
 19   205 ms   204 ms   205 ms  24.105.30.129

Trace complete.Preformatted text

I just got back from playing on the Europe Server, no problems at all. Yet I still can’t stay connected for more than 3 minutes on the American. It’s definitely a US server blizzard issue.

I am having the same issue in the last 10 min, cant log in to then game in America Servers, but Europe and Asia is fine, what can I do to resolve this ?

Im on the Americas servers but am from Australia

Is this fixed yet for anyone?

`Tracing route to 24.105.30.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 1 ms 1 ms 2 ms 24.105.30.129

Trace complete.`

The idea that this is an ISP issue is ridiculous imo.
You’re really going to tell me that through 3 different regions(with what? 4-5 different ISPs total?) all of those ISPs just need to fix themselves?
It’s def. something on blizzard’s end and I’m glad it’s being looked into.

2 Likes

I am on the East Coast

TRACEROUTE:
traceroute to 24.144.187.250 (24.144.187.250), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.361 ms 0.354 ms 1.080 ms
2 24.105.18.131 (24.105.18.131) 0.656 ms 0.738 ms 0.836 ms
3 137.221.105.12 (137.221.105.12) 1.076 ms 1.077 ms 1.078 ms
4 137.221.66.20 (137.221.66.20) 1.076 ms 1.076 ms 1.072 ms
5 137.221.83.68 (137.221.83.68) 33.007 ms 33.031 ms 33.033 ms
6 137.221.65.68 (137.221.65.68) 7.064 ms 5.853 ms 5.846 ms
7 137.221.68.32 (137.221.68.32) 37.431 ms 37.453 ms 37.547 ms
8 las-b21-link telia net (62.115.178.200) 5.852 ms 5.525 ms 5.546 ms
9 ash-bb4-link telia net (62.115.137.38) 59.340 ms 59.350 ms 60.275 ms
10 pitt-b2-link telia net (62.115.142.225) 59.275 ms 58.795 ms 58.785 ms
11 armstrong-ic-339912-pitt-b1 c telia net (62.115.167.245) 59.501 ms 59.535 ms 59.604 ms
12 dynamic-acs-24-144-187-250 zoominternet net (24.144.187.250) 59.344 ms 59.357 ms 59.320 ms

I had to edit it a bit so that the above was not an internet link. That’s my results too, but keep dc’ing. Corning, NY (yes I restarted modem and waited about 30 seconds).

Blockquote

Fortunately, no SR that you gain/lose during the beta will effect your actual SR. S18 will continue right where S17 left off, as if the beta season never happened.

Tracing route to 24.105.30.129 over a maximum of 30 hops

1     1 ms     1 ms     1 ms  192.168.0.1
2     *        *        *     Request timed out.
3     *        *        *     Request timed out.
4     *        *        *     Request timed out.
5    16 ms    15 ms    15 ms  222-165-89-200.fibertel.com.ar [200.89.165.222]

6    11 ms    12 ms    12 ms  221-165-89-200.fibertel.com.ar [200.89.165.221]

7    11 ms    11 ms    11 ms  129-165-89-200.fibertel.com.ar [200.89.165.129]

8    26 ms    13 ms    15 ms  150-165-89-200.fibertel.com.ar [200.89.165.150]

9    10 ms    12 ms    11 ms  ae6.baires3.bai.seabone.net [185.70.203.22]
10   151 ms   137 ms   145 ms  et1-1-0.miami19.mia.seabone.net  89.221.41.187]

11   136 ms   141 ms   141 ms  be6762.ccr21.mia03.atlas.cogentco.com [154.54.9.17]
12   139 ms   137 ms   136 ms  be3400.ccr21.mia01.atlas.cogentco.com [154.54.47.17]
13   139 ms   138 ms   138 ms  be3410.rcr21.b002802-2.mia01.atlas.cogentco.com [154.54.6.86]
14   137 ms   139 ms   137 ms  te0-0-2-3.nr11.b002802-1.mia01.atlas.cogentco.com [154.24.43.42]
15   137 ms   136 ms   143 ms  gi0-0-0-18.205.nr11.b002802-1.mia01.atlas.cogentco.com [38.104.90.5]
16   210 ms   210 ms   209 ms  ae1-br01-eqmi2.as57976.net [137.221.76.33]
17   202 ms   197 ms   198 ms  xe-0-0-1-1-br01-eqda6.as57976.net [137.221.65.62]
18   208 ms   207 ms   213 ms  et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]

19   207 ms   207 ms   215 ms  137.221.65.122
20   219 ms   205 ms   208 ms  et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]

21   201 ms   201 ms   202 ms  be1-pe01-eqla1.as57976.net [137.221.68.67]
22   217 ms   226 ms   210 ms  lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]

23   216 ms   215 ms   212 ms  24.105.30.129

Trace complete.

Location: East Coast / Canada (Bell Fibeop 1000Mbps Up/Down). Able to join and complete a match (QP) on Asian server. Able to join / connect to America servers, but unable to complete a match (QP) due to ‘connection to server lost, unable to connect’.

The Blizzard Launcher shows the following messsage:

There will be maintenance occurring in one of our data centers on Tuesday, August 20th beginning at 5:00 AM (PDT) and lasting until 10:00 AM (PDT). We do not expect any disruption to games or services during this time but will be monitoring the progress of the maintenance closely. Please follow @BlizzardCS on Twitter for any updates.

It is currently 8:49AM PDT

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms mynetwork [192.168.2.1]
2 1 ms 2 ms 1 ms -loop0.57w.ba09.stjh.nf.aliant.net [142.163.63.12]
3 1 ms 3 ms 1 ms -be14-181.dr01.stjh.nf.aliant.net [142.176.208.57]
4 12 ms 12 ms 13 ms -be1.dr01.crbk.nf.aliant.net [142.166.149.126]
5 13 ms 11 ms 10 ms -ae3-50.dr02.crbk.nf.aliant.net [142.166.181.54]
6 20 ms 20 ms 19 ms -et-0-3-0.cr02.hlfx.ns.aliant.net [142.166.181.113]
7 23 ms 22 ms 21 ms -hg-0-2-0-0-50.cr01.hlfx.ns.aliant.net [142.166.149.93]
8 40 ms 38 ms 37 ms -be19.bx01.nycm.ny.aliant.net [207.231.227.110]
9 39 ms 38 ms 38 ms -lag-197.ear3.NewYork1.Level3.net [4.71.230.101]
10 38 ms 38 ms 39 ms 4.69.216.226
11 39 ms 66 ms 39 ms -BLIZZARD-EN.ear1.NewYork5.Level3.net [4.35.72.34]
12 117 ms 116 ms 117 ms -ae1-br01-eqny8.as57976.net [137.221.71.33]
13 115 ms 115 ms 115 ms -et-0-0-2-br02-eqch2.as57976.net [137.221.65.8]
14 116 ms 116 ms 116 ms -et-0-0-29-br01-eqch2.as57976.net [137.221.65.2]
15 117 ms 117 ms 115 ms 137.221.65.132
16 175 ms 219 ms 219 ms -et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
17 116 ms 116 ms 117 ms -be1-pe02-eqla1.as57976.net [137.221.68.69]
18 117 ms 116 ms 117 ms -lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
19 118 ms 117 ms 117 ms 24.105.30.129

Trace complete.

Even if the SR doesn’t matter, you still end up getting suspensions for something blizzard is supposed to be responsible for. This happened frequently a few weeks ago to the point where I end up getting a 7 hours cool-down. Happened twice today ,had a 10 min cool-down and then a 30 min. At this point I’m skeptical about even queuing for comp. Bummer considering I’m enjoying tanking now more than ever since we’re forced to have 2 healers in game.

1 Like