It won’t let me post WinMTR or Tracert test results. It says I’m not allowed to post links.
Same happened to me, I just put a space before the .net or .com
I am having this issue. Been having it since I resubbed a few days ago. I know for a fact it is not on my end. I’ve run tests repeatedly for long and short periods of time. While doing these tests, I noticed a particular node along the route dropping packets whenever WoW would start to lag.
eqch2.as57976 net
This has happened in the past. There’s an old backbone network that causes issues with games and services, WoW being one of them. This is the THIRD time I’ve seen this happen in 15 years. Every single time WoW starts lagging, MTR and traceroute tests on windows all show that one node to stop responding and then drop packets. Every time without fail. It’s that node.
Blizzard has a hard time dealing with this because it’s not their node. You’ll also noticed (especially east to west, or west to east) while in dungeons or raids, your latency slowly climbs to 300+.
1 Like
Here you are Tratt, WinMTR and traceroute from the PC with a direct wired connection to the modem on which this problem does happen.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.0.1
2 13 ms 9 ms 18 ms 68.149.96.1
3 18 ms 22 ms 15 ms rc3ar-tge0-13-0-1-1.ed.shawcable .net [64.59.185.41]
4 12 ms 12 ms 16 ms 66.163.70.129
5 55 ms 35 ms 100 ms rc3no-be6.cg.shawcable .net [66.163.64.69]
6 32 ms 34 ms 38 ms rc2wt-be100.wa.shawcable .net [66.163.75.233]
7 31 ms 35 ms 32 ms rc6wt-tge0-10-0-11.wa.shawcable .net [66.163.68.70]
8 77 ms 73 ms 76 ms ae1-br01-eqse2.as57976 .net [137.221.73.33]
9 72 ms 73 ms 78 ms xe-0-0-1-1-br02-eqch2.as57976 .net [137.221.65.42]
10 72 ms 79 ms 79 ms be2-pe02-eqch2.as57976 .net [137.221.69.73]
11 75 ms 75 ms 73 ms 24.105.62.129Trace complete.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % Sent Recv Best Avrg Wrst Last 192.168.0.1 - 0 283 283 0 3 119 1 68.149.96.1 - 0 283 283 8 27 577 16 rc3ar-tge0-13-0-1-1.ed.shawcable .net - 0 283 283 10 22 137 14 66.163.70.129 - 0 283 283 11 24 165 20 rc3no-be6.cg.shawcable .net - 0 283 283 14 25 139 21 rc2wt-be100.wa.shawcable .net - 0 283 283 29 43 192 31 rc6wt-tge0-10-0-11.wa.shawcable .net - 0 283 283 29 43 192 31 ae1-br01-eqse2.as57976 .net - 0 283 283 71 85 214 78 xe-0-0-1-1-br02-eqch2.as57976 .net - 0 283 283 71 87 209 78 be2-pe02-eqch2.as57976 .net - 0 283 283 71 84 214 75 24.105.62.129 - 0 283 283 71 85 214 81 ________________________________________________ ______ ______ ______ ______ ______ ______ WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
We still see these high latency spikes on the home network while on Ethernet.
| 192.168.0.1 - 0 | 283 | 283 | 0 | 3 | 119 | 1 |
|---|---|---|---|---|---|---|
| 68.149.96.1 - 0 | 283 | 283 | 8 | 27 | 577 | 16 |
For comparison here is my home network on Telus ADSL.
WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.1.254 - 0 | 78 | 78 | 0 | 0 | 1 | 0 |
| 10.139.226.1 - 0 | 78 | 78 | 4 | 7 | 20 | 4 |
Is that a separate router then modem or a Shaw - router/modem combination device? If they are separate try the Ethernet cable directly into the modem - bypass the router.
It’s a modem/router combo that the PC is plugged directly in to.
I would still be interested in hearing how a local spike or two would produce effects such as your mount not showing up and instead ‘flying’ through the air or running super-fast, old school Tauren style, hitting the resurrect button but staying in the land of the dead but still being able to be attacked by PvP players and aggressive NPCs, not generating ability power, etc… Generally speaking a network lag issue would mean me being not being able to use abilities at all and everyone else running in place.
WinMTRs and Tracerts are basic tests which indicate a problem. There could be a lot more going on with the signal that we can’t see with the tests we have. Basically it appears you have an issue on the home network how it manifests itself is likely what you see in game. I would give Shaw a call here.
If you want a second opinion I would open a ticket:
https://us.battle.net/support/en/help/product/wow/197/1462/channels
I would also work through the possible solutions found on this support page:
(expand the Advanced Troubleshooting section as well)
Since I have no issues playing other games such as FFXIV, watching Netflix or streaming from my own Plex server I’m going to go ahead and say that the problem lays on the Blizzard side, especially since they’ve already admitted it in Blue posts, one of which directly cited Ion stating they’re aware of the issue and are working to resolve it. Many, many people have been having these exact same issues and all of it started when BfA came in to the picture. I appreciate you’re trying to help but I’m pretty darn sure you’re barking down the wrong alley. I’m not going to bother Shaw with this because I’m pretty darn sure swapping out the modem would only result in my having to change all of my log on passwords for my wifi devices.
3 Likes
5 25 ms 23 ms 23 ms ge-5-1-0.rlghncpop-rtr1.southeast.rr com [24.93.64.26]
6 31 ms 38 ms 38 ms gig9-0-0.clmascmhe-rtr2.sc.rr com [24.93.64.43]
7 36 ms 38 ms 38 ms bu-ether11.atlngamq46w-bcr00.tbone.rr com [66.109.6.34]
8 37 ms 38 ms 38 ms bu-ether12.asbnva1611w-bcr00.tbone.rr com [66.109.6.33]
9 465 ms 24 ms 19 ms 66.109.9.107
10 99 ms 75 ms 72 ms ae1-br01-eqat2.as57976 net [137.221.75.33]
Was this thread really unstickied? The problem still persists and is worse than it’s been in 2 months due to people logging in for 8.1.5. It is NOT fixed, Blizzard!
4 Likes
It had pretty much disappeared for me at some point this year. Now that patch 8.1.5 has gone live, however, I’ve been seeing a frequent, though modest, delay between when I give a command and my character executes it.
WinMTR is showing the same thing it has since I switched ISPs a while back: a distinct lack of dropped packets along with average latency of single digit to teens ms range until the last few hops where it is in the 30-40 ms range. In game it shows latency in the 50-60 ms range for both home and world, but there is now a slight delay.
Seeing the issue again more severely on Turalyon in areas that tend to be heavily populated (Boralus, the incursion zone, and most of Zandalar due to Horde population advantage). Far worse than before today’s restarts/maintenance.
Bump for hope springing eternal
This has been happening to me on Eonar quite a lot recently. It’s really really annoying.
It happens to me on all of my characters on Eonar(I mostly play as Leafanna and Willtaru) and sometimes my characters on Nazjatar (although not as much).
It happens at various times throughout the day.
The zone i’m in doesn’t seem to matter.
My ping is usually steady at about 60-70 ms but clicking on quest items, using abilities, and mounting all sometimes have a 1-2 sec delay.
Its been really bad these past few hours from about 5pm - 11:30pm EDT
I will probably get lash back for this but oh well and I am NOT claiming this Is the Issue just some thing I tested…
I’ve been having latency/DC Issues since the start of BfA (In Legion I was fine)
But because of this I was testing stuff and I have kind of replicated this “Lag” or some thing similar on my hunter, I would have 30-50 latency play JUST fine
But then I would join a group on purpose for a boss and while It’s trying to phase me I would use disengage and sure enough that sort of “Lag” would hit I could move, I could talk but my abilities were not going off , It would FINALLY go off once I fully zoned Into the shard I was zoning Into I tested this 2-3 times able to do It every time
Join a server, It starts to phase I use an instant cast like Disengage and It would NOT go off until I was fully phased the Icon would light up and stay lit up until I fully phased Into the new shard then It would go off.
So maybe It’s a possibility of “Shards” fighting over players? And that’s why It doesn’t affect every one, Only those unlucky enough to get assaulted by these vicious shards.
The thing I don’t get though, Is I do get that lag any where , In Bg’s,Dungeons,Out In the world etc, I can’t figure out how the shards would fight over you while you were In an Instanced area (If this were to be the Issue)…
It may be Coincidence maybe others can test It.
Here is the most updated response. There is no solution.
2 Likes
Friendly bump since Blizz is closing all new reports over the last week and referring them here. This issue has been consistent for some time now with no new updates from Blizz in this thread.
Could we please get some sort of update on what is being done? The game is pretty intolerable in the affected zones.
This issue has not been resolved. Not only do I experience lag all the time, it gets worse when I am in a more populated zone, no matter the server. I have also been booted out of the game completely and dc’ed rather suddenly. I have horrible lag when I am entering an instance, so bad that I frequently get kicked from group. This is every level character I have, and in all zones.
World Quests and rare fighting in game are impossible. I am lucky to get one hit on a boss and maybe if I am super lucky, I get credit.
I know my laptop is a few years old, and I am having a new pc built, but if this issue is not fixed I will have to quit WOW and go to another game. Very sad about this, as I love WOW and the people who play it that are my friends. But they have also expressed concerns over these lag issues and a lot of them have left the game because of it.
1 Like
At what point is this going to be resolved and fixed? I’m on the Uldaman server which was forefully connected to Ravencrest. I’d like to level my 111 Alliance toon, however, being anywhere near or in the zone of Boralas makes the game play just god awful. I leave that zone and it is fine. So no, it’s not my computer or my internet or my electricity or my water. These are the things that are driving the player base away. I would hope this would be something that would be addressed quickly.
1 Like