anyone else have bad latency since the new patch?
10 Likes
I was just coming here to make sure I’m not crazy, seems like with each patch the latency issues and disconnects are getting worse and worse.
5 Likes
Me and pretty much everyone in my Brazilian guild are reporting lag that starts in the evening. The start of the season also had something going on, and there are several people using different internet providers, so it’s probably a routing issue on Blizzard’s side.
5 Likes
YES! Randomly sometimes too! Ping will show fine, but spells are delayed or “spongy” Today my latency is just terrible.
1 Like
I didn’t notice any issues before coming home from work today, but it’s noticeably bad atm.
2 Likes
Its happening for a few weeks by now. Always between 7pm and 11pm (BRT).
Tracert to 24.105.62.129 (according to wowpedia for BR servers) always show the connection reaching 500+ ms at “BLIZZARD-EN ear7 Chicago2 Level3 net [4.7.196.134]”, Everyone in my guild/friend list that has to go through this level3 route suffers the same problem at the exact same time.
This means 1500+ ms in game, which makes it unplayable during that time.
1 Like
That nodes rejects ICMP test traffic, so you can’t use the value you’re seeing in any ping or tracert tests for troubleshooting. If it was truly 500ms, you wouldn’t be able to login.
1 Like
Still seeing spiky home and world latency in the 250-450ms ranges since yesterday. Just hit 800ms (home) according to the ingame latency tracker thingy. Edit: Now home is fine and world is 500+.
Tried rebooting, vpn, disabling addons, resetting the router, etc.; no change.
Whew, I thought it was me. Reconnected my VPN like 5 times and it’s all the same.
Ping is fine in game (27 ms for home and world) but everything is incredibly laggy! Summoning the AH mount take 10 seconds, getting mail takes 2-3 seconds per mail, it’s unplayable right now. (Zul’jin-US server, in Silvermoon city)
2 Likes
Thats part of the route, not the final destination/especific wow server. When there are no problems, that node has the same latency of the others. Right now it shows 140ms-150ms and in game I have no problems (180ms).
That especific node is the one that goes up when the latency problem starts around 7pm and everything goes bad until 11pm when it goes back to the usual 180ms and that node is back to ~150ms.
And you can totally log in WoW with 500ms or more.
Yes, I fully understand what you are referring to. I’ve been troubleshooting connection tests to the Blizzard servers for many years. And again, those hops, regardless of data value displayed, are designed to protect against DDoS, which means slow or no response to ICMP traffic (what you’re using for tests). They are still fully functional, but they aren’t set up to report to you.
1 Like
Wouldn’t those be the ones that do not return any value and just “time out”/ *?
That’s what Blizzard told us for many years every time we were asked to run tracertroutes to the IPs they gave us for testing on both CS and their removed tracerout test page.
Doesn’t make sense that two nodes returning timeouts aren’t the ones you’re referring to, but instead one of the nodes actually returning values (and the one that changes at the exact moment of the problem happening).
Nope, they can show no response or an inflated value. Also, you’re pinging a login/authentication server that checks your game license status, not a game server. Game server IPs are not listed publicly anymore.
A long time ago a lot of them would show no response, but not all.
And this is probably part of the reason Blizzard stopped offering any connection troubleshooting. First, Blizzard is a gaming studio, not an ISP. Like any other online business, they pay for hosting at a datacenter (Google in this case) and how you reach it is between you and the company you pay for connection and routing services (the ISP). Second, it’s time consuming to explain or argue with players in tickets about how backbone nodes (Level3) respond to ICMP requests. And finally, since most other AAA game titles aren’t offering connection troubleshooting anymore, it appears Blizzard decided to join them over 2.5 years ago.
1 Like
Same here. Getting terrible lag spikes constantly since the last patch but the home/world ping in game looks fine.
3 Likes
My exact same issue, latency is fine and stable but there are lag spikes coming in like crazy
2 Likes
Same here as well, latency is stable but inputs are getting hung up ( i notice it most trying to do crafting / orders ) , both in live and in classic
2 Likes
yea, everything was fine this morning. Now im having lag all the time. The ping seems to be ok, so maybe is the jitter or something server sided.
1 Like
Yeah I thought it was me but professions and opening the profession reward bags take a while too.
According to wowpedia and other sites, this is the IP to do any kind of traceroute tests to Blizzard servers located in that datacenter.
To be fair, they’re offering almost no kind of support/troubleshooting to anything.
Still, I’m here now at 8:39pm with 400ms+. Like a clock at ~7pm it started and like what is happening for 3 weeks, every single day, it will go away around 11pm.
8 113 ms 117 ms 116 ms et-6-0-8 edge6 Atlanta2 Level3 net [4.7.137.13]
9 * * 487 ms ae2.3608.ear7.Chicago2.net.lumen.tech [4.69.142.178]
10 586 ms 563 ms 545 ms BLIZZARD-EN ear7 Chicago2 Level3 net [4.7.196.134]
It looks like my ISP ends as it enters lumen/Blizzard internal business. But… I guess its just coincidence that both the game and those nodes have problems at the same time and this is not worth looking into.
The amount of players here reporting the same problem, at the same time, with same 3 weeks, while on different ISPs but going through that Lumen/Blizzard route, is not normal.