Disconnects after my ping climbs to 3000

Ethan0754-1607 · June 2, 2020, 2:48am

Over the past couple of weeks this has been happening and I’m not sure what is happening.

I get disconnected after my ping climbing to 3000 or more and then it sends me right back into the menu like nothing happened.

It only happens when I’m tabbed into the game and when i tab out to my other screen my ping shows 60.

This also changes based on the day. One day it will be perfectly normal with 60 ping the whole day and then the next I will just have to take a break from the game because I get disconnected after 30s or so.

Here are results from Battle.net Looking Glass
~~

TRACEROUTE:
traceroute to 73.24.56.164 (73.24.56.164), 15 hops max, 60 byte packets
1 Blizzard Blizzard 4.829 ms 4.808 ms 4.806 ms
2 24.105.18.3 (24.105.18.3) 4.830 ms 4.831 ms 4.831 ms
3 137.221.105.16 (137.221.105.16) 4.832 ms 4.833 ms 4.834 ms
4 137.221.66.22 (137.221.66.22) 4.783 ms 4.782 ms 4.783 ms
5 137.221.83.86 (137.221.83.86) 8.471 ms 8.473 ms 8.473 ms
6 137.221.65.68 (137.221.65.68) 8.437 ms 6.133 ms 6.119 ms
7 137.221.68.32 (137.221.68.32) 6.774 ms 6.786 ms 6.784 ms
8 te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcast. net (50.242.151.165) 6.055 ms 6.084 ms 6.064 ms
9 be-11587-cr02.losangeles.ca.ibone.comcast. net (68.86.83.17) 6.918 ms 8.334 ms 8.325 ms
10 be-11523-cr01.houston.tx.ibone.comcast. net (68.86.87.174) 33.656 ms 33.652 ms 33.152 ms
11 be-12324-cr02.dallas.tx.ibone.comcast. net (68.86.84.110) 33.462 ms 32.783 ms 32.774 ms
12 be-7922-ar01.sshackleford.ar.lrock.comcast .net (68.86.90.214) 38.611 ms 38.609 ms 38.599 ms
13 162.151.130.130 (162.151.130.130) 38.575 ms 38.728 ms 38.721 ms
14 96.110.100.202 (96.110.100.202) 38.705 ms 38.622 ms 38.595 ms
15 c-73-24-56-164.hsd1.ar.comcast. net (73.24.56.164) 55.206 ms 51.640 ms 51.623 ms

02/06/2020 02:40:45 UTC

PING:
PING 73.24.56.164 (73.24.56.164) 56(84) bytes of data.
64 bytes from 73.24.56.164: icmp_seq=1 ttl=52 time=49.6 ms
64 bytes from 73.24.56.164: icmp_seq=2 ttl=52 time=47.4 ms
64 bytes from 73.24.56.164: icmp_seq=3 ttl=52 time=49.6 ms
64 bytes from 73.24.56.164: icmp_seq=4 ttl=52 time=48.5 ms

— 73.24.56.164 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 47.437/48.824/49.673/0.924 ms

02/06/2020 02:40:46 UTC

MTR:
Start: Tue Jun 2 02:40:45 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.5 0.2 1.9 0.5
2.|-- 24.105.18.3 0.0% 10 0.5 0.8 0.5 2.0 0.0
3.|-- 137.221.105.16 0.0% 10 1.0 0.9 0.8 1.0 0.0
4.|-- 137.221.66.22 0.0% 10 0.6 4.2 0.3 37.3 11.6
5.|-- 137.221.83.86 0.0% 10 5.8 7.4 5.7 21.8 5.0
6.|-- 137.221.65.68 0.0% 10 5.8 15.6 5.8 68.1 20.6
7.|-- 137.221.68.32 0.0% 10 5.8 6.0 5.8 6.4 0.0
8.|-- te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcast. net 0.0% 10 5.7 5.7 5.6 5.8 0.0
9.|-- be-11587-cr02.losangeles.ca.ibone.comcast. net 0.0% 10 7.2 7.1 6.1 8.3 0.5
10.|-- be-11523-cr01.houston.tx.ibone.comcast. net 0.0% 10 32.5 33.5 32.5 34.3 0.5
11.|-- be-12324-cr02.dallas.tx.ibone.comcast. net 0.0% 10 32.7 33.6 32.6 34.8 0.3
12.|-- be-7922-ar01.sshackleford.ar.lrock.comcast. net 0.0% 10 38.4 38.4 38.3 38.6 0.0
13.|-- 162.151.130.130 0.0% 10 38.5 38.6 38.5 38.6 0.0
14.|-- 96.110.100.202 0.0% 10 38.7 38.7 38.6 38.8 0.0
15.|-- c-73-24-56-164.hsd1.ar.comcast. net 0.0% 10 52.3 50.3 48.8 53.2 1.3

02/06/2020 02:40:45 UTC

~~

Blockquote

Nicole-1893 · June 2, 2020, 4:42am

Looking glass tests aren’t the best for diagnosing this. I suggest providing a WinMTR instead

Ethan0754-1607 · June 2, 2020, 5:17pm

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| 10.0.0.1 - 31 | 13 | 9 | 13 | 809 | 4947 | 17 |

| 96.120.23.13 - 31 | 13 | 9 | 12 | 809 | 4947 | 12 |

| 96.110.100.201 - 31 | 13 | 9 | 12 | 810 | 4946 | 18 |

|be-111-ar01.sshackleford.ar.lrock.comcast. net - 31 | 13 | 9 | 14 | 839 | 4954 | 18 |

|be-33656-cr02.dallas.tx.ibone.comcast. net - 31 | 13 | 9 | 19 | 816 | 4961 | 22 |

|be-12495-pe03.1950stemmons.tx.ibone.comcast. net - 31 | 13 | 9 | 18 | 815 | 4961 | 20 |

| 50.208.232.130 - 29 | 14 | 10 | 19 | 739 | 2557 | 33 |

| ae1-br01-eqda6.as57976. net - 29 | 14 | 10 | 42 | 766 | 2580 | 48 |

| et-0-0-4-br01-eqch2.as57976. net - 29 | 14 | 10 | 41 | 773 | 2578 | 49 |

| et-0-0-0-pe02-eqch2.as57976. net - 29 | 14 | 10 | 40 | 777 | 2578 | 48 |

| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |

|____________|||||||

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

I wasnt able to run it for 5 minutes after the issue due to getting disconnected

Caterpepi · June 2, 2020, 9:18pm

Hey, Ethan0754! Thanks for the connection test. It’s a bit short, since it was only ran for a few seconds, but the problem is starting at the home network.

There’s a 31% packet loss, and the average latency is spiking up to 809. The worst latency is reaching almost 5000ms. In this situation, it can help to try the following:

Reset the network device
Reset network settings:
1. Click on the Start Menu
2. Select on the Settings option.
3. In the Windows Settings, click on “Network & Internet”
4. Near the bottom of the new window, click on “Network Reset”
Try again, and if it persists, try rebooting to help with the changes made from the Network Reset.

If the problem continues, please contact the ISP to address the packet loss and high latency on the home network.