It appears that I’m now getting a fairly poor connection to WoW and the culprit appears to be an IP address owned by Blizzard. I use XFinity by Comcast and haven’t had this problem before tonight. The client keeps kicking me out with error " [WOW51900319]".
Upon running a WinMTR it appears that I’m getting the following ping experience:
(Please note that I attempted to add my WinMTR clip, but was told by your forums that I could not include “links”… let me know how you’d like me to continue).
I would like to know what additional information you require to troubleshoot this new glitch. Thank you.
This was not run during the disconnect, no. It was started shortly thereafter. you’ll see that hop 10, 11, and 12 give all manner of packet loss. The one which causes the most trouble is 137.221.83.69 – I’d love to know if there is a problem with the routers receiving traffic right before they arrive at 137.221.105.2
The packet loss on those hops is most likely not actually packet loss. There is no packet loss on the hop after those two. It generally just indicates a very busy node.
What we will want to do is run winMTR in 10 minute segments until you get a DC
OK… I will keep it up and running moving forward. Clearly, the local client believes it to be packet loss (hence the “WOW51900319” error and the disconnect). Can you please review those nodes and see if they can be optimized? It has been ugly for the last 12 hours. Current latency = 4974 with node 137.221.65.69
You’ll see that my WinMTR shows a clean connection from my local ISP into the primary trunk and then chokes when it hits your node.
Same with me. These same nodes show high ms and packet loss. I submitted my winmtr and they said they were not nodes but peering?? I don’t care if it is peering or a node, it is own by blizzard and shows high ms and in my case 10-15% packet loss which causes my connection to lag, 1-2 second spell casts, 1-2 seconds mounting etc.
The latency spikes on your modem/router are concerning. We normally expect to see the worst on that be no higher than 10, and the average to be about 1-2. You’re is higher than that on both reports.
Those hop switches are normal. That is what they often show. Likely security or DDOS mitigation. The ping packets you send are very low priority and the switch is simply ignoring them. As they say that is a “Red Herring” - you need to look elsewhere for the issue.
It looks like you are on a wireless connection. If so I would first try a Ethernet cable. Here is the support page for disconnects - work through things. Open the Advanced Troubleshooting section as well.
The latency spikes on MY hardware? I will powercycle my modem to see if that fixes the issue (I’ve powercycled 2x in the last 24 hours). The fact that your nodes are having 10x the latency should be more concerning, sir.
You’ve got multiple customers telling you that you’ve got issues with nodes/hardware that you own… yet you’re focusing on my spikes which are significantly less frequent or problematic. As I write this, your node is spiking at 5800ms.
Let’s just be honest about where the issues lie. I work in IT and this is simply deflection. Moreover, I’m on a hard line connection. A speed test I just took (while posting this) shows a 9ms connection to a local trunk, download speed of 448Mbps and an upload of 42Mbps. While typing this, your node failed again and booted me out of the game. Error [WOW51900319]
Here is my WinMTR. As you can see I have wonky readings on both the same hop switches. I haven’t disconnected in recent memory and my latency is always around 50ms.
MVPs (green text) do not work for Blizzard, they are simply knowledgeable players like yourself that volunteer to assist others on the forums.
The latency spikes on the as57967.net nodes are perfectly normal, as Tratt explained here. Some of these core routers into the Blizzard network are configured to either drop or de-prioritize ICMP traffic when under heavy load. You can see in Tratt’s test the latency is also spiking there, but he is not having disconnection issues.
As you may be familiar with since you work in IT, there are many different types of packets traversing the internet. The WinMTR test uses ICMP packets to test the connection and report latencies back to the tool, while World of Warcraft uses TCP packets to transmit your game data back and forth from client to server. So those ICMP packets being delayed or dropped at those specific routers does not mean your in-game TCP packets are experiencing the same fate. The game traffic is getting through those routers just fine.
The core cause of the disconnections lie somewhere else.
What other troubleshooting have you attempted from our World of Warcraft Disconnection Problems article? Disconnections can be caused by a lot of different things (I’ve seen cases of keyboards causing disconnects) so hopefully with a bit more information we can get to the bottom of this for you.
The WOW51900319 error seems commonplace with many users experiencing this problem within the last three days. I went through the step by step guide. I ran the repair tool, I did a fresh install of wow, I do not use any addons, I checked my computers drivers, and I reset my router. I cannot see my character list as it will not log into the game server. Is this something that will be addressed in tomorrows maintenance?
![:slight_smile:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/slight_smile.png?v=6" ":slight_smile:")