Constant d/c… please help! It’s nap time which means pops can play video games!
I had this issue on classic yesterday got dc’d 20-30 times all within 5-10 minutes a piece. I put a ticket into blizzard who wanted all this spec info on my PC. Now today I cannot log in at all. My battlenet keeps going offline and I cant log into classic
I had the same issue since April 13th, I could simply predict I would get disconnected by simply moving stuff on my bags which wern’t moving, or seeing people run still.
Starting April 16 it was way more frequent. What’s even more strange is that I do not have this issue playing on another computer within the same network. I did a reset of my modem/router etc etc and the issue persisted on my main computer. WoW + every other Battle.net game and Battle.net client has been uninstalled and I even manually deleted every folder of Blizzard Entertainment / WoW in Program Files and AppData. I still had the issue afterward even after a clean reinstall with no AddOns.
I did all available Windows Update + GPU driver and now it seems to be fine since yesterday evening, currently monitoring.
Playing Classic Wotlk on Faerlina
I too have been getting disconnected all day long, if I can even get past the splash screen without being disconnected. If I can get to connect I am on for maybe a minute of that and then it drops me. Here is the trace route to US (West)
1 10.0.4.1 (10.0.4.1) 0.805 ms 0.482 ms 0.465 ms 0.481 ms 0.468 ms 0.604 ms * 0.559 ms 0.604 ms 0.619 ms 0.460 ms 0.491 ms * 0.548 ms 0.647 ms 0.627 ms 0.626 ms 0.633 ms * 0.676 ms (15% loss)
2 192.168.1.254 (192.168.1.254) 1.741 ms 1.681 ms 1.609 ms 1.808 ms 1.810 ms 1.584 ms * 1.716 ms 1.439 ms 1.330 ms 1.450 ms 1.548 ms * 1.669 ms 1.450 ms 1.614 ms 1.373 ms 1.823 ms * 1.782 ms (15% loss)
3 76-206-252-1.lightspeed.irvnca.sbcglobal.net (76.206.252.1) 18.520 ms 18.050 ms 18.295 ms 17.930 ms 18.641 ms 18.213 ms 18.281 ms 18.190 ms 17.791 ms 17.523 ms 18.205 ms 17.996 ms 18.194 ms 17.927 ms 17.909 ms 18.032 ms 17.583 ms 17.958 ms 18.156 ms 18.126 ms (0% loss)
4 70.232.228.61 (70.232.228.61) 18.275 ms 19.001 ms 18.678 ms 18.629 ms 18.968 ms 18.885 ms 18.761 ms 18.912 ms 19.242 ms 19.209 ms 18.679 ms 18.870 ms 18.437 ms 18.535 ms 18.560 ms 18.971 ms 18.658 ms 18.638 ms 19.502 ms 18.974 ms (0% loss)
5 12.242.115.33 (12.242.115.33) 21.967 ms 22.599 ms 21.317 ms 22.047 ms 22.279 ms 21.613 ms 21.850 ms 21.788 ms 21.795 ms 22.048 ms 21.461 ms 21.742 ms 21.333 ms 21.596 ms 21.716 ms 21.959 ms 21.850 ms 21.523 ms 21.339 ms 21.361 ms (0% loss)
6 * * * * * * * * * * * * * * * * * * * * (100% loss)
7 * * * * * * * * * * * * * * * * * * * * (100% loss)
8 * * * * * * * * * * * * * * * * * * * * (100% loss)
9 * * * * * * * * * * * * * * * * * * * * (100% loss)
10 * * * * * * * * * * * * * * * * * * * * (100% loss)
11 * * * * * * * * * * * * * * * * * * * * (100% loss)
12 * * * * * * * * * * * * * * * * * * * * (100% loss)
13 * * * * * * * * * * * * * * * * * * * * (100% loss)
14 * * * * * * * * * * * * * * * * * * * * (100% loss)
15 * * * * * * * * * * * * * * * * * * * * (100% loss)
16 * * * * * * * * * * * * * * * * * * * * (100% loss)
17 * * * * * * * * * * * * * * * * * * * * (100% loss)
18 * * * * * * * * * * * * * * * * * * * * (100% loss)
19 * * * * * * * * * * * * * * * * * * * * (100% loss)
20 * * * * * * * * * * * * * * * * * * * * (100% loss)
21 * * * * * * * * * * * * * * * * * * * * (100% loss)
22 * * * * * * * * * * * * * * * * * * * * (100% loss)
23 * * * * * * * * * * * * * * * * * * * * (100% loss)
24 * * * * * * * * * * * * * * * * * * * * (100% loss)
25 * * * * * * * * * * * * * * * * * * * * (100% loss)
26 * * * * * * * * * * * * * * * * * * * * (100% loss)
27 * * * * * * * * * * *
Howdy!
Reports of this issue have dropped off significantly over the last 24 hours. This issue appears to have been resolved. Please note that the disconnection error code WOW51900319 error is a standard disconnection error in general, other sources may cause it. If you continue to run into this issue, please follow the troubleshooting Here, and create a new thread with a WinMTR.
Closing this thread as the issue is resolved, we want to separate any other issues from this moving forward to avoid confusion.
Thank you.