Constant disconnect from game servers

Technical Support
1

Hello and thank you for your time.

I’m seriously confused. I could play Overwatch for months without problems and suddenly, I get disconnected from the game servers every single time after a couple of seconds into a game. It even happens during skirmish / etc. while queueing for quick play.

I have not done any major (or even minor as I am aware of) changes to my pc, the problems just “suddenly” appeared.

I tried rebooting my network, updated my network driver, reset winsock data, flushed my DNS and renewed my IP.

Since it went without problems in the past, I did not have any new major bandwith-hogging applications running (tried it without my normal ones, but to no avail).

I am connected via LAN, so wireless interference is out of the question.

I’ve run the Looking-Glass and the output was the following:

TRACEROUTE:
traceroute to 37.201.144.16 (37.201.144.16), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.359 ms 0.345 ms 0.341 ms
2 37.244.24.131 (37.244.24.131) 1.031 ms 1.035 ms 1.032 ms
3 Blizzard Blizzard 1.380 ms 1.425 ms 1.470 ms
4 137.221.66.46 (137.221.66.46) 0.597 ms 0.604 ms 0.603 ms
5 137.221.78.88 (137.221.78.88) 1.171 ms 1.171 ms 1.169 ms
6 137.221.78.34 (137.221.78.34) 1.438 ms 1.160 ms 1.123 ms
7 nl-ams14a-ri1-ae-26-0.aorta. net (213.46.182.193) 0.859 ms 0.862 ms 0.858 ms
8 * * *
9 de-dus23e-rc1-ae-19-0.aorta. net (84.116.138.205) 11.894 ms 11.909 ms 11.907 ms
10 de-bfe18a-rd01-ae-1-0.aorta. net (84.116.191.122) 10.662 ms 11.412 ms 11.364 ms
11 84.116.190.26 (84.116.190.26) 9.962 ms 9.833 ms 9.860 ms
12 * * *
13 * * *
14 * * *
15 * * *

29/05/2020 23:35:33 UTC

PING:
PING 37.201.144.16 (37.201.144.16) 56(84) bytes of data.

— 37.201.144.16 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2997ms

29/05/2020 23:35:33 UTC

MTR:
Start: Fri May 29 23:35:33 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- 37.244.24.131 0.0% 10 0.5 0.6 0.5 0.9 0.0
3.|-- Blizzard 0.0% 10 1.6 1.4 1.3 1.6 0.0
4.|-- 137.221.66.46 0.0% 10 0.5 3.4 0.5 27.8 8.6
5.|-- 137.221.78.88 0.0% 10 3.3 2.8 1.0 15.8 4.6
6.|-- 137.221.78.34 0.0% 10 48.6 12.7 1.0 53.6 20.8
7.|-- nl-ams14a-ri1-ae-26-0.aorta. net 0.0% 10 0.8 2.5 0.8 17.1 5.1
8.|-- nl-ams02a-rc2-lag-5-0.aorta. net 90.0% 10 1.4 1.4 1.4 1.4 0.0
9.|-- de-dus23e-rc1-ae-19-0.aorta. net 0.0% 10 28.1 15.7 9.9 29.8 7.3
10.|-- de-bfe18a-rd01-ae-1-0.aorta. net 0.0% 10 10.8 10.4 10.3 10.8 0.0
11.|-- 84.116.190.26 0.0% 10 9.9 9.9 9.8 10.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

29/05/2020 23:35:33 UTC

-> I had to include some spaces between some lines, for example “[…]19-0.aorta .net […]” since it was considered a link.

I really hope that someone can help me fix my problems. Thank you in advance.

2

I seem to be having the same problem and have been for a couple of weeks now but my ping just gets higher and higher reaching 3000 almost every time. What’s your ping like before you get kicked?

3

It looks like Blizzard is having trouble reaching you from their servers and your connection is rejecting pings. Can you add a WinMTR instead?

Click here to show/hide WinMTR instructions

Players in the Americas and Oceania regions: Follow the Blizzard support documentation for WinMTR.

  • Make sure your issue is caught in the test or you run it for at least 5 minutes.
  • Players on EU servers: please follow the same directions, except you’ll want to post results in the EU Tech Support forum.

Share your results in a reply:

  1. Click the “Copy Text to clipboard” button after you’ve finished the test.
  2. Paste the text in a reply, highlight it, then click </> on the post editor.
  3. If you can’t post links, add spaces before .com/.net/.us/.au, etc., which will break the link and allow you to post.

Please do not remove full hostnames from the test instead of “breaking the links” with spaces, as this makes troubleshooting much more difficult.

4

I tried my hands at the WinMTR, hopefully I did it right.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                               fritz.box -    0 |  397 |  397 |    0 |    0 |    2 |    0 |
|                          compalhub.home -    0 |  397 |  397 |    1 |    3 |   21 |    4 |
|                           84.116.198.72 -    1 |  389 |  387 |   13 |   92 | 1573 |   17 |
|        de-bfe18a-rd01-ae-18-0.aorta.net -    1 |  389 |  387 |   20 |   98 | 1574 |   46 |
|         de-bfe18a-rd02-ae-0-0.aorta.net -    1 |  389 |  387 |   20 |   90 | 1067 |   47 |
|         de-fra01b-rc1-ae-65-0.aorta.net -    1 |  389 |  387 |   18 |   95 | 1604 |   33 |
|           ch-otf01b-ra1-ae8-0.aorta.net -    1 |  385 |  382 |   18 |   86 | 1074 |   58 |
|                 213.46.179.58.aorta.net -    1 |  385 |  382 |   18 |   89 | 1125 |   47 |
|              ae1-br01-eqfr5.as57976.net -    5 |  338 |  324 |   21 |  101 | 3281 |   29 |
|         et-0-0-2-br01-eqam1.as57976.net -    7 |  309 |  288 |   21 |  132 | 3350 |   52 |
|        et-0-0-35-pe02-eqam1.as57976.net -    1 |  389 |  387 |   20 |   94 | 1067 |   59 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   79 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
5

Thank you, Steech! The test looks like it was done properly :slight_smile: The problem is starting after it leaves the home network here:

| 84.116.198.72 - :warning: 1 | 389 | 387 | 13 | 92 | 1573 | 17 |

This is a liberty global peer, which is apart of the ISPs network. The latency is quite high here. After this hop, there’s a consistent amount of packet loss that gradually increases by the time it reaches the AMS1 servers.

With the packet loss and high latency starting at the liberty global peer, this will need to be addressed by the ISP to look into what’s causing the packet loss and if there may be any home network or signal/line issues near the home.