I figured out the problem, for me anyway. I had to uninstall add-ons. turns out files were corrupted. I just uninstalled and reinstalled and I have not disconnected once in the past few days. I was using DBM, details and plater. I am pretty sure plater was the issue and I did not reinstall it. I would reset UI as well after uninstalling add-ons.
3 Likes
Same boat here. I have tried every single thing, and nothing has worked. Had no issues until a few days ago, now I cannot stay logged in longer than 2-3 minutes before I get kicked out. I have tried all remedies, uninstalled, re-installed, DNS flushes, network refresh, no add ons, deleted WTF folders, updated everything that could be updated, you name it. No word from Blizz on a fix 
2 Likes
I’ve been having the same issue. Been trying to play all day but this happens every time.
3 Likes
Same sort of issues. My disconnects tend to happen from mounts but have randomly occurred in other ways. I’ve been going back and doing Agent Tournament quests from WOTLK and I get DC’d all the time when hopping onto a jousting mount. Landing on the ground from flying causes them as well. This has been occurring for me since I began playing TWW
3 Likes
Same issue here. I don’t think it’s us. Most here are running Windows I assume, but I’m on macOS and having the exact same symptoms. I’ve jumped through all the usual troubleshooting hoops as well. This appears to be on Blizzard’s end, not ours. Quite frustrating.
3 Likes
I think im going to have a mental breakdown. Nothing is worse than doing arenas or just simply standing in one spots and getting booted off. Same error code has what was stated. Can some devs please tell us what they think its really going on. I have 1gbs download 30ms latency and never had a issue for 16 years. I spent my own gold in game to play and this is what i get. Atleast refund me my gold or something. We are all sick of this and seems like bliz dosent care. Or they just say its our fault.
1 Like
[quote=“Orby-angerforge, post:46, topic:1937426, full:true”]
I think im going to have a mental breakdown. Nothing is worse than doing arenas or just simply standing in one spots and getting booted off. Same error code has what was stated. Can some devs please tell us what they think its really going on. I have 1gbs download 30ms latency and never had a issue for 16 years. I spent my own gold in game to play and this is what i get. Atleast refund me my gold or something. We are all sick of this and seems like bliz dosent care. Or they just say its our fault. Had to post a second time in so angry
also experiencing same kind of issues, tried some solutions posted and nothing helps. symptomatically, seems like client side problem that briefly crashes LAN interface. only wow / battle.net does this to my machine. “could be” some driver issue so will keep trying things, but if 1 and only 1 application is associated with constant crashes… well, hard to say that sounds like something i should continue to pay for.
My spouse is having this same problem. Her computer sits right next to mine in our office. She has a similar set up (2 monitors vs my 1) and her WoW just constantly disconnects randomly - it’s inconsistent and happens more at some times vs others.
I have not had this problem. So initially I thought it was addons. Completely wiped those out - no effect. Thought maybe it was graphics issues? Changed those completely - no effect.
Again her computer has no problems doing anything else - just with WoW and despite us being on the same ISP, very similar hardware, I have no issues.
We’ll try the IPV6 thing… but this definitely seems like it’s WoW’s side… considering both of us have been playing WoW since 2007 and haven’t had issues like this before.
On gigabit fiber, been playing for years with this hardware - no previous issues, nothing changed.
Good luck to WoW devs to figure this out - will report back if IPV6 helps.
IPV6 did not help. lol.
Noticed this issue after the recent WoW Anniversary patch. Not just with me but numerous other people in my raid as well. Never really had issues with radom DCs before but now when i pull a boss in the NP raid I feel like its a 50/50 chance someone will DC during the fight. It is exceptionally painful when this happen in a small group for Heroic Queen Ansurek. Did 12 pulls last night had half of them were scuffed due to people getting the DC bug… I dont want to pull a boss and pray for people not to DC… Sucks the fun out of the game.
4 Likes
It’s really odd, I was having this problem incessantly before the 11.0.5 patch numerous times a day. Since then I have NOT DC’ed once. I was hoping to find it settled the matter for everyone. I’m more confused now about what could be causing it for you than before.
to me it’s feels like it’s almost certainly a DB sharding issue, some of the users connected to some subset of DBs the game server stops communicating and lags. Sometimes recovering, but now more than ever forcing a game client disconnect.
I submitted two support tickets and just got told: “go check forums lol”.
From what I can tell it’s packetloss on WoWs server end to ISP, but they refused to acknowledge the data I attached to my ticket, so shrug WoW is bricked until they fix it which they won’t
had this issue before, here is the fix I use,:
also I needed to make sure ,my DX11 is enabled in launching wow, ‘-d3d11’
Still no response from Blizzard in these issues:
Looking at old troubleshooting posts.
- Find Blizzard servers connected too
- netstat -an | find /i “3724”
TCP 192.168.0.203:60067 64.224.30.144:3724 ESTABLISHED
TCP 192.168.0.203:60105 64.224.28.245:3724 ESTABLISHED - Run tracert
"tracert 64.224.30.245
Tracing route to 64.224.30.245 over a maximum of 30 hops
1 2 ms 1 ms 1 ms Docsis-Gateway.hsd1.ut.comcast.net [192.168.0.1]
2 11 ms 9 ms 8 ms 100.93.169.3
3 * * * Request timed out.
4 7 ms 21 ms 5 ms po-324-351-rur401.saltlakecity.ut.utah.comcast.net [69.139.230.73]
5 5 ms 12 ms 13 ms po-400-xar01.saltlakecity.ut.utah.comcast.net [162.151.49.161]
6 13 ms 12 ms 9 ms po-2-xar02.saltlakecity.ut.utah.comcast.net [162.151.39.214]
7 15 ms 14 ms 13 ms be-306-arsc1.sandy.ut.utah.comcast.net [24.124.175.21]
8 14 ms 8 ms 25 ms be-501-ar01.sandy.ut.utah.comcast.net [24.124.175.226]
9 31 ms 29 ms 35 ms be-36721-cs02.sunnyvale.ca.ibone.comcast.net [96.110.41.85]
10 29 ms 34 ms 32 ms be-2212-pe12.9greatoaks.ca.ibone.comcast.net [96.110.33.38]
11 * * * Request timed out.
12 42 ms 34 ms 40 ms ae1-br02-eqsv5.as57976.net [137.221.70.35]
13 41 ms 34 ms 40 ms et-0-0-4-br02-eqla1.as57976.net [137.221.65.6]
14 122 ms 180 ms 215 ms et-0-0-29-br01-eqla1.as57976.net [137.221.65.0]
15 * * * Request timed out.
16 43 ms 37 ms 35 ms et-0-0-0-pe04-swlv10.as57976.net [137.221.83.87]
17 37 ms 45 ms 43 ms las-swlv10-ia-bons-04.as57976.net [137.221.66.23]
18 * * * Request timed out.
19 * * * Request timed out.
20 45 ms 44 ms 44 ms 5.42.178.1
21 47 ms 50 ms 40 ms 64.224.30.245
Trace complete."
"tracert 64.224.30.144
Tracing route to 64.224.30.144 over a maximum of 30 hops
1 3 ms 2 ms 1 ms Docsis-Gateway.hsd1.ut.comcast.net [192.168.0.1]
2 14 ms 11 ms 12 ms 100.93.169.2
3 15 ms 10 ms 13 ms po-324-351-rur401.saltlakecity.ut.utah.comcast.net [69.139.230.73]
4 9 ms 13 ms 12 ms po-400-xar01.saltlakecity.ut.utah.comcast.net [162.151.49.161]
5 15 ms 13 ms 12 ms po-2-xar02.saltlakecity.ut.utah.comcast.net [162.151.39.214]
6 14 ms 10 ms 17 ms be-306-arsc1.sandy.ut.utah.comcast.net [24.124.175.21]
7 14 ms 8 ms 9 ms be-501-ar01.sandy.ut.utah.comcast.net [24.124.175.226]
8 28 ms 22 ms 23 ms be-36711-cs01.sunnyvale.ca.ibone.comcast.net [96.110.41.81]
9 35 ms 23 ms 30 ms be-2212-pe12.9greatoaks.ca.ibone.comcast.net [96.110.33.38]
10 * * * Request timed out.
11 40 ms 43 ms 40 ms ae1-br02-eqsv5.as57976.net [137.221.70.35]
12 55 ms 37 ms 41 ms et-0-0-4-br02-eqla1.as57976.net [137.221.65.6]
13 375 ms 442 ms 436 ms et-0-0-29-br01-eqla1.as57976.net [137.221.65.0]
14 * * * Request timed out.
15 50 ms 46 ms 53 ms et-0-0-0-pe04-swlv10.as57976.net [137.221.83.87]
16 43 ms 54 ms 53 ms las-swlv10-ia-bons-04.as57976.net [137.221.66.23]
17 * * * Request timed out.
18 * * * Request timed out.
19 39 ms 38 ms 36 ms 5.42.178.1
20 50 ms 45 ms 47 ms 64.224.30.144"
Trace complete.
Note that everything is fine till the 137.221.x.x 's owned by Blizzard . . .
The forums are player-to-player troubleshooting areas these days. The blues who used to post in here have been gone for some time.
Those are no longer the active IPs and should not be used for running tests.
what are you saying, those are literally the IPs my game client is connecting to when I run the netstat command. Are there new ports being used since TWW?
It sounded like you were using IPs from the old posts. That said, you’re probably looking at an authentication IP and not the actual game server.
Same here and I thought it might be my ISP, so I am glad to see others with this problem.
1 Like