World MS spikes in dungeons

Hello! Game has been unplayable for weeks and it feels like I have tried everything, must be on blizzards end as EVERYTHING else works. Even while the lag happens in WoW. Chat works in WoW for example. My friends hear me on discord, youtube and twitch are still playing. Other games is online. Its only WoW that is affected.
It always happens during the night and its making it really hard to play dungeons when world ms spikes to 1000 every 30 sec.
Here are my trace routes.

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms home [192.168.1.1]
2 8 ms 8 ms 8 ms 100.72.128.3
3 9 ms 8 ms 8 ms h-46-59-119-49.NA.cust.bahnhof.se [46.59.119.49]
4 * * * Request timed out.
5 9 ms 8 ms 8 ms sto-ste-er1.sto-ste-hypernode2.bahnhof.net [158.174.156.182]
6 9 ms 8 ms 8 ms 158.174.156.128
7 9 ms 10 ms 9 ms sto-ste-er1.sto-cr1.bahnhof.net [46.59.112.42]
8 9 ms 8 ms 8 ms sto-cr1.sto4-er1.as8473.net [46.59.112.175]
9 9 ms 9 ms 9 ms pni-bahnhof-blizzard.bahnhof.net [46.59.118.193]
10 28 ms 27 ms 27 ms ae1-br01-eqsk1.as57976.net [137.221.86.33]
11 * * * Request timed out.
12 * * * Request timed out.
13 27 ms 27 ms 27 ms bond0-vs01-eqam1.as57976.net [137.221.78.57]
14 28 ms 28 ms 27 ms 137.221.66.43
15 27 ms 27 ms 27 ms 185.60.112.157

Trace complete.

Tracing route to 185.60.112.158 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms home [192.168.1.1]
2 8 ms 8 ms 8 ms 100.72.128.3
3 9 ms 8 ms 8 ms h-46-59-119-49.NA.cust.bahnhof.se [46.59.119.49]
4 * * * Request timed out.
5 9 ms 8 ms 8 ms 158.174.156.131
6 9 ms 9 ms 9 ms 158.174.156.128
7 9 ms 9 ms 9 ms sto-ste-er1.sto-cr1.bahnhof.net [46.59.112.42]
8 9 ms 9 ms 9 ms sto-cr1.sto4-er1.as8473.net [46.59.112.175]
9 9 ms 9 ms 9 ms pni-bahnhof-blizzard.bahnhof.net [46.59.118.193]
10 27 ms 27 ms 27 ms ae1-br01-eqsk1.as57976.net [137.221.86.33]
11 27 ms 28 ms 28 ms et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
12 * * * Request timed out.
13 27 ms 27 ms 27 ms 137.221.78.53
14 27 ms 27 ms 27 ms 185.60.112.158

Trace complete.

Tracing route to 185.60.112.159 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms home [192.168.1.1]
2 8 ms 8 ms 8 ms 100.72.128.3
3 8 ms 8 ms 8 ms h-46-59-119-49.NA.cust.bahnhof.se [46.59.119.49]
4 * * * Request timed out.
5 9 ms 8 ms 8 ms 158.174.156.239
6 9 ms 9 ms 8 ms 158.174.156.128
7 9 ms 9 ms 9 ms sto-ste-er1.sto-cr1.bahnhof.net [46.59.112.42]
8 8 ms 9 ms 8 ms sto-cr1.sto4-er1.as8473.net [46.59.112.175]
9 9 ms 9 ms 9 ms pni-bahnhof-blizzard.bahnhof.net [46.59.118.193]
10 27 ms 27 ms 27 ms ae1-br01-eqsk1.as57976.net [137.221.86.33]
11 27 ms 27 ms 27 ms et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
12 * * * Request timed out.
13 28 ms 27 ms 27 ms 137.221.78.53
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

All 3 differents Ip Adresses.

Its the route, nothing you can do, not sure if Blizzard can also do something , the only entity guilty is the peering provider blizzard is using for route. I told them couple of times already to raise the issue to them because the problem is from there.

1 Like

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