From Argentina, ISP Fibertel - More than four hours without service 
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 14 ms 23 ms 222-165-89-200.fibertel.com.ar [200.89.165.222]
6 13 ms 10 ms 20 ms 221-165-89-200.fibertel.com.ar [200.89.165.221]
7 12 ms 10 ms 15 ms 129-165-89-200.fibertel.com.ar [200.89.165.129]
8 19 ms 14 ms 23 ms 150-165-89-200.fibertel.com.ar [200.89.165.150]
9 12 ms 20 ms 12 ms ae6.baires3.bai.seabone.net [185.70.203.22]
10 137 ms 136 ms 138 ms et1-1-0.miami19.mia.seabone.net [89.221.41.187]
11 137 ms 138 ms 136 ms be6762.ccr21.mia03.atlas.cogentco.com [154.54.9.17]
12 138 ms 137 ms 137 ms be3400.ccr21.mia01.atlas.cogentco.com [154.54.47.17]
13 134 ms 137 ms 136 ms be3410.rcr21.b002802-2.mia01.atlas.cogentco.com[154.54.6.86]
14 139 ms 137 ms 138 ms te0-0-2-3.nr11.b002802-1.mia01.atlas.cogentco.com [154.24.43.42]
15 142 ms 137 ms 147 ms gi0-0-0-18.205.nr11.b002802-1.mia01.atlas.cogentco.com [38.104.90.5]
16 208 ms 211 ms 210 ms ae1-br01-eqmi2.as57976.net [137.221.76.33]
17 214 ms 200 ms 197 ms xe-0-0-1-1-br01-eqda6.as57976.net [137.221.65.62]
18 207 ms 208 ms 206 ms et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
19 207 ms 209 ms 207 ms 137.221.65.122
20 208 ms 207 ms 206 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
21 204 ms 203 ms 201 ms be1-pe01-eqla1.as57976.net [137.221.68.67]
22 209 ms 210 ms 219 ms lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
23 214 ms 217 ms 213 ms 24.105.30.129
Trace complete.
too busy releasing your guys version of Trump University to actually reset the servers? None of the blizzard games are working for me.
1 Like
Well, we made it to google news…
1 Like
This isn’t just overwatch, all blizzard games are being affected by this.
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 3 ms 4 ms 3 ms tukw-dsl-gw66.tukw.qwest.net [63.231.10.66]
3 5 ms 3 ms 3 ms tukw-agw1.inet.qwest.net [63.226.198.9]
4 4 ms 3 ms 3 ms sea-brdr-03.inet.qwest.net [67.14.41.150]
5 * * * Request timed out.
6 4 ms 3 ms 4 ms ae-2-3613.edge1.Seattle3.Level3.net [4.69.160.73]
7 19 ms 4 ms 3 ms BLIZZARD-EN.edge1.Seattle3.Level3.net [4.59.232.146]
8 63 ms 63 ms 56 ms ae1-br01-eqse2.as57976.net [137.221.73.33]
9 33 ms 31 ms 32 ms xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40]
10 33 ms 32 ms 32 ms et-0-0-29-br02-eqsv5.as57976.net [137.221.65.117]
11 32 ms 32 ms 32 ms xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6]
12 32 ms 32 ms 32 ms be2-pe01-eqla1.as57976.net [137.221.68.71]
13 32 ms 31 ms 32 ms lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
14 33 ms 33 ms 33 ms 24.105.30.129
Trace complete.
Then why wait till Tuesday to do something about it? Reset the servers and try again … someone screwed up if it was working fine all weekend and now this morning it isn’t. 7 hours with nothing being done is crap and absurd let alone not keeping the community posted on what is going on. Someone dropped the ball.
2 Likes
Every time i enter the game, i am constantly losing connection to the server, i’ll log in and lose connection almost immediately, or in about 1 or 2 minutes, and everytime i try to re log in, i am met with the same outcome, is anyone else experiencing this issue?
1 Like
I wonder how long has this been and issue?
I have the same issue, yet can play on EU servers just fine. It’s only NA.
i am having exact same problem this is the first time i have had this happening.
Since this morning apparently
what’s up with that, can’t even connect to the game
Still getting connection errors
It’s entirely possible this entire problem has no simple flip of the switch fix on blizzards end, it may be the route your computer is taking to connect to the blizzard servers that is the issue.
This has been going on since like 9 AM. I don’t understand how this has been an issue for SEVERAL hours.
3 Likes
If that is the case, which wouldn’t be the first time as I remember a route problem some months ago because some Brazilian ISP poisoned the routes, internet consortium should start putting fines on ISP for causing this mess. Otherwise we will keep seeing this forever.
Experiencing this issue as well. Didn’t have a single problem with it last night- played from 11:00-2:00 straight, no disconnection. Tried to log on today (8/19/19) at 12:30 pm & the game wouldn’t even put me in. “Lost connection to game server.”, no matter how many times I put in my login info.
Closed the game & restarted it. Was able to get into the game this time, but every two minutes would be booted because “connection to game server lost.”
Would log me back in but would lose the connection, like I said, every two minutes.
Restarted my modem twice.
Tried again. The same effin issue.
Hello, how the hell do we fix this? I just want to be able to play the game, let alone worry about being DCed mid comp match!
Here’s my traceroute results below. Looking through the above posts and my own, Level 3 looks to be involved in many of the reports. It looks like there have been previous reported issue with Level 3 Communication and latency issues in the past - this seems worse though.
> > * 1 <1 ms <1 ms <1 ms ----
> > * 2 8 ms 7 ms 9 ms eug2-dsl-gw01.eug2.qwest.net [65.100.6.1]
> > * 3 8 ms 8 ms 8 ms eug2-agw1.inet.qwest.net [65.100.7.1]
> > * 4 13 ms 14 ms 13 ms sea-brdr-03.inet.qwest.net [67.14.41.154]
> > * 5 * * * Request timed out.
> > * 6 14 ms 13 ms 14 ms ae-1-3513.edge1.Seattle3.Level3.net [4.69.160.69]
> > * 7 14 ms 14 ms 14 ms BLIZZARD-EN.edge1.Seattle3.Level3.net [4.59.232.146]
> > * 8 33 ms 40 ms 33 ms ae1-br01-eqse2.as57976.net [137.221.73.33]
> > * 9 33 ms 33 ms 33 ms xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40]
> > * 10 33 ms 33 ms 33 ms et-0-0-29-br02-eqsv5.as57976.net [137.221.65.117]
> > * 11 33 ms 38 ms 33 ms xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6]
> > * 12 33 ms 33 ms 33 ms be2-pe01-eqla1.as57976.net [137.221.68.71]
> > * 13 34 ms 34 ms 33 ms lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
> > * 14 33 ms 33 ms 34 ms 24.105.30.129
It’s not on your end, so all we can do is just wait around until a fix is pushed through by whomever actually has the issue originating from their end.
Just saw their tweet. Hopefully it all is resolved easily; frustrating as it is on this end, I can’t imagine the stress they are in over there with everyone flipping out about it too.
Glad they’ve recognized it though.