After following the guides on Blizzard’s support website, the problem still persists. I restarted my computer, renamed the wow folders, and disabled outdated addons. Nothing. I ran a traceroute again same issues. I am not good with computers and would post it but for some reason the website here says I can’t post links. I got request timed out and high latency at the end coding lines or whatever format cmd is run in.
Try a full reset first. There should be no addons, outdated or not once you complete this.
This is only a diagnostic tool, not a fix-it. Ran during when lag is the worse can point out where in your connection dropped packets occur. Usually anything in Blizzard’s network is monitored by them.
When is the lag occuring. Are you doing instances/queued pvp. You could be on one server, but for group content depending on time of day, could be connecting to a different one.
Where are you connecting from? What kind of internet?
80-200 is in my opinion not unusual. 400 might not be either depending on where you live, and what servers your connecting to. Not ideal obviously.
There may be a lot of distance, and routers, between where you live and Blizzard’s servers.
You can post your trace is you code block it, try:
Ok blizzard, its time to stop saying that is our problem. There is a lot of people with the same issue.
1 9 ms 5 ms 2 ms 10.0.0.1
2 14 ms 15 ms 11 ms 96.120.62.217
3 23 ms 13 ms 21 ms po-302-1209-rur101.bethelpark.pa.pitt.comcast.net [96.110.214.157]
4 14 ms 16 ms 15 ms po-2-rur102.bethelpark.pa.pitt.comcast.net [96.110.2.170]
5 13 ms 12 ms 12 ms po-100-xar02.bethelpark.pa.pitt.comcast.net [96.110.49.193]
6 18 ms 14 ms 13 ms be-53-ar01.mckeesport.pa.pitt.comcast.net [96.216.140.105]
7 15 ms 15 ms * be-31611-cs01.pittsburgh.pa.ibone.comcast.net [96.110.42.161]
8 23 ms 23 ms 28 ms be-3411-pe11.ashburn.va.ibone.comcast.net [96.110.32.134]
9 52 ms 24 ms 22 ms 50.208.235.6
10 104 ms 89 ms 81 ms ae1-br01-eqdc2.as57976.net [137.221.72.33]
11 * * * Request timed out.
12 * * * Request timed out.
13 94 ms 82 ms 92 ms et-0-0-0-pe02-swlv10.as57976.net [137.221.83.83]
14 83 ms 90 ms 101 ms las-swlv10-ia-bons-02.as57976.net [137.221.66.19]
15 84 ms 82 ms 83 ms 137.221.105.2
I asked ChatGPT for its advice. Here is what it says:
The traceroute you’ve provided shows the path taken by packets from your computer to the destination IP address 137.221.105.2. There are a few points where latency increases significantly:
Hop 10 There’s a noticeable increase in latency here, with times of 104 ms, 89 ms, and 81 ms. This hop likely represents a significant physical distance or a congested network segment.
Hops 11 and 12: These hops show “Request timed out.” This could be due to the routers at these hops being configured to not respond to ICMP (ping) requests, or they are under heavy load and dropping ICMP packets. It does not necessarily indicate a problem with packet forwarding, but it does prevent us from seeing the latency at these points.
Hop 13 The latency here is slightly lower than hop 10 but still higher than the earlier hops, with times of 94 ms, 82 ms, and 92 ms. This indicates the latency persists or slightly improves after the previous high-latency hop.
Hop 14 The latency remains high here with times of 83 ms, 90 ms, and 101 ms.
Hop 15 The final destination shows latency consistent with the previous hops, with times of 84 ms, 82 ms, and 83 ms.
Possible causes of latency:
Physical distance: The increase in latency at hop 10 may be due to packets traveling a long physical distance, such as crossing continents or significant geographical regions.
Network congestion: High traffic levels at specific network nodes can cause delays, which might explain the increased latency at hop 10.
Routing policies: Certain ISPs and backbone networks may have specific routing policies that introduce additional hops or indirect paths, increasing latency.
Router performance: The routers at hops 10, 13, and 14 might be experiencing high load or be configured to prioritize other types of traffic over ICMP packets.
The test was run to the Las Vegas server. Are you playing on a server hosted in Las Vegas?
Other than that, the advice sounds correct to me. The connection to Chicago servers will have less latency than Las Vegas-based servers.
I am playing on whitemane, horde.
Whitemane is hosted in Las Vegas, so you’ll have a worse connection to it than a server hosted in Chicago. ChatGPT’s assessment was mostly correct, as there’s a huge gap between two nodes per the ISP’s routing table, which is adding extra latency. Nothing you can really do about that except complain about slow/laggy connection to the ISP.
This problem is fairly new though. I don’t remember having a problem when I first started playing classic wow on whitemine when classic first came out. For the most part, I don’t notice an issue, it’s with occasional latency spike where it will go to around 400ms and everything is freezing for a few seconds, I can’t have that happen in raids or dungeons.
Hey man. Like a said i have the same issue.
If the problem is between our home and the server, we are f***.
What we can do about it?
You can try a VPN until the ISP repairs it. But you want to put it on their radar, too.
50.208.235.6 is registered to Comcast in Arizona and likely located there. The jump between that node and the Blizzard peer is where all the latency is happening. They probably need another node between to handle traffic.
1 Like
Thank you so much for the help. Blizzard’s GMs are useless. They could have easily told me this, instead of giving me the link to the support article and then saying ask the forums. Why even have GM’s? They should be paying you green text guys, or giving you free game time.
I have been playing on Whitemane for over two years and never had any real consistent issues with lag/latency but the past two weeks the game is borderline unplayable during primetime hours. Odd that all these people’s ISPs are having independent issues at the same time…
I did this test last night.
While in whitemane i had 1k ms i switch to oceania server. I played around 30 min without a single issue, without a single freeze. Swithc back to whitemane and instant 1k ms,
The problem is NA. Its the server or its the last trip of connection.
Its not our ISP or our windows…
The Las Vegas server isn’t having issues though. NA players can connect and use it without issue; I’m one of them.
1 Like
So I was able to confirm that is my ISP, or at least the 3rd party network they use to route traffic. I posted in my ISP’s customer forums, and got this response from an employee:
“Hey [@user_758ozz] Thank you for visiting our official Xfinity Forums Community support page. We greatly appreciate you taking the time to share your experience regarding your game. Reviewing the data, I am not showing this is something we can assist with. I am showing your data not being routed by us but other third-party network connections. I would recommend reaching out to your games support team and see if they have any tips and tricks to help further.
I am an Official Xfinity Employee.”
Blizzard can’t help at all? Lucilky the lag spikes are less and less, but I am worried that if I raid or do dunegons that the game will freeze. 5 seconds is enough for a wipe.
As far as I’m aware, the extent of connection troubleshooting they offer is on the support documentation: https://us.battle.net/support/en/article/99037
Since the note at the bottom suggests heading to external sources for connection issues beyond the steps, someone answering the ticket may only be able to refer you to those steps again.
So what can I do. The ISP says talk to Blizzard, Blizzard says talk to the ISP. My ISP sent a tech to my house. Should I try contacting Equinix? I am not a customer of theirs, would they still be able to help?
Personally, I would keep contacting the ISP since it’s their job to connect you in an optimal way to services you want to use (game server). Equinix is unlikely to entertain any requests from an ISP’s enduser.
Keep in mind that some of your route to Las Vegas may include parts of Texas’ infrastructure, a lot of which is flooded/damaged due to Hurricane Beryl.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.