Absurd latency spikes

Support Technical Support
1

Another key bites the dust.

Man, never expected that I might have to stop playing WoW due to Blizzard’s inability to fix an issue that’s being going on for several months already. As it stands I can’t raid, can’t do pvp, can’t do keys, and even delves became an issue. God, I really wish I didn’t have to pretend I’m calmly writing this post, and could just say what I really mean :slight_smile: Alas.

The nodes at fault are the same ones people have been reporting since February of this year:

  • ae3-4.rt.eqx.fkt.de.retn.net / 87.245.232.233
  • pr01.eqfr5.blizzardonline.net / 80.81.195.26
  • ae1-br01-eqfr5.as57976.net / 137.221.80.33

Here’s the actual moment of latency spike in PingPlotter: https://i.imgur.com/m7GXrly.png

I’m tired of describing the issues every single time, so I’m just leaving the link to some previous threads on this matter: one with 70 replies, the other with 370. There have been dozens of other threads as well, but they all have 2 things in common: 1. describe the same issue, 2. no response from Blizz at all.

Number one from February:

Number two from April (been going for months):

And with the release of TWW even more people have started having these issues: and there’s still not a single utterance from Blizzard on this issue. Guess I’ll just save this post - in case Blizzard acknowledges it via removing it - to post in a few days.

Let’s see if opening an issue at the Office of Customer Protection (ECC-Net) yields any results. If not - well, I’ve been collecting aaall the logs these past 6 months, all “issues” with sending tickets, and some other anti-consumer practices… will have to check what I can do with them.

And to all others with the same issue: keep reporting it, sending tickets en masse, and doing everything you can to force Blizzard to acknowledge the issue. Maybe one day we’ll be able to raid / do keys again.

6 Likes
2

Last week a lot of ppl got this problem and wrote about on this forum… And we got zero responses. It is quite odd, but it looks like, customer support reps simply disappeared from the forum after the enormous counts of complaint about the same issue.

It’s funny because it looks as if they hide and wait for the storm to pass. But it won’t until they fix it - time shows that it is only getting worse.
I hope, at least, they sent info to their technical stuff before they hid in bunkers.

2 Likes
3

Yeah, I just got a 30 second freeze spike in an instance (Follower dungeon). Yesterday I got one when fighting Spinshroom and died because of that.

I don’t understand what’s going on honestly. Funnily enough, it even causes my computer’s brower to be slow too. Despite getting ping from both server and google etc when doing a ping in Terminal.

1 Like
4

i do have same problem and Raids are big fps problem and lag, but i dont want to write more, i did start other game, and will probably unsub. dont want to pay to some one who does not care about players and dont want to fix game

4 Likes
5

Yep, same issue.

Game “stops” for a minute or two, and then sprint back to normal. Dont need to tell you that I am dead by the time its back to normal.

Spike starts at et-0-0-1-pe01-eqam3.as57976.net (137.221.78.55)

Have this problem since reales of TWW (back in DF s1 or s3 no issue)

3 Likes
6

Yeah,

have it since end of s3 and all s4 of Dragonflight.

In TWW I have it too, but less.

Still can’t do mythic progression and usually dieing in m+ and with current m+ iteration high keys are not for me in that case.

Will wait 1-2 months and if not fixed I am done with game for good. Tired of Blizz.

1 Like
7

There seems to be something going on in Europe, I guess?

I sometimes get 40 % loss just before Blizzard servers. Just now I got 20 % loss between hops 3 and 9 going through my country (Sweden) through Europe to Paris.

8

i got these spikes last few months its horrible

1 Like
9

Again 4 times during the last 1 hour.

pingplotter show an issue here ae2-br02-eqam1_as57976_net and nodes below.

2 Likes
10

The same old routing issues. Been happening since february, bouta celebrate a full year of this :slight_smile:

11

Can you scroll down to the last node(s)? This doesn’t say anything so far.

Those seem to be routing nodes somewhere in exchanges, I think. Those tend to not prioritize ICMP Echo requests (Ping). Latency spikes at those nodes, and even packet loss, is expected when doing these connectivity tests and is not any meaningful indication unless the latency and packet loss continues or worsens from that point all the way to the end-node. Always, and I mean always, include the first nodes and last nodes, those are the primary points of interest.

12

You can check this one: Disconnected from WoW all day, WinMTR logs included - #2 by Кеттарол-howling-fjord
There’s a problem connecting 185.60.114.159 (one of battle.net IPs). For me, at least. There’re routing problem on one of blizzard nodes after cn-lgpy1-ia-bons-02.as57976 hop.
There are also traceroutes from other ppl with the same tendency

13

The great example of what happens if you do nothing to fix an issue. Even more people start getting it as we can see from other treads on forum and reddit.
And zero responses from Blizzard, however they quickly responds after similar problem in Poland and fixed it… But Denmark, UK and other countries? They don’t care, total silence.

14

Idk, the first trace there doesn’t look odd in any way. ± 29 ms to the final Blizzard node without loss is fine.

In the second trace, your ISP is just messing up (or their peering partners) by routing traffic from Hungary to South Korea, way before reaching Blizzard’s AS? Contact them to fix their odd (or cheap) routing.

15

Even with this odd mess up 2 blizzard nodes get ping (et0 and icn), I checked it several times. But hops 24-30 send no response and they don’t even required to send back ping through Korea btw. It depends on blizzard router mac tables, etc. If korean nodes were only issue - i couldn’t get a ping back from netherlands blizz routers.

Anyway, it is in Blizzard interest to find a solution for their players to get an access to their servers. My case is not unique, a lot ppl have this troubles, sadly.

16

Honestly, that’s prob a limitation of the test in use. There should in most cases be no hop 24-30.

With all due respect, but it doesn’t work like this.

Your ISP and your ISP’s peers steer you to Korea, not Blizzard. You can blame Blizzard for it, but it’s false.

1 Like
17

Bro i totally agree with you thats all i can say because u say it a lot more than is needed as a proof… u cant doo a single key/raid without a lag or two (metaphoritically) LITERALLY from several months this game is completely unplayable because u dont know when the COSMIC lag spike occur… this is only in WoW either retail or classic titles all other games works totally fine no lag no spike totally pure normal working but WoW is UNPLAYABLE!!! fix the damn servers… let us doo keys and raid content.

1 Like
18

Eveyrhting’s included - check the image (imgur link).

Another 4 situations like this today. Casualties: 1 key, 2 lives at delves. Blizzard has become an affix unto itself.

2 Likes
19

if we only get any reaction from blizzard at all…

2 Likes
20

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.