Used to get disconnected all the time on my old pc. Just got a new pc, was good for a month then started getting disconnected today.
Anyone else experiencing the same problem? -_-
There’s some other recent posts that popped up recently about spectrum users experiencing issues in connection right now.
I’m with Shaw internet in Canada
There was a few others that mentioned Shaw in a few of the posts and on twitter. It might be related.
Oh okay ty :), hoping they’re doing something about this issue.
Hey, Glaivepower! The Spectrum issue should be fixed now, including the chicago node where the problem was mostly occuring. We’re not sure if this would have impacted other ISPs, but are you still experiencing disconnections? If so, could you gather a WinMTR file until the problem occurs for 10 to 15 minutes? Copy and paste the text file created and paste it between two ~~~ like so:
~~~
WinMTR Here
~~~
If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)
Hello,
I’m still receiving disconnects with no lag issues. I’ve troubleshooted everything and even replaced the router incase the connection was not 100%. The only thing i can think of this being is the similar issue to Spectrum. I use Comcast and live near Chicago and saw another reply to a similar thread yesterday stating they had the same issue with Comcast.
This disconnect appears to be roughly every 30 mins give or take. I will attempt to gather a file of the disconnect when I find available time however am in middle of raid at the moment.
Does this help? Ran it a few times and doesnt always show the no response from host.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| EMG3425-Q10A.twlakes.net - 0 | 291 | 291 | 0 | 0 | 7 | 0 |
| host-192-199-190-1.twlakes.net - 0 | 291 | 291 | 1 | 3 | 29 | 2 |
| gnbo-edge-197.inet.twlakes.net - 0 | 291 | 291 | 1 | 2 | 6 | 3 |
| 204.29.12.237 - 29 | 136 | 97 | 0 | 16 | 103 | 99 |
| 7-1-4.bear1.StLouis1.Level3.net - 33 | 128 | 87 | 28 | 34 | 120 | 115 |
| No response from host - 100 | 58 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.ear7.Chicago2.Level3.net - 33 | 128 | 87 | 0 | 40 | 125 | 121 |
| ae1-br01-eqch2.as57976.net - 28 | 139 | 101 | 34 | 47 | 1031 | 1031 |
| be1-pe1-eqch2.as57976.net - 34 | 124 | 82 | 34 | 40 | 124 | 121 |
| 24.105.62.129 - 33 | 128 | 87 | 0 | 40 | 126 | 120 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
@Acheilos, there’s been a few comcast reports or ISP that peer with comcast that I’ve been seeing, but nothing consistent enough or with connection tests to determine an issue. Could you start a new thread with the WinMTR tests as well? I suspect that there’s configuration or throttling issues causing disconnections/latency for Comcast, but we definitely need more tests!
As for some suggestions, with the disconnections being consistent, there’s settings in the router that can cause mitigation and prioritize certain connection types or devices. Try checking for the QoS (Quality of Service), WMM (Wireless Multimedia), and UPnP (Universal Plug and Play) settings, if any of those are enabled, disable them. These settings can differ from device to device, so check the router manufacturer’s manual or with the ISP if the device was provided by them.
@Astorlord, thank you for the WinMTR test! There’s significant packet loss on this node here:
| 204.29.12.237 -
29 | 136 | 97 | 0 | 16 | 103 | 99 |
It is starting on this node, and after this point there’s around 30% loss on each of the nodes. It looks like it belongs to IRIS Networks, which could be the ISP’s peering partner or what they peer off to after their nodes. For this case, you’ll need to contact your ISP with the connection test calling out this specific node to see if they can reach out to IRIS Networks or reroute the connection. An alternative connection or VPN should workaround this issue in the mean time.
@Glaivepower, whenever you get the chance to the test will be super helpful to check 
We see other users are experiencing issues with disconnections or high latency after the case yesterday, but it’s best to start your own thread so that we can start gathering and troubleshooting these situations individually. It’s difficult to track multiple different regions and ISP issues on one thread. If we do find a trend, we can start a dedicated thread to these issues.
If anyone else is having similar disconnection or latency issues and not on Shaw Communications, please create your own thread.
I am having the same issue. Chat continues to work but I am receiving no updates and no other characters load and I can’t mount or cast spells. I am with Rogers in Canada
Happens yesterday in Oceanic realm.
This has been happening to me as of the last three days and I use Sparklight, which was once CableOne ISP.
I been getting these disconnect constantly for the last couple days too. The disconnect frequency is around 10 mins or so. My ISP is Spectrum, live east of LA.
Tried multiple method and didn’t work.
I’ve been getting high latency and disconnected for a few days now and I am on Centurylink ISP and I’ve done a ton of speedtest’s and they all come out great with no problems. I even did a line test through my ISP website and nothing is wrong. I ONLY have this problem with World of Warcraft. I don’t play any other blizzard games. I also live in Washington state USA.
Indeed, for me the only thing affected is just WoW. Everything else are just fine and that’s why I’m suspecting it has to do with Blizzard servers.
Hey all,
The original poster of this thread hasn’t posted in a couple weeks now. I’m locking this to prevent it from getting sidetracked by a bunch of unrelated issues. Please check other recent threads if you’re looking for a general ISP issue, but at this time we’re not aware of anything in our control that would be causing this.