Would someone at Blizzard do there job and make sure we don’t get DCed, Thank you!
Dude I get DCed in the middle of a GR happened 5+ times tonight
Since the forums aren’t flooded with complaints about disconnections you can safely assume it’s not a mass problem, so it’s highly unlikely to be at the server end.
Carry out the analysis suggested in the post. Make a thread in Tech Support and actually provide enough information for people to investigate the problem.
Remember that the route your network traffic takes between your PC and Blizzard’s servers goes through multiple hops, any of which could have a fault or be dropping packets, all of which are outside the responsibility and purview of Blizzard.
@SeaBigBear
Which means you may have to contact your ISP to have them troubleshoot and/or maintenance your service.
Which will, hopefully, help Blizzard and other players help you determine what your issue is, so you know where to start looking for a solution.
Good luck.
Blizz wtf my mouse keeps sticking. Fix ploz1111one
Looks more like your 1 key got stuck instead.
Bahahaha.
I’m still getting DCed & I have done the IP Release, Renew, and Flush DNS thing too!
Would you run WinMTR test and paste the result?
We cannot help you without any information.
The support article given by Meteorblade contains the steps of how to run WinMTR.
Here it is:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
10.0.0.1 - 0 | 43 | 43 | 1 | 12 | 17 | 11 |
96.120.28.141 - 0 | 43 | 43 | 8 | 12 | 20 | 10 |
po91-rur01.warsaw.in.chicago.comcast net - 0 | 43 | 43 | 9 | 11 | 15 | 10 |
162.151.184.117 - 0 | 43 | 43 | 16 | 18 | 24 | 18 |
be-33491-cr02.350ecermak.il.ibone.comcast net - 0 | 43 | 43 | 14 | 19 | 26 | 18 |
be-10563-pe01.350ecermak.il.ibone.comcast net - 0 | 43 | 43 | 13 | 15 | 24 | 15 |
50.242.151.154 - 0 | 43 | 43 | 14 | 21 | 72 | 50 |
ae1-br01-eqch2.as57976 net - 0 | 43 | 43 | 72 | 91 | 368 | 72 |
137.221.65.132 - 0 | 42 | 42 | 71 | 162 | 1067 | 72 |
No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
be1-pe01-eqla1.as57976 net - 0 | 43 | 43 | 73 | 75 | 79 | 75 |
lax-eqla1-ia-bons-02.as57976 net - 0 | 43 | 43 | 74 | 76 | 81 | 77 |
24.105.30.129 - 0 | 43 | 43 | 70 | 73 | 85 | 74 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Please follow the instructions, I.e. run for 10 minutes while you experience latency or disconnection.
From your short run, I don’t see any issue.
If you are using wireless connection, try testing with wired connection.
here:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
10.0.0.1 - 0 | 1472 | 1472 | 0 | 10 | 75 | 48 |
96.120.28.141 - 1 | 1468 | 1467 | 7 | 12 | 70 | 16 |
po91-rur01.warsaw.in.chicago.comcast net - 1 | 1468 | 1467 | 7 | 11 | 62 | 14 |
162.151.184.117 - 1 | 1468 | 1467 | 13 | 17 | 40 | 14 |
be-33491-cr02.350ecermak.il.ibone.comcast net - 1 | 1468 | 1467 | 14 | 19 | 41 | 19 |
be-10563-pe01.350ecermak.il.ibone.comcast net - 1 | 1468 | 1467 | 13 | 17 | 44 | 21 |
50.242.151.154 - 1 | 1468 | 1467 | 13 | 21 | 447 | 18 |
ae1-br01-eqch2.as57976 net - 1 | 1454 | 1452 | 70 | 94 | 4618 | 71 |
137.221.65.132 - 1 | 1468 | 1467 | 70 | 84 | 1067 | 73 |
et-0-0-2-br01-eqla1.as57976 net - 1 | 1416 | 1406 | 0 | 154 | 3804 | 537 |
be1-pe01-eqla1.as57976 net - 1 | 1468 | 1467 | 70 | 74 | 119 | 76 |
lax-eqla1-ia-bons-02.as57976 net - 1 | 1468 | 1467 | 71 | 75 | 137 | 78 |
24.105.30.129 - 1 | 1464 | 1462 | 69 | 72 | 119 | 70 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
96.120.28.141 - 1 1468 1467 7 12 70 16
At hop 2 and onwards, there are some data packet loss. I.e. some problems between your router/modem and your ISP gateway.
If problem continues after power cycling your router/modem, you should contact your ISP (comcast?) to resolve the problem; show them this WinMTR log.
Thank you & I will look in to this!