Hi, so recently my ping went up from about 30-40 to 100-120. Its only wow having this problem.
I’m not disconnecting or anything just that the ping is way higher than what i’m used to.
well, im in romania. on silvermoon realm, my ms wich normally is around 55 66, now sits at over 200. dont know what to do, i’ve restarted the modem, still high ms
I’ve been having the exact same problem for a few days now, and from my investigations I’ve discovered that it’s a problem with the blizzard-owned hop ae1-br02-eqam1.as57976.net [137.221.78.35], and probably also with the hop 80.249.208.83 in lase to blizzard from AMS-IX, which had already caused major problems at the end of last year, even making it impossible to stay connected to the servers for more than a few seconds.
This can also be seen from the tests posted above by another user.
I opened a ticket in the game and the GM said to open a post here, which I did (link below) but it was ignored, maybe Blue aren’t working over the weekend…
Anyway the problem is in blizzard’s infrastructure and now it’s up to them to fix it, the only way around it is to use a VPN and hope to connect to a server that avoids the hop in question.
Hey, got the same problem in Czech Republic. Entire yesterday i was playing with 500-900 latency, and it seemed like the more mobs we pulled in m+, the worse it got, sometimes i was in lag for 3+ seconds xd. At midnight the latency got better and game was playable. Today in the afternoon the lag started again.
Idk how to test latency other than speedtest(.)net, where i get stable 9ms and my ingame latency was normally around 30-40ms.
Hopefully blizzard will do smthing about it, if its really problem on their side.
It might be a different issue, i was playing later in the night (after midnight) and ping went down to the usual 30-40. Now during the day its starting to climb back up, i have about 90 now and i expect to go back to 120-130 later.
I checked your Toppic and I think you are testing on the wrong ip, I don’t doubt that there is a problem but from my tests it is on two hops one leased to blizzard from AMS-IX with ip 80.249.208.83 which was already problematic late last year and hop 137.221.78.35 which is within the actual blizzard infrastructure.
Where did you find the ip 137.221.106.28 on which you tested? Because I have an idea that once we get into the 62.115.x.x ip range we are already inside the blizzard infrastructure and then to get to 137.221.106.28 is blizzard itself routing through america.
Try test with 185.60.112.157 as the destination ip for your treceroute and winmtr and post the results.
Same result, also is consistent with the ping i have in game, as i said during the night it goes back to normal and traceroute is consistent with the problems i’m getting in game.
I have the same provider for my phone and home internet but i tested with another provider with a hotspot and the ping goes down. Problem hotspot is not stable.
Also tried using the ip from resource monitor. The remote adress connecting to wow and its always this point thats giving the problem: 80.249.208.83
From what i found on older posts eu should have this 3 points:
185.60.114.159
185.60.114.158
185.60.114.157 - this is the only one giving problems
EDIT:
I found a random post on reddit saying that using warp by cloudflare fixed his issue and i tested it and it improves the ping a lot.
Just search on google Warp by Cloudflare. It works similar to a vpn from what i’m understanding but its free.
As you can see, the problems start at 80.249.208.83 with an atypical 88>104ms ping rise and then propagate to ae1-br01-eqam1 as57976 net - 0 which has ip 137.221.78.35 94>303ms i.e. the two hops I have reported in several posts.
Even testing with the other 2 ip’s goes through 80.249.208.83 and br01-eqam1 as57976.
As these two hops are then one in lease and one in blizzard infrastructure if blizzard doesn’t act we can’t do anything but use a VPN or WRAP to bypass them until blizzard does something.