"Connection lost to server" constantly, with perfect connectivity

Technical Support
1

When playing competitive, being kicked from a game with no real connection issues is devastating. This happens on a very regular basis (several times a day). I have a screenshot of (as well as 24/7 logs) of TCP connection reliability all the way to Google being rock solid when this happens. Literally just being booted and immediately rejoin, which resets everything and disqualifies the player despite reconnecting literally within 10 seconds of disconnecting.

THIS IS A PROBLEM ON BLIZZARDS SIDE, real user connection issues DO NOT RESOLVE THEMSELVES INSTANTLY with no perceivable network events. No packet loss, sub 100ms pings, and no IP routing switches. Literally no network events AT ALL.

After suffering through this along with countless people on the technical forums, I am tired of it. There is literally 1 or more reports of this happening on every single page in the technical support forum.

Just like all the rest I am sure I will get some automated response telling me to do Blizzards asinine “troubleshooting” and then be completely ignored.

7 Likes
2

Imgur

3

The latency at the second hop is higher than the rest of the chain. Can you try to capture this issue with a WinMTR running? Keep it going for at least 10 minutes. Use the Copy Text to Clipboard button and paste the results back here in your reply.

Thank you!

5

I still have the same issues similar to these on EU server post patch I already mentioned in my post :

I think there could be a problem with the login server. A friend who plays OW for years told me she had similar problems for 2 months some while ago and they just disappeared after.

1 Like
6

LOL you did get the cut and paste troubleshooting

1 Like
7

Your kidding right? I’m running a paid network monitoring program, TCP pinging with dummy packets. WinMTR isn’t even capable of TCP pinging, making it a hell of a lot less reliable. I also record network events 24/7 so if you want those logs then I can provide those no problem. The latency on the second hop is well within standard tolerance and is probably due to that router having a higher load than the rest in the chain.

EDIT: When I play tomorrow I will play quick match and try and run a monitor on each game. That way it doesn’t effect my ranking, and I don’t really care if we get a couple second slow start.

1 Like
8

I got the same problem since the update today. My issue is that i always lost connection right before the end of the match. I tested it out multiple time, i can connect, play, enter training, browse skins, etc. without any problem, then right before the end of the match, i will get “lost connection to the server” message. THIS IS NOT MY CONNECTION OR MY PC’S PROBLEM. The only variable related to the disconnect is the match ending. FIX THE DAMN PROBLEM

3 Likes
9

Same problem. I get Disconected very often, i alredy have a punishment for leaving my games. It begins with the new patch

10

Well, I just played three games and attempted to hook into the server specifically for each game. The game servers refuse all packets whether ICMP, UDP, or TCP.

However I did notice something interesting inside Blizzards network. Although it’s minor and without being able to see the end destination I can’t see if it translates or not (It doesn’t look like it), I am getting random significant ping spikes from Blizz hardware.

Remove the space after htt for link, apparently I can’t post links anymore. Wherever you see blank spots on the graph is where latency exceeded my set upper limit of 250ms.

htt ps://imgur.com/C89yJDd

11

This has been happening to me constantly for the last two months, right around the time Ashe went live. Same thing. That and D/Cing when I die sometimes and can’t respawn.

12

same here, multiple random disconnects per day, it is KILLING competitive for me. i can rejoin instantly but im often moved back to spawn and i lose my ult charge and stats for the game, so it can throw a vital teamfight if i just disappear and then have to start at spawn, it’s the same as dying.

2 Likes
13

Same here, I lose connection about 2 minutes into comp play or quickplay. I have all these penalty warnings. This was running perfectly until the winter update. I tried the “troubleshooting” but don’t understand half of it. Just make the damned game work.

1 Like
14

Droolguy,

The request for WinMTRs are less about quality and more because this is a tool we’ve all been using in support for a while to investigate these issues, and the exported results are more easily copy/pasted to our network admins when needed. Also, in some cases we’re interested in how the ICMP echo requests look. We know the program has quirks since some of the internet discards ICMP to protect against DDoS attacks, but we’re accustomed to the quirks of this program.

Interesting findings with that pingplotter graph though. There may legitimately be something going on at our backbone - I’ll look out for other reports. On average a couple hundred MS spike for a brief amount of time should not be disconnecting you, especially when it’s not accompanied by any packet loss, though.

I checked out your account and it does look like there have been a some number of dropped packets from your location. It’s possible the packets just hit our timeout threshold but I’m wondering if your sampling isn’t happening quickly enough to catch the issue. It looks like you ran that pingplotter for about 5 minutes with only 61 samples taken. Can you up the sampling to 1 packet per second and re run it? That should give us a bit more accurate information.

15

just literally 30 seconds ago i got yet another disconnect, first point capped in KOTH in competitve and i DC and dont even get the chance to rejoin, INSTANTLY punished with a huge SR loss and 10 minute ban.

blizzard this is COMPLTELY UNACCEPTABLE and you need to fix this trash performance. there are numerous threads about this, TONS of people are having this issue with your game lately.

i have ZERO problems with my internet or any other online game. it is on your end. competitive was already a joke but this is just ridiculous. your game is almost unplayable.

1 Like
16

it’s entirely on your end. get this crap fixed. got all the time in the world to work on mobile games though i bet.

3 Likes
17

I don’t have much to do tomorrow so I should be able to log quite a bit, and yes I can drop the poll rate down to 1 a second and switch to ICMP if you want.

I normally run 2.5 seconds or more simply because if I switch to ICMP 1 second or less it can start hitting those DDoS filters.

Since playing the game really shouldnt be a prerequisit to seeing any network issues I can set it up on it’s own thread and let it run all day pointed at la1.

Like you said though, there is no packet loss showing, and those ping spikes don’t translate down (they don’t line up and cascade through the hops) so there is a good chance nothing is wrong.

Without being able to get a response from the game servers themselves though it is very difficult to troubleshoot this way.

EDIT: It’s running, best I can give you is a sample rate of 1.4 seconds on ICMP, anything faster and it runs into Blizzards DDoS protection and I start loosing huge amounts of packets.

EDIT 2: Ran all day, nothing unusual happening. Negligible packet loss (0.1%) and acceptable pings. Unfortunately since I can’t reach the actual game servers it just shows that the backbone isn’t having any problems, doesn’t show that the game servers themselves are not having any issues.

1 Like
18

Hey guys, i’ve been having this problem too and I am losing SR for no apparent reason. Could any one of you guys see if you guys know what’s the problem?

TRACEROUTE:
traceroute to 118.200.113.177 (118.200.113.177), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.410 ms 3.387 ms 3.435 ms
2 24.105.18.131 (24.105.18.131) 7.840 ms 7.850 ms 7.877 ms
3 137.221.105.16 (137.221.105.16) 7.733 ms 7.854 ms 7.872 ms
4 137.221.66.22 (137.221.66.22) 5.056 ms 5.077 ms 5.083 ms
5 137.221.83.68 (137.221.83.68) 9.886 ms 9.925 ms 9.938 ms
6 137.221.65.68 (137.221.65.68) 15.901 ms 126.281 ms 126.326 ms
7 137.221.68.32 (137.221.68.32) 6.313 ms 6.337 ms 6.348 ms
8 mpr1.lax2.us.above. net (206.223.123.71) 6.404 ms 6.377 ms 5.626 ms
9 ae13.cs1.lax112.us.eth.zayo. com (64.125.28.230) 14.821 ms 14.843 ms 15.026 ms
10 ae2.cs1.sjc2.us.eth.zayo. com (64.125.28.144) 14.173 ms 14.227 ms 14.247 ms
11 ae9.mpr1.pao1.us.zip.zayo. com (64.125.27.189) 15.019 ms 14.841 ms 15.253 ms
12 64.125.35.190 (64.125.35.190) 15.004 ms 15.304 ms 16.115 ms
13 203.208.172.233 (203.208.172.233) 15.763 ms 15.813 ms 14.883 ms
14 203.208.158.49 (203.208.158.49) 291.442 ms 291.339 ms 291.546 ms
15 203.208.182.250 (203.208.182.250) 190.147 ms 190.168 ms 189.667 ms

28/05/2019 08:23:17 UTC

TRACEROUTE:
traceroute to 118.200.113.177 (118.200.113.177), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.335 ms 0.334 ms 0.333 ms
2 24.105.18.131 (24.105.18.131) 1.043 ms 1.074 ms 1.073 ms
3 137.221.105.16 (137.221.105.16) 1.072 ms 1.071 ms 1.070 ms
4 137.221.66.22 (137.221.66.22) 0.567 ms 0.786 ms 0.789 ms
5 137.221.83.68 (137.221.83.68) 3.022 ms 3.038 ms 3.038 ms
6 137.221.65.68 (137.221.65.68) 5.690 ms 10.343 ms 10.325 ms
7 137.221.68.32 (137.221.68.32) 5.528 ms 5.524 ms 5.521 ms
8 mpr1.lax2.us.above. net (206.223.123.71) 5.375 ms 5.424 ms 5.405 ms
9 ae13.cs1.lax112.us.eth.zayo. com (64.125.28.230) 15.118 ms 15.936 ms 15.920 ms
10 ae2.cs1.sjc2.us.eth.zayo. com (64.125.28.144) 17.504 ms 16.975 ms 16.950 ms
11 ae9.mpr1.pao1.us.zip.zayo. com (64.125.27.189) 14.837 ms 15.772 ms 14.801 ms
12 64.125.35.190 (64.125.35.190) 15.295 ms 15.290 ms 15.285 ms
13 203.208.172.233 (203.208.172.233) 22.257 ms 22.264 ms 20.774 ms
14 203.208.158.49 (203.208.158.49) 293.780 ms 292.137 ms *
15 203.208.182.250 (203.208.182.250) 190.256 ms 190.152 ms 189.899 ms

28/05/2019 08:23:17 UTC

PING:
PING 118.200.113.177 (118.200.113.177) 56(84) bytes of data.
64 bytes from 118.200.113.177: icmp_seq=1 ttl=46 time=194 ms
64 bytes from 118.200.113.177: icmp_seq=2 ttl=46 time=194 ms
64 bytes from 118.200.113.177: icmp_seq=3 ttl=46 time=193 ms
64 bytes from 118.200.113.177: icmp_seq=4 ttl=46 time=194 ms

— 118.200.113.177 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 193.959/194.054/194.222/0.327 ms

28/05/2019 08:23:17 UTC

PING:
PING 118.200.113.177 (118.200.113.177) 56(84) bytes of data.
64 bytes from 118.200.113.177: icmp_seq=1 ttl=46 time=194 ms
64 bytes from 118.200.113.177: icmp_seq=2 ttl=46 time=194 ms
64 bytes from 118.200.113.177: icmp_seq=3 ttl=46 time=194 ms
64 bytes from 118.200.113.177: icmp_seq=4 ttl=46 time=194 ms

— 118.200.113.177 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 194.032/194.126/194.263/0.324 ms

28/05/2019 08:23:17 UTC

MTR:
Start: Tue May 28 08:23:17 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 0.5 1.1 0.5 3.4 0.9
3.|-- 137.221.105.16 0.0% 10 0.5 0.6 0.5 0.9 0.0
4.|-- 137.221.66.22 0.0% 10 0.6 1.3 0.5 7.4 2.1
5.|-- 137.221.83.68 0.0% 10 1.5 4.1 1.0 7.5 2.3
6.|-- 137.221.65.68 0.0% 10 5.6 6.1 5.6 9.1 0.9
7.|-- 137.221.68.32 0.0% 10 5.8 7.1 5.4 19.8 4.4
8.|-- mpr1.lax2.us.above. net 0.0% 10 5.5 5.5 5.4 5.7 0.0
9.|-- ae13.cs1.lax112.us.eth.zayo. com 0.0% 10 14.7 15.2 14.7 17.2 0.6
10.|-- ae2.cs1.sjc2.us.eth.zayo. com 0.0% 10 14.9 16.7 14.1 38.2 7.5
11.|-- ae9.mpr1.pao1.us.zip.zayo. com 0.0% 10 14.0 15.3 13.9 26.3 3.8
12.|-- 64.125.35.190 0.0% 10 14.7 14.7 14.7 14.9 0.0
13.|-- 203.208.172.233 0.0% 10 15.0 15.0 14.9 15.2 0.0
14.|-- 203.208.158.49 20.0% 10 292.4 292.6 291.4 298.1 2.2
15.|-- 203.208.182.250 0.0% 10 189.6 190.0 189.5 193.3 1.0
16.|-- 203.208.191.114 0.0% 10 183.0 183.2 183.0 183.4 0.0
17.|-- ae3-0.tp-cr03.singnet.com.sg 0.0% 10 183.4 183.3 183.2 183.4 0.0
18.|-- ae8-0.tp-ar11.singnet.com.sg 0.0% 10 190.1 190.4 189.8 194.1 1.2
19.|-- 202.166.123.134 0.0% 10 195.9 196.2 195.8 197.7 0.3
20.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21.|-- bb118-200-113-177.singnet.com.sg 0.0% 10 194.2 194.3 194.0 194.7 0.0

28/05/2019 08:23:17 UTC

MTR:
Start: Tue May 28 08:23:17 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.5 0.6 0.5 0.7 0.0
3.|-- 137.221.105.16 0.0% 10 0.6 1.4 0.4 8.6 2.4
4.|-- 137.221.66.22 0.0% 10 0.5 0.7 0.5 1.3 0.0
5.|-- 137.221.83.68 0.0% 10 1.3 3.8 1.0 7.6 2.8
6.|-- 137.221.65.68 0.0% 10 5.7 10.0 5.6 37.3 10.2
7.|-- 137.221.68.32 0.0% 10 5.5 5.7 5.5 6.0 0.0
8.|-- mpr1.lax2.us.above. net 0.0% 10 5.5 8.2 5.3 22.3 5.5
9.|-- ae13.cs1.lax112.us.eth.zayo. com 0.0% 10 16.8 15.8 14.8 17.2 0.8
10.|-- ae2.cs1.sjc2.us.eth.zayo. com 0.0% 10 32.8 32.8 14.0 52.6 12.7
11.|-- ae9.mpr1.pao1.us.zip.zayo. com 0.0% 10 14.1 16.2 13.9 36.3 7.0
12.|-- 64.125.35.190 0.0% 10 14.9 15.0 14.7 16.6 0.5
13.|-- 203.208.172.233 0.0% 10 15.0 15.2 14.9 15.8 0.0
14.|-- 203.208.158.49 10.0% 10 291.5 291.9 291.3 294.7 0.9
15.|-- 203.208.182.250 0.0% 10 190.3 189.9 189.5 190.7 0.0
16.|-- 203.208.191.114 0.0% 10 183.3 183.3 183.1 184.0 0.0
17.|-- ae3-0.tp-cr03.singnet.com.sg 0.0% 10 183.4 183.4 183.2 183.6 0.0
18.|-- ae8-0.tp-ar11.singnet.com.sg 0.0% 10 189.9 190.0 189.9 190.2 0.0
19.|-- 202.166.123.134 0.0% 10 207.1 206.6 195.9 232.4 13.9
20.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21.|-- bb118-200-113-177.singnet.com.sg 0.0% 10 194.5 194.4 194.2 194.6 0.0

28/05/2019 08:23:17 UTC

19

Please don’t necro a 6-month-old thread. Their issue is likely resolved by now. Start a new thread with this data.