UK based here, on an enterprise ISP. I have been having the same trouble for a week now as well. I’m currently using a VPN to circumvent the disconnects and it has been working so far and have been on for 8+ hours a day for three days now since starting the VPN, with maybe one or two disconnects.
It’s almost like micro-disconnets, and my Bnet launcher goes down with the WoW client, very strange.
1 Like
why cant we get a bluepost about this? blizz plz
Yes I was in UK at that time, particulary in Scotland
1 Like
Micro disconnections is a bloody good term, that is it exactly, its as if the game dies for a second which is enough to disconnect.
Its happening less but its still happening.
I got the usual Blizzard copy and paste answers which are no help at all, I’d prefer them to say its a problem and they are dealing with it.
1 Like
I had similar problems when Prepatch rolled out, but has seemed to have stabilised and have been able to play uninterrupted without a VPN all day yesterday.
Not sure what they did, but at least for me, this has been resolved… for now. Finger’s crossed!
Edit: I clearly spoke too soon, and now it’s very frequent.
bumping the post so perhaps we might get an answer
1 Like
Clearly a couple of people have the issue. Symptoms sound very weird though. There’s been other issues for a long time (since January/February-ish) but the issue some others (me included) are facing is entirely different from what you guys are experiencing. A little weird that most of this thread has been having this issue for quite some time, whereas Ceasium just had it happen when Prepatch dropped.
Best I can offer is to dig into some of the older network connectivity troubleshoots Blizzard used to ask for and have you guys do a WinMTR or Traceroute (how to do that is also linked on the righthand side of the article posted). But I am not certain if analyzing the routing here necessarily provides any super valuable info on what’s happening, especially if you’re constantly disconnecting not just from the game, but essentially (as you say) get a complete disconnect on the device and the MTR won’t be able to run uninterrupted for the amount of time it’s usually supposed to be run for when it comes to Blizzard troubleshooting (5-10 mins).
If this truly only happens with WoW and nowhere else, that is the only thing that might tie your symptoms with some of the other network issues reported this year. It’s either connected to the Blizzard node packet loss thing or there really is some (sorry not sorry for the language) dumb a** ISP stuff going on specifically with people trying to play WoW.
If you have it available, try Hearthstone as well. From what I could gather, Hearthstone will try to connect you to some of the same IPs listed for WoW in the troubleshoots and my own issues have in fact also happened when connecting to Hearthstone. It may seem unrelated to your issue at first, but if you also face the same disconnect issue in Hearthstone as well it at the very least takes the issue away from “just WoW” and towards “Blizzard Games routing through the same destinations”.
Maybe something interesting crops up or perhaps this is a different symptom of the same issue.
Other than that, all I can provide is this bump and wishing you guys luck with getting any help or response from the Blues themselves. Finger’s crossed.
little patch this morning, but still disconnects out of nowhere. By just watching a ingame scene and doing nothing. The game just crashed.
I think it’s ridiculous that I had to use the waybackwhen machine to find data on this stuff.
I’ve done several 10min WinMTR’s to their listed IP’s and eu.battle.net and it seems like the problem hop is at et-0-0-2-br02-eqam3.as57976.net where my packetloss ranged between four tests 21%-80%. It’s always after a timeout hop.
There is a bit of ms jitter on battle.net’s first IP connection from an England based one, but no packetloss seen across all the tests.
195.66.238.234 - 0 | 604 | 604 | 4 | 7 | 76 | 4 | (last England registered IP)
137.221.79.33 - 0 | 604 | 604 | 11 | 126 | 430 | 181 |
Request timed out. - 100 | 122 | 0 | 0 | 0 | 0 | 0 |
137.221.65.77 - 27 | 246 | 181 | 0 | 1219 | 4933 | 2419 | ( et-0-0-2-br02-eqam3.as57976.net)
137.221.78.69 - 1 | 601 | 600 | 9 | 10 | 29 | 10 |
137.221.66.47 - 1 | 597 | 595 | 10 | 10 | 11 | 10 |
185.60.112.157 - 1 | 593 | 590 | 10 | 10 | 25 | 10 |
I have a feeling that this is where the problem lies for us in England. Curiously, it seems like Ireland have a completely different route.
Thanks Sellblade for the MTR recommendation, I wish you luck with your own networking issues! It has put my mind at ease that this is something on their end as resolving up until that point for me has been clean.
Same thing it shows for me. For me I don’t even see packet loss before it hits Blizzard, at all. And just to be entirely clear: I’m not disconnecting. I had high World Latency from December to April (and by high, I mean HIGH) and now it’s kind of just… slightly more ping than usual, with the World Latency or both occassionaly spiking to above 100 for some time, seemingly at random.
So this is definitely not fool proof evidence. Blizzard also said when this sort of stuff happened in 2020, that generally you CAN and WILL see packet loss on Blizzard Node(s), because of certain packet types being sent that are commonly used in DDoS Attacks, actively getting throttled, but none of that stuff is any relevant Game Data, so even if you see packet loss, their statement on it used to be “That’s normal”. The Jitter is what I feel like is worse and gods above am I seeing it a lot on my end as well, that especially the Blizzard network nodes just spike into the multitude of 1000’s randomly, for no apparent reason. Could be during busy hours, could be in the dead of night at 4 AM.
Last time (As in December and onwards, where some italian players were affected it was an issue with their Backbone that they were apparently super slow in responding to. And not everybody or a vast majority was having problems, despite the problem being on their end.
But yes. Even though you may not get a direct answer, the rule of thumb is that Blizzard at the very least is LOOKING at these Posts. So in any case don’t take silence as an invitation to think nothing will be done. Anything you can think of, anything I’ve posted, even if our issues are completely different, show them. Open Tickets. Even automated response tickets generally tend to reach somebody if the problem is widespread enough. Common Blizzard Troubleshoots, just do them and list them and clearly say that they did not work, if they did not work. Don’t get triggered by the automated responses. It might feel like silent treatment, but alas, it seems like they are just not prone to actually showing and telling that they are aware of a problem or don’t see a problem.
Keep the Thread alive and don’t let it autoclose, if y’all are still having issues.
Same problem. I get on wow, after 1-2 minutes I get DC’d. Thanks a lot for these days we get to play for free 2 minutes at a time. Jesus.
ISP: Telenor
Location: Stockholm, SE
I disabled “Optimize Network For Speed” in Options → Network and this seems to have fixed it for me.
Edit: It still happened one time after a few hours of play.
1 Like
Edit: Seems my problem was because of addons. I disabled out of date addons and no longer have issues. I’m not sure we had the same problem to begin with, mine was that after about 1 minute quite precise I DC’d. Never managed to stay connected for more than a minute or two.
Edit again: I think it might be bagnon.
I too am having this problem since the Pre patch. Its super random.
There are days where I log in and keep getting DC every 5 seconds. No connection problem on my end. Only happens with WoW
And there are days where nothing happens but the Constant DC or the Random streak of DC is getting on my nerves.
I just log in, 5 seconds later DC Error wow51900319
WHERE ARE THE BLUES IN HERE
1 Like
It’s started happening through my VPN as well so it’s been pretty much unplayable. Can’t play Diablo 4 either right now because of it - so it’s not strictly WoW.
I’ve been eyeing Battle.net’s client message about Friday having some b.net maintenance in the morning, so fingers crossed this may address this!
Edit as of 10/08/24: still not fixed. I have also gone through other troubleshooting steps like flushing DNS, renewing IP and also scannow on the machine etc etc.
1 Like
I just wanted to give an update to my own situation.
As of 14/08/24, when there were some server troubles reported by many, Blizz eventually came up with fixes and servers were back. After that tweet, It appears my troubles have also disappeared and I get stay on fully!
My pingplotter and MRT are still showing high ms on the first hop to Blizz-side servers and I remain optimistically cautious. But so far I’ve been able to stay logged in on bnet, D4 and WoW.
Now, I do want to add, because it would be disingenous not to disclose this: The same day (around the same time), on a whim, I uninstalled my VPN app (Surfshark). I only started using it when the troubles began to circumvent the disconnects, but I stopped bothering when it was prevelant no matter where I tunneled from, so it was not active. I can not say with 100% confidence that it was Blizz, or my uninstalling actions that has fixed the issue, but I just want to put it out there just in case.
Many thanks to Blizz for what feels like fixing this issue, if at least as a bonus, by fixing the log-in and server issues, if that was what did it for me (which I think so because my laptop that still has the VPN app is also working flawlessly).
Well today I think I got this bug. Played my daily and Internet dropped randomly, when WoW was open. Overall Internet did not drop.
So far that worked for me was disabling all Addons.
I’m still having this issue. Sometimes once per session, sometimes multiple times per in a row every 2 minutes.
2 Likes
Exactly the same problem for me today. Unable to play. Loop disconnection after a few seconds. It’s like my connection is going “ddos”. This impacts my entire connection even outside of WoW.
ISP : Red By Sfr
Country : France
1 Like
As of September 7th I’m still experiencing this bug across WoW and Diablo 4. Any help would be great.