Extreme World Latency in the evenings

I’m having insane World Latency pretty much every day in the evenings, making the game effectively unplayable.
My connection is far from stressed, everything works perfectly outside of WoW.
My Routers interface doesn’t show any issues.
Restarting my Router and my Game doesn’t change anything. Neither does playing without Addons.

Here’s my looking glass results when the issues happened once:
TRACEROUTE:
traceroute to 178.20.88.92 (178.20.88.92), 15 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * ams1a-admin-looking-glass-back01 (37.244.16.56) 989.016 ms !H 989.004 ms !H

25/02/2023 21:08:09 UTC

TRACEROUTE:
traceroute to 178.20.88.92 (178.20.88.92), 15 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * 178.20.88.92 (178.20.88.92) 17.954 ms

25/02/2023 21:08:09 UTC

PING:
PING 178.20.88.92 (178.20.88.92) 56(84) bytes of data.
From 37.244.16.56 icmp_seq=2 Destination Host Unreachable
From 37.244.16.56 icmp_seq=3 Destination Host Unreachable

— 178.20.88.92 ping statistics —
4 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2999ms
pipe 3

25/02/2023 21:08:09 UTC

PING:
PING 178.20.88.92 (178.20.88.92) 56(84) bytes of data.
From 37.244.16.87 icmp_seq=2 Destination Host Unreachable
From 37.244.16.87 icmp_seq=3 Destination Host Unreachable

— 178.20.88.92 ping statistics —
4 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2998ms
pipe 2

25/02/2023 21:08:09 UTC

TRACEROUTE:
traceroute to 178.20.88.92 (178.20.88.92), 15 hops max, 60 byte packets
1 ams1b-admin-looking-glass-back01 (37.244.16.87) 1257.346 ms !H 1257.330 ms !H 1257.327 ms !H

25/02/2023 21:08:14 UTC

TRACEROUTE:
traceroute to 178.20.88.92 (178.20.88.92), 15 hops max, 60 byte packets
1 37.244.50.146 (37.244.50.146) 1.042 ms 2.013 ms 2.019 ms
2 * * *
3 137.221.66.36 (137.221.66.36) 0.496 ms 0.517 ms 0.501 ms
4 137.221.77.54 (137.221.77.54) 9.456 ms 9.475 ms 9.488 ms
5 137.221.65.27 (137.221.65.27) 9.222 ms 9.258 ms 9.261 ms
6 137.221.80.34 (137.221.80.34) 9.468 ms 9.490 ms 9.469 ms
7 * * *
8 212.91.228.66 (212.91.228.66) 21.377 ms 21.385 ms 21.384 ms
9 212.91.230.17 (212.91.230.17) 23.813 ms 24.125 ms 24.336 ms
10 178.20.88.92 (178.20.88.92) 23.314 ms * *

25/02/2023 21:08:15 UTC

PING:
PING 178.20.88.92 (178.20.88.92) 56(84) bytes of data.
From 37.244.16.87 icmp_seq=1 Destination Host Unreachable
64 bytes from 178.20.88.92: icmp_seq=2 ttl=51 time=1034 ms
64 bytes from 178.20.88.92: icmp_seq=4 ttl=51 time=17.5 ms

— 178.20.88.92 ping statistics —
4 packets transmitted, 2 received, +1 errors, 50% packet loss, time 2999ms
rtt min/avg/max/mdev = 17.529/526.113/1034.698/508.585 ms, pipe 2

25/02/2023 21:08:14 UTC

PING:
PING 178.20.88.92 (178.20.88.92) 56(84) bytes of data.

— 178.20.88.92 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

25/02/2023 21:08:17 UTC

MTR:
Start: Sat Feb 25 21:08:09 2023
HOST: ams1a-admin-looking-glass-back01 Loss% Snt Last Avg Best Wrst StDev
1.|-- Blizzard 40.0% 10 0.9 19.4 0.7 107.5 43.2
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 137.221.66.40 30.0% 10 0.5 117.8 0.4 821.8 310.4
4.|-- 137.221.78.54 30.0% 10 6.3 141.3 6.2 684.7 253.5
5.|-- 137.221.65.156 30.0% 10 100.7 100.7 6.1 541.6 197.3
6.|-- 137.221.65.28 30.0% 10 40.5 67.3 6.2 398.9 146.8
7.|-- 137.221.80.32 30.0% 10 6.6 43.5 6.3 255.9 93.7
8.|-- ??? 100.0 6 0.0 0.0 0.0 0.0 0.0
9.|-- 212.91.228.66 0.0% 6 15.4 15.4 15.3 15.5 0.0
10.|-- 212.91.230.17 0.0% 6 19.7 19.2 17.9 20.4 0.8
11.|-- 178.20.88.92 83.3% 6 18.0 18.0 18.0 18.0 0.0

25/02/2023 21:08:09 UTC

MTR:
Start: Sat Feb 25 21:08:09 2023
HOST: ams1b-admin-looking-glass-back01 Loss% Snt Last Avg Best Wrst StDev
1.|-- Blizzard 70.0% 10 0.8 121.6 0.8 363.2 209.2
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 137.221.66.44 60.0% 10 0.5 287.9 0.5 1076. 526.6
4.|-- 137.221.78.66 60.0% 10 6.0 298.8 6.0 1076. 519.2
5.|-- 137.221.65.156 60.0% 10 7.5 222.1 6.2 797.7 385.2
6.|-- 137.221.65.28 60.0% 10 9.0 168.6 6.2 652.9 322.9
7.|-- 137.221.80.32 60.0% 10 32.7 158.3 11.4 528.3 247.5
8.|-- ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
9.|-- 212.91.228.66 0.0% 3 15.4 15.5 15.4 15.6 0.0
10.|-- 212.91.230.17 0.0% 3 17.4 19.6 17.4 21.0 1.9
11.|-- ??? 100.0 3 0.0 0.0 0.0 0.0 0.0

25/02/2023 21:08:09 UTC

TRACEROUTE:
traceroute to 178.20.88.92 (178.20.88.92), 15 hops max, 60 byte packets
1 37.244.50.146 (37.244.50.146) 0.849 ms 1.853 ms 1.854 ms
2 * * *
3 137.221.66.36 (137.221.66.36) 0.423 ms 0.446 ms 0.445 ms
4 137.221.77.54 (137.221.77.54) 9.419 ms 9.458 ms 9.467 ms
5 137.221.65.27 (137.221.65.27) 9.619 ms 9.624 ms 9.623 ms
6 137.221.80.34 (137.221.80.34) 9.569 ms 9.450 ms 9.392 ms
7 * * *
8 212.91.228.66 (212.91.228.66) 21.394 ms 21.452 ms 21.432 ms
9 212.91.230.17 (212.91.230.17) 22.731 ms 22.848 ms 23.269 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

25/02/2023 21:08:22 UTC

MTR:
Start: Sat Feb 25 21:08:12 2023
HOST: ams1b-admin-looking-glass-back01 Loss% Snt Last Avg Best Wrst StDev
1.|-- Blizzard 40.0% 10 2.0 28.5 1.1 163.3 66.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 137.221.66.44 30.0% 10 0.4 125.6 0.3 876.1 331.0
4.|-- 137.221.78.66 30.0% 10 43.5 155.4 6.3 876.6 319.4
5.|-- 137.221.65.156 30.0% 10 25.9 99.0 6.2 597.8 220.4
6.|-- 137.221.65.28 30.0% 10 6.7 75.3 6.0 452.9 167.1
7.|-- 137.221.80.32 30.0% 10 6.3 52.4 6.2 328.4 121.7
8.|-- ??? 100.0 6 0.0 0.0 0.0 0.0 0.0
9.|-- 212.91.228.66 0.0% 6 15.7 15.6 15.4 15.8 0.0
10.|-- 212.91.230.17 0.0% 6 16.3 17.7 16.3 20.2 1.3
11.|-- ??? 100.0 6 0.0 0.0 0.0 0.0 0.0

25/02/2023 21:08:12 UTC

MTR:
Start: Sat Feb 25 21:08:14 2023
HOST: cdg1a-admin-looking-glass-back01 Loss% Snt Last Avg Best Wrst StDev
1.|-- 37.244.50.131 0.0% 10 1.2 1.0 0.8 1.3 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 137.221.66.34 0.0% 10 0.6 0.6 0.4 1.3 0.0
4.|-- 137.221.77.80 0.0% 10 9.3 9.7 9.3 12.6 0.9
5.|-- 137.221.65.27 0.0% 10 9.3 12.8 9.1 43.1 10.6
6.|-- 137.221.80.34 0.0% 10 9.6 14.8 9.3 54.9 14.2
7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8.|-- 212.91.228.66 0.0% 10 20.9 21.0 20.9 21.3 0.0
9.|-- 212.91.230.17 0.0% 10 21.8 25.0 21.8 26.6 1.4
10.|-- 178.20.88.92 30.0% 10 23.6 23.4 23.2 23.6 0.0

25/02/2023 21:08:14 UTC

PING:
PING 178.20.88.92 (178.20.88.92) 56(84) bytes of data.

— 178.20.88.92 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3009ms

25/02/2023 21:08:25 UTC

TRACEROUTE:
traceroute to 178.20.88.92 (178.20.88.92), 15 hops max, 60 byte packets
1 37.244.50.131 (37.244.50.131) 3.154 ms 3.145 ms 3.276 ms
2 * * *
3 137.221.66.34 (137.221.66.34) 0.382 ms 0.431 ms 0.437 ms
4 137.221.77.80 (137.221.77.80) 23.730 ms 23.789 ms 23.805 ms
5 137.221.65.27 (137.221.65.27) 9.414 ms 9.479 ms 9.500 ms
6 137.221.80.34 (137.221.80.34) 9.842 ms 9.665 ms 9.662 ms
7 * * *
8 212.91.228.66 (212.91.228.66) 20.977 ms 21.064 ms 21.076 ms
9 212.91.230.17 (212.91.230.17) 26.504 ms 26.513 ms 26.704 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

25/02/2023 21:08:27 UTC

PING:
PING 178.20.88.92 (178.20.88.92) 56(84) bytes of data.

— 178.20.88.92 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3000ms

25/02/2023 21:08:28 UTC

MTR:
Start: Sat Feb 25 21:08:19 2023
HOST: cdg1a-admin-looking-glass-back01 Loss% Snt Last Avg Best Wrst StDev
1.|-- 37.244.50.131 0.0% 10 1.0 2.0 0.9 7.5 1.9
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 137.221.66.34 0.0% 10 0.6 0.5 0.3 0.6 0.0
4.|-- 137.221.77.80 0.0% 10 82.1 37.7 9.2 143.7 48.4
5.|-- 137.221.65.27 0.0% 10 25.7 13.2 9.3 29.7 7.7
6.|-- 137.221.80.34 0.0% 10 9.5 12.4 9.5 27.1 5.9
7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8.|-- 212.91.228.66 0.0% 10 21.1 21.2 21.0 22.0 0.0
9.|-- 212.91.230.17 0.0% 10 24.7 23.4 21.7 25.6 1.3
10.|-- 178.20.88.92 90.0% 10 23.3 23.3 23.3 23.3 0.0

25/02/2023 21:08:19 UTC

MTR:
Start: Sat Feb 25 21:08:25 2023
HOST: cdg1b-admin-looking-glass-back01 Loss% Snt Last Avg Best Wrst StDev
1.|-- 37.244.50.146 0.0% 10 0.9 1.1 0.9 1.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 137.221.66.36 0.0% 10 0.7 0.6 0.4 0.8 0.0
4.|-- 137.221.77.54 0.0% 10 9.7 55.5 9.3 232.3 89.9
5.|-- 137.221.65.27 0.0% 10 29.0 18.3 9.2 77.7 21.8
6.|-- 137.221.80.34 0.0% 10 9.6 17.1 9.5 68.1 18.6
7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8.|-- 212.91.228.66 0.0% 10 21.5 21.6 21.4 22.0 0.0
9.|-- 212.91.230.17 0.0% 10 25.0 24.1 22.2 27.2 1.7
10.|-- 178.20.88.92 90.0% 10 24.0 24.0 24.0 24.0 0.0

25/02/2023 21:08:25 UTC

And for the love of god, please don’t tell me to contact my ISP. You know that they won’t do anything, and so do I.

1 Like

Another looking glass result: https://pastebin.com/j2HxhqsE

It’s been absolute lag fest recently world ms spiking like crazy causing action delay sometimes with 50-90 ms still have delay absolutely unplayable, Tyralion is the server 2 weeks before no delay in 50-90ms. Having 3 second gcd with low ms seems like a server issue to me.

i’m having extreme Latency too. Even just rn (16:37)
484 ms (local)
707 ms (Realm)

(16:38)
511 ms (Local)
739 ms (realm)

i’m on preety dead realm too, so idk what is going on. (and no, it’s not a connection problem, cause anything else exept wow works super well.

Here’s another looking glass from today: https://pastebin.com/GrEaJWcd

Aaaand another looking glass from just now, when world latency was at 240ms: https://pastebin.com/HKraEaVm

Can someone finally shed some light on this? It’s extremely frustrating how unplayable it makes this game.
Like clockwork, every late afternoon to evening the world latency goes to absolute garbage

vodafone as isp?

No, a local company called DNS:NET. It’s not their fault though, doesn’t make sense.

Issue still persists btw. Doing ANYTHING in the afternoon = constant 1 to 2s stutter lags etc.

1 Like

i had same problem!

It just doesn’t stop. It’s still the same, the game is absolutely unplayable.

If you won’t let me create a ticket, then at least respond to this topic. What an embarrassment of a support team.
I know that whoever is responsible for this forum probably has no idea how to fix this and waaaaay too little time. But at least ONE response that acknowledges the problem and sends it to the right person would be nice.

My realm isn’t even a possibility for looking glass anymore. Wtf is going on?

And I STILL can not create a ticket about the topic.

You can’t submit this ticket.
An error has occurred. This may be a temporary error, so please try again later.

It is NOT temporary, as I’ve tried every day for almost two weeks now.

Since you won’t let me create a ticket:
tracert1: https://pastebin.com/5G8q3r3n
tracert2: https://pastebin.com/mW7gEHe0
tracert3: https://pastebin.com/3ydUzAif

As looking glass doesn’t work anymore, here are traceroutes for the 3 european IPs listed in your support article. I won’t post my msinfo and dxdiag here.

And IF I someday get graced with a response here, don’t you dare tell me to go read https://eu.battle.net/support/en/article/99037

It didn’t help anything, I need some actual insight and help here. I’m losing my mind over this garbage.

1 Like

Hey there

I have exactly the same issue since this wednesday (maintenance windows to be exact).

First things first:
The latency problem only affects the world ping (ping for character and world interactions), not the home ping (chat etc.). The more traffic there is (the more action on the screen) the worse the lags get. Arathi Blizzard is perfectly to test: low action because of low range of sight → low traffic → only small lag spikes up to 150ms (bad enough). On a normal random battleground (or rated) with 10 to 15 players with normal range of sight → latency goes up to SECONDS and is completely unplayable.

I completed every single step in every guide available in the support section or the forum. From checking everything on my own computer, network, router, from software to hardware.

There is not a single issue despite this latency in World of Warcraft. I let some tracert run to check the dev of latency. What i observed is that the increase of latency only occurs while WoW is running → tracert latency without wow is perfectly fine (everything around 30 ms). This happens to every IP mentioned online by blizzard (185.61.112.157, 185.61.112.158, 185.61.114.159). Even tested with different VPNs to different Locations worldwide, no change.

The insane latency increases or even timeouts only occurs on the hops after the first blizzardonline.net-address (pr01.eqfr5.blizzardonline.net [80.81.195.26]). So I guess it’s not on our end OR on the end of our ISP so it has to be on blizzards end. I got a different ISP than you @Guffin and already contacted them as well. They can’t really do anything about it…

EDIT2: And another note, latency is 90% a problem between 6pm and 10pm, in the prime time…

1 Like

Hey,

It seems that I am facing the same issue as you guys. Important lag in WoW only, while everything else is fine. Software/network/hardware are fine, other games are fine. And sometimes it seems to be related to the party I am in (maybe it’s switching between the three EU servers depending on group realm).

Yeah i noticed this as well, sometimes when i get invited, i instantly get a 200-400ms world ping…

Same thing here. Everything else I use the network works perfectly fine. The ISP has no clue, they dont see the problem on their end. Tracert gives similar results at the step with blizzardonline.
World ping was always around 32ms now it sometimes gets near 1000ms.
It doesn’t matter what I’m doing in game it just happens randomly. Skills, groups, interaction with npc, mount up, dragonflying, changing talents, etc.
Eventually I gotta ALT F4 because I can’t even log out or shut down the game from the menu…

Usually my Home and World ping is around 16ms. But when the problems occur World ping is instantly around 1000ms - 20 000ms.
I’ve had the same issue for a week even without any addons.
Drivers up to date, all network connections checked.

It seems to happen every now and then when I load the game (zoning in/out, restarting the game and such).
A simple /reload does not work, have to restart the game a few times and then its back to normal til next time it happens.

Tried all of the tools (Traceroute, Pathping, Looking Glass) provided by Blizzard but results came back normal, nothing out of the ordinary. I also swapped to new TP cables before I tried.

Problem persists, desperation is nigh.
S.O.S TTT
(Send help)