I’ve been experiencing frequent, ongoing disconnects from World of Warcraft since 7/21/2026. This is happening repeatedly throughout play sessions, not tied to any specific zone, instance, or action.
I’ve already ruled out common local causes:
Scan & Repair via Battle.net: completed, no files repaired/no corruption found
All addons are up to date
Internet speed test: 836 Mbps down / 923 Mbps up, 8ms latency (connection confirmed stable and more than sufficient)
Ran tracert and pathping to a Blizzard NA IP (24.105.29.30) during an active disconnect
Pathping results during the disconnect showed a clean path with 0% real packet loss at every responding hop. Two hops showed 100% loss, but both were immediately followed by 0%-loss hops downstream, which indicates those nodes are simply not responding to ICMP/ping probes rather than actually dropping traffic. The trace could not reach the final destination IP, which is expected if ICMP is blocked at your end.
Given that my local hardware, addons, and network have all tested clean, this appears to be an issue on Blizzard’s end rather than mine. Could you please investigate on your side? Happy to provide additional logs (WoW.log, network trace) if needed.
Thanks for your help.
Character: Zeezuu
Realm: Mal’Ganis
Region: Americas
Date/Time of most recent disconnect: 7/22/26 @ 915am ET.
I’m experiencing the same issue. All of my guildmates and friends in the game are suffering from severe lag. On top of that, because of the constant disconnects (DCs), my account was rolled back, and I lost a lot of macros, settings, and other changes I had made.
It’s impossible to play like this, especially when we’re paying for the game. Blizzard needs to take action and provide the level of service we’re paying for.
Yeah Same here, It wasn’t so bad for me last night but right now its constiant DC or lag and all I’m doing is messing around with housing. With multiple reports on here as well as the Gen forums you would think after almost 24 hours it would have been fixed by now!
They’re probably just getting to work lol I live on east coast and not able to stay logged in I connected my VPN to Illinois server and was able to stay logged in with low ms.
True - but it did start last night at like 7pm PT. So - just a ‘We noticed instability - we are working on it’ is all we need. Not a PR post - lol - shouldn’t be hard to do that even outside of core hours
I don’t really understand the nuance behind the internet, so I’m just parroting what I’ve seen people who do say:
It seems like this issue is not related to Blizzard, rather a common routing point that a lot of the major ISP’s in the South East share that connects us to the data centers where the game is actually being hosted. Blizzard can’t fix that routing issue, as it’s not on their side.
It sounds like the reason behind this assumption is due to the fact that Mobile Hotspot/using VPN’s to different areas is fixing the issue.
I don’t think it’s server side. It’s a traffic issue. It sounds like the internet has an interstate and there is a massive traffic jam. I think we are all sitting in the same traffic?
It started with a few disconnects as soon as I was in the game and now it’s disconnecting before it even loads. I guess I’m off to do something else until the issue is fixed!
Having the same issues as described by others, and would make sense that it’s more an issue with the ISP than Blizzard itself since a lot of LATAM players are also having the same problems (since we connect to mostly the Los Angeles servers).
Those nodes are designed to ignore most of the data from the test you’re running to it, so you can’t use it for troubleshooting. Sometimes it will show a normal ping and other times it will show 5k+.
Yeah, the confusion in this thread starts with the title of the post not matching the description in the original post. Crashing and disconnecting are completely different things.
If you are disconnecting, you’d need to seek external assistance for that because Blizzard doesn’t handle any connection concerns anymore.
And if your actual game client is crashing, as in freezing or closing, you need to start a new thread with your DxDiag.
Yea - it likely is a server side problem - who owns there servers? AWS? Get your pitchforks!
