Ow lost connection to game server

Technical Support
#1

Hello,

I keep getting disconnected from competitive games right after the match start. It’s really frustrating as I get now banned for 8h every time this happens. This means, I can’t play a game a payed for, even though I have no other connection issues with any of my other tools/games.

I can’t tell you how frustrating it is after a hard work-day, to want to enjoy the game a little and bam, after 10 sec, disconnected and banned …

I’ve tried all your suggestions on both the battle.net site and other forums.
I’ve reset everything there is to reset, updated my network drive again and all my drivers.

I want to note AGAIN, that I don’t have any other connection issues anywhere else. Overwatch is the only one that manifests this and it feels like I’m robbed of my money.

PLEASE invest some time and energy in detecting a network issue in comparison to a leaver … It’s absurd this way. Do a deeper network test for each player before starting a game, even if it takes 10s longer of waiting … This way you can avoid people like me that are close in throwing the game to the trash … literally … and from what I’ve seen online, I’m just one out of many many more.

Waiting for an answer and please don’t give me another link to one of your articles where you tell us to reset stuff … I work in IT domain also, I know that a restart is the solution to 90% of the cases, but it’s also a sign of non-professionalism and the proof that there are not enough experts available.

Here are my “Looking-Glass” results:
P.S. I edited all links and added a space prior to the “.net”, because your forum is so “smart” that it doesn’t let me post links from a tool you designed …

==============
TRACEROUTE:
traceroute to 78.97.202.189 (78.97.202.189), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.737 ms 0.723 ms 0.721 ms
2 37.244.25.130 (37.244.25.130) 259.156 ms 259.392 ms 275.178 ms
3 Blizzard Blizzard 1.452 ms 1.457 ms 1.455 ms
4 137.221.66.32 (137.221.66.32) 0.693 ms 0.691 ms 0.691 ms
5 137.221.77.76 (137.221.77.76) 7.692 ms 7.703 ms 7.704 ms
6 137.221.65.35 (137.221.65.35) 7.513 ms 7.550 ms 7.562 ms
7 137.221.65.19 (137.221.65.19) 7.633 ms 7.660 ms 7.664 ms
8 137.221.79.34 (137.221.79.34) 7.790 ms 7.812 ms 7.809 ms
9 uk-lon03a-ri1-ae-25-0.aorta. net (213.46.175.253) 7.906 ms 7.786 ms 7.886 ms
10 * * *
11 de-fra04d-rc1-ae-56-0.aorta. net (84.116.132.5) 59.617 ms 59.749 ms 59.773 ms
12 ro-buh01a-rd3-ae-37-0.aorta. net (84.116.138.14) 59.987 ms 60.051 ms 60.182 ms
13 ro-tm01a-rd4-ae-32-1853.aorta. net (84.116.187.86) 70.240 ms 70.162 ms 68.855 ms
14 ro-tm01a-rd3-ae-33-1863.aorta. net (84.116.187.101) 55.733 ms 55.285 ms 55.205 ms
15 ro-cj01a-rd4-ae-32-1852.aorta. net (84.116.187.82) 59.392 ms 59.410 ms 59.202 ms

14/09/2020 14:20:40 UTC

PING:
PING 78.97.202.189 (78.97.202.189) 56(84) bytes of data.
64 bytes from 78.97.202.189: icmp_seq=1 ttl=50 time=92.9 ms
64 bytes from 78.97.202.189: icmp_seq=2 ttl=50 time=50.4 ms
64 bytes from 78.97.202.189: icmp_seq=3 ttl=50 time=50.6 ms
64 bytes from 78.97.202.189: icmp_seq=4 ttl=50 time=56.8 ms

— 78.97.202.189 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 50.470/62.735/92.979/17.649 ms

14/09/2020 14:20:39 UTC

PING:
PING 78.97.202.189 (78.97.202.189) 56(84) bytes of data.
64 bytes from 78.97.202.189: icmp_seq=1 ttl=50 time=82.2 ms
64 bytes from 78.97.202.189: icmp_seq=2 ttl=50 time=68.9 ms
64 bytes from 78.97.202.189: icmp_seq=3 ttl=50 time=69.2 ms
64 bytes from 78.97.202.189: icmp_seq=4 ttl=50 time=69.3 ms

— 78.97.202.189 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 68.917/72.455/82.257/5.664 ms

14/09/2020 14:20:40 UTC

TRACEROUTE:
traceroute to 78.97.202.189 (78.97.202.189), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.423 ms 0.417 ms 0.418 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 78.97.202.189 (78.97.202.189) 49.784 ms 55.560 ms 55.575 ms

14/09/2020 14:20:39 UTC

MTR:
Start: Mon Sep 14 14:20:39 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.6 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

14/09/2020 14:20:39 UTC

MTR:
Start: Mon Sep 14 14:20:40 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.25.130 20.0% 10 274.6 284.7 256.0 311.6 17.8
3.|-- Blizzard 0.0% 10 1.0 0.9 0.8 1.0 0.0
4.|-- 137.221.66.32 0.0% 10 0.5 1.6 0.4 10.9 3.2
5.|-- 137.221.77.76 0.0% 10 138.8 73.6 7.3 264.5 93.3
6.|-- 137.221.65.35 0.0% 10 20.7 13.3 7.3 34.4 9.4
7.|-- 137.221.65.19 0.0% 10 7.4 7.4 7.3 7.5 0.0
8.|-- 137.221.79.34 0.0% 10 7.7 11.1 7.5 42.3 10.9
9.|-- uk-lon03a-ri1-ae-25-0.aorta. net 0.0% 10 7.8 7.9 7.8 8.7 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- de-fra04d-rc1-ae-56-0.aorta. net 0.0% 10 59.4 62.1 59.4 70.4 4.2
12.|-- ro-buh01a-rd3-ae-37-0.aorta. net 0.0% 10 59.6 59.6 59.4 60.4 0.0
13.|-- ro-tm01a-rd4-ae-32-1853.aorta. net 0.0% 10 59.6 59.8 59.6 60.0 0.0
14.|-- ro-tm01a-rd3-ae-33-1863.aorta. net 0.0% 10 55.3 55.5 55.3 55.9 0.0
15.|-- ro-cj01a-rd4-ae-32-1852.aorta. net 0.0% 10 59.2 59.7 59.2 63.8 1.3
16.|-- 95.77.64.148 0.0% 10 60.2 65.0 59.9 109.1 15.5
17.|-- 78.97.202.189 0.0% 10 118.8 86.4 66.9 121.6 19.8

14/09/2020 14:20:40 UTC

==============

Thank you in advance.
Radu

#2

I can’t help with feedback on the game systems, but I can help with troubleshooting. If you have additional info for developers, you’d want to post that in #general-discussion or #competitive-discussion since they don’t monitor this one.

If this is happening with every Comp match, make sure to run a Scan & Repair on the client, or reinstall, in case you are missing game assets.

Unfortunately, I have to link to a pinned thread/article, because the looking glass test pings the login server only (used for login issues or console players). Instead, please add your WinMTR. Instructions here:

The forums are not a ticket system, but they do offer one if you only want to speak with staff. Here on the forum you’ll find that the community members and MVPs are major components of the support system.

However, I noticed the ping on your home IP doesn’t look very stable, hitting 121ms, but the rest of the test from Blizzard’s end looks good.

Whether you decide to provide that WinMTR here or in the ticket system, you can also check the results on your own while waiting for a response. Look for % loss on individual nodes, as well as very long response times like the one above. Please note that Blizzard nodes generally show bad ping response times of over 3000ms because they ignore some traffic from WinMTR tests, which causes the value to inflate.