Usually I have 40ms.
But today it’s about 150 in Dalaran and about 1000 on random BG - impossible to play.
According to google AI advice I run
netstat -an
while wow.exe is running, found two IPs with port 3724 and tracert them:
> Tracing route to 37.244.62.132 over a maximum of 30 hops
>
> 1 <1 ms <1 ms <1 ms 172.26.0.1
> 2 1 ms 1 ms <1 ms 192.168.144.1
> 3 1 ms 1 ms 1 ms 57.red-81-41-220.staticip.rima-tde.net \[81.41.220.57\]
> 4 \* \* \* Request timed out.
> 5 \* \* \* Request timed out.
> 6 \* \* \* Request timed out.
> 7 10 ms 10 ms 10 ms 216.184.113.248
> 8 11 ms 10 ms \* mad-b3-link.ip.twelve99.net \[62.115.52.140\]
> 9 30 ms 30 ms 30 ms prs-bb2-link.ip.twelve99.net \[62.115.123.220\]
> 10 30 ms 30 ms 30 ms prs-b10-link.ip.twelve99.net \[62.115.137.91\]
> 11 34 ms 34 ms 34 ms prs-bb1-link.ip.twelve99.net \[62.115.137.88\]
> 12 34 ms 34 ms 34 ms prs-b1-link.ip.twelve99.net \[62.115.125.171\]
> 13 34 ms 34 ms 35 ms blizzard-ic-348624.ip.twelve99-cust.net \[62.115.178.205\]
> 14 165 ms \* 165 ms ae1-br02-eqpa4.as57976.net \[137.221.77.35\]
> 15 \* \* \* Request timed out.
> 16 \* \* \* Request timed out.
> 17 144 ms 149 ms 146 ms et-0-0-0-pe03-eqam3.as57976.net \[137.221.78.51\]
> 18 173 ms 175 ms 174 ms 137.221.66.45
> 19 \* \* \* Request timed out.
> 20 \* \* \* Request timed out.
> 21 170 ms \* 167 ms 5.42.176.1
> 22 168 ms 168 ms 170 ms 37.244.62.132
>
> Trace complete.
> Tracing route to 37.244.62.222 over a maximum of 30 hops
>
> 1 <1 ms <1 ms <1 ms 172.26.0.1
> 2 1 ms 1 ms <1 ms 192.168.144.1
> 3 6 ms 7 ms 7 ms 53.red-81-41-220.staticip.rima-tde.net \[81.41.220.53\]
> 4 \* \* \* Request timed out.
> 5 \* \* \* Request timed out.
> 6 \* \* \* Request timed out.
> 7 12 ms 12 ms 12 ms be33-400-grtmadix2.net.telefonicaglobalsolutions.com \[216.184.113.180\]
> 8 13 ms 13 ms 13 ms ae14.edge1.mad1.sp.lumen.tech \[4.68.71.45\]
> 9 32 ms 32 ms 32 ms ae1.3111.edge7.par1.neo.colt.net \[171.75.10.21\]
> 10 56 ms 32 ms 32 ms BLIZZARD-EN.edge7.Paris1.Level3.net \[213.19.199.110\]
> 11 171 ms \* 164 ms ae1-br02-eqpa4.as57976.net \[137.221.77.35\]
> 12 \* \* \* Request timed out.
> 13 \* \* \* Request timed out.
> 14 177 ms 171 ms 150 ms et-0-0-0-pe04-eqam3.as57976.net \[137.221.78.53\]
> 15 175 ms 177 ms 176 ms 137.221.66.47
> 16 \* \* \* Request timed out.
> 17 \* \* \* Request timed out.
> 18 169 ms 168 ms 170 ms 5.42.176.1
> 19 149 ms 141 ms 147 ms 37.244.62.222
>
> Trace complete.
In both cases problems started after the server name started with “blizzard”.
But noone else is complaining here, so is it my problem somehow or Blizzard’s ?
1 Like
You aren’t alone,I’m running Movistar as my fiber ISP, and most of the major spanish streamers and guilds have experiencied this behaviour all week long, here’s my MTR that confirms your case as well:
My traceroute [v0.95]
k55vd (192.168.1.37) → 37.244.62.104 (37.244.62.104) 2025-10-25T21:19:48+0200Keys: Help Display mode Restart statistics Order of fields quitPackets PingsHost Loss% Snt Last Avg Best Wrst StDev
- 192.168.1.1 0.0% 75 0.7 1.0 0.5 6.9 1.0
- 192.168.144.1 0.0% 75 2.4 2.8 1.8 4.1 0.4
- 105.red-81-41-221.staticip.rima- 0.0% 75 2.9 2.9 1.9 4.0 0.4
- (waiting for reply)
- (waiting for reply)
- (waiting for reply)
- 216.184.113.248 0.0% 75 12.4 12.5 11.5 19.2 0.9
- mad-b3-link.ip.twelve99.* 60.0% 75 25.1 14.0 12.5 25.1 3.0
- prs-bb1-link.ip.twelve99.* 0.0% 75 36.9 36.9 36.1 37.6 0.3
- prs-b1-link.ip.twelve99.* 0.0% 75 32.8 32.8 32.2 34.9 0.4
- blizzard-ic-348624.ip.twelve99-c 0.0% 74 36.9 40.9 36.2 107.9 10.6
- ae1-br02-eqpa4.as57976.* 10.8% 74 175.4 175.9 154.4 212.3 7.5
- (waiting for reply)
- (waiting for reply)
- et-0-0-1-pe04-eqam3.as57976.* 0.0% 74 96.5 101.1 55.2 163.0 22.8
- 137.221.66.47 0.0% 74 52.5 48.4 46.7 53.7 1.8
- (waiting for reply)
- (waiting for reply)
- 5.42.176.1 14.9% 74 174.7 173.2 165.9 180.2 2.4
As we can see we’re experiencing a major packet loos on the madrid link for twelve99, why is this happening? I only can suspect it’s related to the botched football blockage going on, either way I’d like for Blizzard to weight in on this one.
1 Like
I’m playing from Tenerife this week and it was a rather decent experience so far, but today 25/10/25, starting somewhere around 14.00 I started having a VERY high latency, like, anywhere between 300ms and 17000ms. It doesn’t go lower than 300ms at all, which is not very useful in the game.
those with port 3724:
1 3 ms 1 ms 2 ms 172.172.1.1
2 3 ms 3 ms 6 ms 192.168.144.1
3 6 ms 4 ms 4 ms 85.red-81-41-251.staticip.rima-tde. net [81.41.251.85]
4 28 ms 29 ms 29 ms 190.red-81-41-252.staticip.rima-tde. net [81.41.252.190]
5 * * * Request timed out.
6 29 ms 29 ms 28 ms 216.184.113.248
7 * * 30 ms mad-b3-link. ip.twelve99. net [62.115.52.140]
8 53 ms 53 ms 52 ms prs-bb2-link. ip.twelve99. net [62.115.123.220]
9 51 ms 52 ms 51 ms prs-b10-link. ip.twelve99. net [62.115.137.91]
10 53 ms 53 ms 53 ms prs-bb1-link. Ip.twelve99. net [62.115.137.88]
11 52 ms 50 ms 50 ms prs-b1-link. Ip.twelve99. net [62.115.125.171]
12 55 ms 53 ms 88 ms blizzard-ic-348624. Ip.twelve99-cust. net [62.115.178.205]
13 225 ms 200 ms 203 ms ae1-br02-eqpa4.as57976. net [137.221.77.35]
14 * * * Request timed out.
15 * * * Request timed out.
16 205 ms 203 ms 204 ms et-0-0-1-pe04-eqam3.as57976 .net [137.221.78.69]
17 203 ms 207 ms 208 ms 137.221.66.47
18 * * * Request timed out.
19 * * * Request timed out.
20 208 ms 199 ms 199 ms 5.42.176.1
21 201 ms 200 ms 202 ms 66.40.182.182
Trace complete.
Tracing route to 66.40.182.182 over a maximum of 30 hops
1 2 ms 4 ms 2 ms 172.172.1.1
2 5 ms 4 ms 3 ms 192.168.144.1
3 5 ms 4 ms 4 ms 85.red-81-41-251.staticip.rima-tde .net [81.41.251.85]
4 28 ms 28 ms 29 ms 190.red-81-41-252.staticip.rima-tde .net [81.41.252.190]
5 * * * Request timed out.
6 28 ms 27 ms 29 ms 216.184.113.248
7 39 ms 32 ms * mad-b3-link .ip.twelve99 .net [62.115.52.140]
8 52 ms 53 ms 54 ms prs-bb2-link .ip.twelve99 .net [62.115.123.220]
9 51 ms 52 ms 51 ms prs-b10-link .ip.twelve99 .net [62.115.137.91]
10 54 ms 53 ms 53 ms prs-bb1-link.ip.twelve99 .net [62.115.137.88]
11 52 ms 51 ms 52 ms prs-b1-link .ip.twelve99 .net [62.115.125.171]
12 55 ms 55 ms 94 ms blizzard-ic-348624 .ip.twelve99-cust .net [62.115.178.205]
13 201 ms * 202 ms ae1-br02-eqpa4.as57976 .net [137.221.77.35]
14 * * * Request timed out.
15 * * * Request timed out.
16 199 ms 202 ms 204 ms et-0-0-1-pe04-eqam3.as57976 .net [137.221.78.69]
17 204 ms * 206 ms 137.221.66.47
18 * * * Request timed out.
19 * * * Request timed out.
20 214 ms 206 ms 207 ms 5.42.176.1
21 199 ms 196 ms 197 ms 66.40.182.182
Trace complete.
Same problem here, playing from Cordoba with O2 (works with Movistar fiber) and i got like 300-400ms on open world, and when i enter on Raid i get like 15000ms, it’s impossible to play.
1 Like
Ooooh, so this is spanish problem, not Blizzard’s…
1 Like
yeah I don’t know which ISP I have here, but I have the same - open world around 300-600ms, sometimes goes higher, raids are just massacre (and it’s just LFR), I’m playing Legion Remix
who knows really, it’s somewhere between spanish ISPs and Blizzard servers, but the package loss is obvious
UPD. Today, 26/10/2025 situation didn’t improve by a single bit, ping is red all the time, it’s unplayable
UPD 2. Installed WTFast, immediately ping 55ms, home and world, all perfect. Goes through Madrid 12 to Brussels 3 to Amsterdam 17, instead of directly Madrid 12 to Eadhoven node.
Hi gents,
Same thing from Poland since Friday24.10.2025 afternoon. Very high World latency.
Support ticket closed after I did everything they suggested and resolution was to go to forums and ask community. Perfect, but at least I am not alone.
Fix: Installed ExitLag…turnen on, Home and World latency very low…turned off, World low, Home a big higher, but it doesn’t matter to run m+.
2 Likes
At least we can now confirm that it’s not only happening to users in Spain. It had been happening to me for a few days, and I thought it was just lag issues due to the number of people playing, so I didn’t pay much attention to it until it became constant. It might have started after the last maintenance, since it didn’t happen before, but I’m not sure. I hope they can confirm something for us. The idea of trying ExitLag is tempting, but I don’t want to pay for another subscription just to make the most of this one… Let’s see what Blizzard has to say.
This morning latency looks Ok - 40ms.
I hope the problem is fixed and latency will remain tiny until this evening and forever 
Unfortunately, yesterday morning I also had good ping, but things keep getting worse as the day goes on, and by night it becomes unplayable. I really hope I’m wrong and that they’ve actually fixed it, but in my case, yesterday I had low ping in the morning, and around 8:00 p.m. the problems started again.
Yes, same thing now - 1000ms and more…
1 Like