Me and my wife are DC every 2 hours or so , most even on the minute like 16:16 - 18:16 and so on . We share the same Internet connecting . I did run WinMTR the past copple of hours . Would be great to know what i can do more to solve the problem. After Reset my IP, make a 7 day lease time on the IP and even Factory reset the Router
WinMTR Statistics
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.0.1 | 0 | 5536 | 5536 | 0 | 0 | 25 | 0 |
| 10.43.7.254 | 0 | 5536 | 5536 | 4 | 9 | 145 | 12 |
| 188.64.255.105 | 1 | 5532 | 5531 | 4 | 9 | 106 | 6 |
| 185.143.169.25 | 0 | 5536 | 5536 | 4 | 10 | 144 | 12 |
| 185.143.169.10 | 0 | 5536 | 5536 | 5 | 10 | 150 | 15 |
| 185.143.169.55 | 1 | 5532 | 5531 | 7 | 11 | 114 | 9 |
| ddf-b2-link.telia.net | 0 | 5536 | 5536 | 7 | 13 | 144 | 12 |
| adm-bb4-link.telia.net | 0 | 5536 | 5536 | 11 | 14 | 125 | 15 |
| adm-b2-link.telia.net | 1 | 5532 | 5531 | 10 | 15 | 150 | 22 |
| blizzard-ic-348623-adm-b2.c.telia.net | 1 | 5532 | 5531 | 10 | 17 | 454 | 83 |
| ae1-br02-eqam1.as57976.net | 1 | 5441 | 5429 | 10 | 36 | 4654 | 13 |
| et-0-0-67-pe01-eqam1.as57976.net | 0 | 5536 | 5536 | 10 | 18 | 151 | 19 |
| 185.60.112.157 | 0 | 5536 | 5536 | 10 | 14 | 42 | 17 |
And this one right after the last DC
WinMTR Statistics
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.0.1 | 1 | 291 | 290 | 0 | 0 | 13 | 0 |
| 10.43.7.254 | 1 | 287 | 285 | 4 | 9 | 21 | 10 |
| 188.64.255.105 | 1 | 287 | 285 | 5 | 9 | 36 | 12 |
| 185.143.169.25 | 1 | 287 | 285 | 6 | 10 | 33 | 11 |
| 185.143.169.10 | 1 | 287 | 285 | 5 | 10 | 28 | 10 |
| 185.143.169.55 | 1 | 287 | 285 | 8 | 12 | 28 | 15 |
| ddf-b2-link.telia.net | 1 | 287 | 285 | 7 | 13 | 72 | 14 |
| adm-bb4-link.telia.net | 1 | 287 | 285 | 11 | 16 | 26 | 16 |
| adm-b2-link.telia.net | 1 | 287 | 285 | 12 | 16 | 27 | 19 |
| blizzard-ic-348623-adm-b2.c.telia.net | 1 | 287 | 285 | 10 | 18 | 72 | 17 |
| ae1-br02-eqam1.as57976.net | 1 | 287 | 285 | 10 | 17 | 118 | 15 |
| et-0-0-67-pe01-eqam1.as57976.net | 1 | 287 | 285 | 11 | 18 | 75 | 15 |
| 185.60.112.157 | 1 | 287 | 285 | 10 | 15 | 26 | 15 |
Heya Aeden,
That’s some fantastic troubleshooting and you have hit the nail on the head narrowing it down to a probable router issue. Typically, this is a DHCP leasing issue as you instinctively went to. If you are connecting wirelessly “Group Key Renewal” (wording may vary) is another setting which would work similarly and may be something on your router.
If this isn’t something you have, I’d check with your ISP for firmware any pending updates along with any other settings they have unique to their router configuration. The only other settings, I could think of is QoS, which turning off may also help.
Thanks for the answer Mosinathus
I hope i did some troubleshooting right atleast. But no, im Hard wired , so with a LAN cable but my wife uses WIFI from her Laptop and we both Disconnect at the same time ever Hour on 16min in that hour after i Factory reset my router. The Router is a ARRIS model TG862S with 100mb/s and my Internet Provider said that it cant be changed to a NETGEAR or a ASUS ,so im stucked with it so far. Another thing is that i even get kicked from Diablo 3 at the same time if that helps . Is there a way that i can see ( like softwares ) what the reason is that i Disconnect ( at the moments ) from the Games that i can show my IP Provider becouse im sure they just gonna push the problem to Blizzard .
Thats a really unusual situation you found yourself in there, Aeden.
The forced disconnection being on such an exact timer would very much fit a faulty DHCP lease in the router but since that has already been checked - honestly, I would have to suspect the device itself may be the root cause of the issue here. There have been reports of various ARRIS-brand routers using the historically rather controversial Intel Puma 6 chipset, so there is at least a chance the same may be true for the TG862S model - but the symptoms you described are untypically drastic even for that scenario.
My best suggestion here would be to utterly bypass the router for a test, and see if the problem disappears - for example, via using a mobile phone tether/hotspot, or a friendly neighbours WIFI (if one such is available). If it does that should hopefully be suitably clear evidence to have the device replaced (or at least repaired) by the ISP.
Any idea what that is ? I did a Pathping test with 3 European servers and one of them did gave me that
Tracing route to 185.60.112.158 over a maximum of 30 hops
0 DESKTOP-2J9831I [192.168.0.4]
1 192.168.0.1
2 10.43.7.254
3 188.64.255.105
4 185.143.169.25
5 185.143.169.5
6 185.143.169.1
7 185.143.169.55
8 ddf-b2-link.telia. nett [213.248.78.104]
9 adm-bb4-link.telia. nett [62.115.143.162]
10 adm-b2-link.telia. nett [62.115.141.195]
11 blizzard-ic-348623-adm-b2.c.telia. nett [62.115.178.203]
12 ae1-br01-eqam1.as57976. nett [137.221.78.33]
13 et-0-0-31-pe01-eqam1.as57976. nett [137.221.78.67]
14 137.221.66.41
15 185.60.112.158
Computing statistics for 375 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-2J9831I [192.168.0.4]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.43.7.254
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% 188.64.255.105
0/ 100 = 0% |
4 8ms 1/ 100 = 1% 1/ 100 = 1% 185.143.169.25
0/ 100 = 0% |
5 8ms 0/ 100 = 0% 0/ 100 = 0% 185.143.169.5
0/ 100 = 0% |
6 9ms 0/ 100 = 0% 0/ 100 = 0% 185.143.169.1
0/ 100 = 0% |
7 11ms 0/ 100 = 0% 0/ 100 = 0% 185.143.169.55
0/ 100 = 0% |
8 12ms 0/ 100 = 0% 0/ 100 = 0% ddf-b2-link.telia. nett [213.248.78.104]
0/ 100 = 0% |
9 16ms 0/ 100 = 0% 0/ 100 = 0% adm-bb4-link.telia. nett [62.115.143.162]
0/ 100 = 0% |
10 15ms 0/ 100 = 0% 0/ 100 = 0% adm-b2-link.telia. nett [62.115.141.195]
0/ 100 = 0% |
11 19ms 0/ 100 = 0% 0/ 100 = 0% blizzard-ic-348623-adm-b2.c.telia. nett [62.115.178.203]
0/ 100 = 0% |
12 15ms 0/ 100 = 0% 0/ 100 = 0% ae1-br01-eqam1.as57976. nett[137.221.78.33]
0/ 100 = 0% |
13 16ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-31-pe01-eqam1.as57976. nett [137.221.78.67]
0/ 100 = 0% |
14 — 100/ 100 =100% 100/ 100 =100% 137.221.66.41
0/ 100 = 0% |
15 14ms 0/ 100 = 0% 0/ 100 = 0% 185.60.112.158
Trace complete.
That pathping looks pretty solid actually. At least during the time this data was captured the connection seems to have been just fine, but it should be noted that such tests do not capture every potential kind of issue (especially not if the root cause is not actually a technical problem but rather an unwanted system/router setting).
Did you have any chance to test bypassing the router, to see if that made any difference?
I did bypass it with my Mobile and no Problems than . i did the same Pathping test right before the Disconnection and that was the result just now . ( The DCs is now in 2 hours distance but every time at a 36min mark so i did start the test at a 34min mark). And my ISP will look deeper in that problem but i really think that i could need a new Modem.
Tracing route to 185.60.112.157 over a maximum of 30 hops
0 DESKTOP-2J9831I [192.168.0.4]
1 192.168.0.1
2 10.43.7.254
3 188.64.255.105
4 185.143.169.25
5 185.143.169.5
6 185.143.169.1
7 185.143.169.55
8 ddf-b2-link.telia.nett [213.248.78.104]
9 adm-bb4-link.telia.nett [62.115.143.162]
10 adm-b2-link.telia.nett [62.115.141.195]
11 blizzard-ic-348623-adm-b2.c.telia.nett [62.115.178.203]
12 ae1-br02-eqam1.as57976.nett [137.221.78.35]
13 et-0-0-67-pe01-eqam1.as57976.nett [137.221.78.71]
14 185.60.112.157
Computing statistics for 350 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-2J9831I [192.168.0.4]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
1/ 100 = 1% |
2 7ms 72/ 100 = 72% 71/ 100 = 71% 10.43.7.254
0/ 100 = 0% |
3 8ms 71/ 100 = 71% 70/ 100 = 70% 188.64.255.105
0/ 100 = 0% |
4 7ms 1/ 100 = 1% 0/ 100 = 0% 185.143.169.25
0/ 100 = 0% |
5 7ms 1/ 100 = 1% 0/ 100 = 0% 185.143.169.5
1/ 100 = 1% |
6 9ms 71/ 100 = 71% 69/ 100 = 69% 185.143.169.1
0/ 100 = 0% |
7 10ms 71/ 100 = 71% 69/ 100 = 69% 185.143.169.55
0/ 100 = 0% |
8 11ms 72/ 100 = 72% 70/ 100 = 70% ddf-b2-link.telia.nett [213.248.78.104]
0/ 100 = 0% |
9 14ms 2/ 100 = 2% 0/ 100 = 0% adm-bb4-link.telia.nett [62.115.143.162]
0/ 100 = 0% |
10 15ms 2/ 100 = 2% 0/ 100 = 0% adm-b2-link.telia.nett [62.115.141.195]
1/ 100 = 1% |
11 18ms 3/ 100 = 3% 0/ 100 = 0% blizzard-ic-348623-adm-b2.c.telia.nett [62.115.178.203]
0/ 100 = 0% |
12 16ms 3/ 100 = 3% 0/ 100 = 0% ae1-br02-eqam1.as57976.nett [137.221.78.35]
0/ 100 = 0% |
13 16ms 3/ 100 = 3% 0/ 100 = 0% et-0-0-67-pe01-eqam1.as57976.ne [137.221.78.71]
0/ 100 = 0% |
14 13ms 3/ 100 = 3% 0/ 100 = 0% 185.60.112.157
Trace complete.
The bolded parts are data packet losses measured by the pathping test, which are surprisingly high - and did not exist in the other test, which I assume was taken not as close to the regular disconnection event.
Assuming this is real loss it would indicate some rather severe issues on the affected nodes, factoring in the time component I’d have to guess this is some form of scheduled automated event running on the node which causes additional load/congestion (could be a proxy/cache update possibly, assuming one such is being used… sadly impossible to determine from data logs alone).
Either way that’d definitely be something your ISP would want to look into, especially since the bypass via the mobile connection setup has already proven that the issue is unique to the regular router/line structure.
Is there any kind of other Software that i could use and show my ISP that my Disconnections happen at every 36mins on the hours and what exactly happens at that time ? becouse i start to have a feeling that i need to spoon feed them every information that i can provide like a baby . Maybie thats gona help speed up the fix with the Disconnections ?
Not sure software-capture is your best bet here, or that you should really be put into a position where you’d need to be the one that provides the evidence. You could probably set up automated capture with Wireshark or a similar tool, but how much that’d prove is anyones guess - especially since it should actually not be too hard to see the connection drop remotely from the ISPs end, if they monitor your line.
Speaking purely personally right now: I’d probably request for an ISP technician to be at my residence at 30 minutes past the hour, hand them a cup of tea and have them sit at the computer to look at the clock for a couple minutes. 
Veadsarius
Is it not strange that all of a sudden players all over Europe with different net-companies all of a sudden 2 weeks started to get this strange disconnections, I am one of them as you can see from my thread. I do not buy this as NOTHING else is disconnected only WOW.
I have now as a desperate last move deleted classic and reinstalled. I do not use any addon. I have updated all drivers. I have done a repair. I have rebooted my router, I use cabel. Might forgot something I done, but I have done all you said I should do to troubleshoot. I did not get an answer on my thread so I am here instead trying to get your attention. I still get disconnections with the same error message that say I have lost connection with blizzards server. I get random disconnects, sometimes 2 times/hour, sometimes after several hours, sometimes the same time a log in.
Conifer: I am pretty sure your specific issue is quite different from what this thread is about - and no, its honestly not strange that in a game that has so many players that some small percentile of that user base will be encountering some form of issue at any given day. That just the law of large numbers fully at work. 
From a gut feeling: if you happen to be using ASUS/ROG “GameFirst” then I’d suggest to uninstall that, since it has been reported by several players lately to cause connection issues specifically with the most recent version of WoW Classic. If that is not the case for you - please do add to your own thread the full network and hardware diagnostic logs (the included test in your thread was sadly very incomplete), so we can both explore this in full and avoid muddying the waters here.