World MS 1000+ - Unplayable Game

Support Technical Support
190

UPDATE: 14 days that the game is unplayable.

→ I found many similar threads on US forums.

→ I found similar old post on EU and US forums regarding WoW but also Overwatch or Diablo.

→ In the many tracer routes I did, I notice this node: hnk-b1-link.ip.twelve99(dot)net
So I searched a little and found out that this node is operated by GoDaddy(dot)com (the worst hosting provider on earth). Blizzard works with this company and use their nodes to link to their servers. In old posts I found issues with the nodes operated by this company. In this scenario, there is absolutely nothing we can do to solve the issue, only Blizzard can deal with it by contacting their “partner” or maybe even they own them I haven’t searched yet and solve the issue or use different nodes.

→ I am completely losing motivation and hope. I am a big WoW player, and was ready to push hard the beginning of this season 4 with my friends but it has not been possible for 2 weeks and Blizzard seems to absolutely not give a damn. Not only we cannot play but we also lose a HUGE amount of time trying to fix this issue. This is sad that such a great game is controlled by such a poor company.

3 Likes
191

Requests timing out, started about 8 days ago. One consistent timing - exactly 3pm or 9:10pm on the clock and my ms goes into 10k (apologies to that mythic group for screwing your 0 for the week)

Country: HK
Server: Retail EU
Traces:
Tracing route to 185.60.112.157 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  ***
  2     5 ms     5 ms     4 ms  1-98-17-223-on-nets.com [***] 
  3     2 ms     1 ms     1 ms  ***
  4     3 ms     3 ms     2 ms  ***
  5     3 ms    12 ms     3 ms  218.188.28.65 
  6     *        *        *     Request timed out.
  7     4 ms     3 ms     5 ms  203.131.243.129 
  8     4 ms     4 ms     4 ms  4.68.75.93 
  9   299 ms   309 ms   302 ms  ae2.3211.edge7.par1.neo.colt.net [171.75.9.205] 
 10   478 ms   479 ms   480 ms  BLIZZARD-EN.edge7.Paris1.Level3.net [213.19.199.110] 
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   308 ms   308 ms   308 ms  137.221.78.55 
 15   315 ms   315 ms   315 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 ***
  2     6 ms     5 ms     4 ms  1-98-17-223-on-nets.com ***
  3     2 ms     3 ms     2 ms  ***
  4     2 ms     2 ms     4 ms  ***
  5     3 ms     2 ms     2 ms  218.188.28.65 
  6     *        *        *     Request timed out.
  7     3 ms     3 ms     3 ms  203.131.243.129 
  8     5 ms     4 ms     3 ms  4.68.75.93 
  9   301 ms   300 ms   301 ms  ae2.3211.edge7.par1.neo.colt.net [171.75.9.205] 
 10   486 ms   486 ms   525 ms  BLIZZARD-EN.edge7.Paris1.Level3.net [213.19.199.110] 
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   306 ms   306 ms   305 ms  137.221.78.55 
 15   309 ms   308 ms   308 ms  137.221.66.41 
 16   311 ms   310 ms   311 ms  185.60.112.158 

Trace complete.

After this spike ended. lasting about 40 min.

1 Like
192

I’ve also been getting sporadic high latency for the past week or so. In the main my latency in both home and world as reported in-game is around 30ms, however maybe every 20 mins or so I’m getting these numbers anywhere up to 400ms. Additional to this, about the same every 20 mins or so I get a big lag spike where everything just stops (in a network way) for around 3 seconds, then it all comes back immediately.

This is happening on both retail and classic, I don’t seem to have any issues on any other games. So looking on wow tech support it seems that the EU servers are at the ip addresses:
185.60.112.157
185.60.112.158
185.60.112.159

When I do a tracert to these what i’m seeing is that .159 seems to be the problematic one. When i’m getting latency in game, doing a tracert to all these address only seems to exhibit high pings to one of them, and its usually .159

Country: GB
Realm: EU - Draenor

Example tracert when im getting bad latency times in game:

159:

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     3 ms     2 ms     2 ms  100.127.0.26 
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     7 ms     5 ms     5 ms  10.100.2.65 
  7     4 ms     5 ms     *     100.127.255.244 
  8     5 ms     5 ms     5 ms  5.181.59.10 
  9     5 ms     5 ms     5 ms  hu0-1-0-2.rcr51.edi01.atlas.cogentco.com [149.6.12.57] 
 10    12 ms    12 ms    13 ms  be3751.ccr21.man01.atlas.cogentco.com [130.117.2.202] 
 11    17 ms    17 ms    18 ms  be3023.ccr52.lhr01.atlas.cogentco.com [154.54.78.93] 
 12    16 ms    18 ms    18 ms  be3488.ccr42.lon13.atlas.cogentco.com [154.54.60.13] 
 13    17 ms    19 ms     *     be2871.ccr21.lon01.atlas.cogentco.com [154.54.58.186] 
 14    17 ms    18 ms    18 ms  ldn-b3-link.ip.twelve99.net [62.115.9.28] 
 15    25 ms    16 ms     *     ldn-bb2-link.ip.twelve99.net [62.115.122.180] 
 16    26 ms    22 ms    21 ms  adm-bb2-link.ip.twelve99.net [62.115.137.235] 
 17    22 ms    23 ms    21 ms  adm-b10-link.ip.twelve99.net [62.115.120.229] 
 18    45 ms    35 ms    48 ms  blizzard-ic-348623.ip.twelve99-cust.net [62.115.178.203] 
 19   884 ms   660 ms   218 ms  ae1-br02-eqam1.as57976.net [137.221.78.35] 
 20     *        *        *     Request timed out.
 21    32 ms    35 ms    30 ms  137.221.78.47 
 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.

158:

Tracing route to 185.60.112.158 over a maximum of 30 hops

  1     2 ms     1 ms     1 ms  home [192.168.1.1]
  2     3 ms     2 ms     2 ms  100.127.0.26
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    77 ms    94 ms   125 ms  10.100.2.65
  7     6 ms     4 ms     5 ms  100.127.255.244
  8     6 ms     4 ms     4 ms  5.181.59.10
  9     7 ms     4 ms     4 ms  hu0-1-0-2.rcr51.edi01.atlas.cogentco.com [149.6.12.57]
 10    14 ms    11 ms    12 ms  be3751.ccr21.man01.atlas.cogentco.com [130.117.2.202]
 11    15 ms    15 ms    15 ms  be2174.ccr51.lhr01.atlas.cogentco.com [154.54.78.89]
 12    16 ms    18 ms    18 ms  be3487.ccr41.lon13.atlas.cogentco.com [154.54.60.5]
 13    17 ms    18 ms    18 ms  be2572.ccr21.lon02.atlas.cogentco.com [154.54.61.254]
 14     *        *        *     Request timed out.
 15    30 ms    19 ms    18 ms  ldn-bb1-link.ip.twelve99.net [62.115.138.168]
 16    24 ms    24 ms    23 ms  adm-bb1-link.ip.twelve99.net [213.155.136.99]
 17    23 ms    23 ms    23 ms  adm-b10-link.ip.twelve99.net [62.115.120.227]
 18    25 ms    25 ms    23 ms  blizzard-ic-348623.ip.twelve99-cust.net [62.115.178.203]
 19    32 ms    34 ms    34 ms  ae1-br01-eqam1.as57976.net [137.221.78.33]
 20     *        *        *     Request timed out.
 21    33 ms    33 ms    32 ms  et-0-0-31-pe01-eqam1.as57976.net [137.221.78.67]
 22    33 ms    34 ms    32 ms  137.221.66.45
 23    33 ms    34 ms    34 ms  185.60.112.158

157:

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     3 ms     2 ms     2 ms  100.127.0.26
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     6 ms     7 ms     4 ms  10.100.2.65
  7     8 ms     6 ms     5 ms  100.127.255.244
  8     6 ms     *        7 ms  5.181.59.10
  9     6 ms     6 ms     4 ms  hu0-1-0-2.rcr51.edi01.atlas.cogentco.com [149.6.12.57]
 10    15 ms    11 ms    12 ms  be3751.ccr21.man01.atlas.cogentco.com [130.117.2.202]
 11    18 ms    15 ms    15 ms  be3023.ccr52.lhr01.atlas.cogentco.com [154.54.78.93]
 12    17 ms    17 ms    34 ms  be3488.ccr42.lon13.atlas.cogentco.com [154.54.60.13]
 13    16 ms    18 ms     *     be2573.ccr21.lon02.atlas.cogentco.com [154.54.62.6]
 14     *        *        *     Request timed out.
 15    18 ms     *       18 ms  ldn-bb1-link.ip.twelve99.net [62.115.138.168]
 16    24 ms    23 ms    24 ms  adm-bb1-link.ip.twelve99.net [213.155.136.99]
 17    23 ms    23 ms    25 ms  adm-b10-link.ip.twelve99.net [62.115.120.227]
 18    24 ms    24 ms    22 ms  blizzard-ic-348623.ip.twelve99-cust.net [62.115.178.203]
 19    99 ms   231 ms     *     ae1-br02-eqam1.as57976.net [137.221.78.35]
 20     *        *        *     Request timed out.
 21    33 ms    31 ms    31 ms  et-0-0-31-pe02-eqam1.as57976.net [137.221.78.69]
 22    36 ms    34 ms    35 ms  137.221.66.47
 23    34 ms    34 ms    34 ms  185.60.112.157

In the above examples its clear that the hop ae1-br02-eqam1.as57976.net [137.221.78.35] for me is the problematic one. The EU endpoint 185.60.112.158 isnt being routed through this, rather ae1-br01-eqam1.as57976.net [137.221.78.33], so I’m wondering if during the game as you phase and travel around the connection load balances between these 3, and this is the reason for the latency coming and going.

It does seem that there have been previous tech support issues with this node as can be seen in this forum post from 2020 (inc. blue post responses): Seriously, can you fix your servers?

2 Likes
193

For me the game is mostly playable around 7-10 in the morning JST. The rest of the time it is not even responding. I havent been able to play for more than half a month now. I pay monthly to play this game. This is slowly becoming a scam.

1 Like
194

Happening for me from the UK on Argent Dawn EU right now. Running tracert I what looks like longer hops to (ae1-br01-eqld5.as57976.net [137.221.79.33]) similar to yours, but the tracert to 159 just had a lot more issues and time outs.

157

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms vodafone.broadband [192.168.1.1]
2 10 ms 9 ms 9 ms host-212-158-250-37.dslgb.com [212.158.250.37]
3 11 ms 10 ms 10 ms 63.130.172.41
4 12 ms 12 ms 12 ms lonap-ix.blizzardonline.net [5.57.81.160]
5 67 ms 219 ms 219 ms ae1-br01-eqld5.as57976.net [137.221.79.33]
6 * * * Request timed out.
7 * * * Request timed out.
8 18 ms 17 ms 17 ms 137.221.78.47
9 18 ms 18 ms 17 ms 185.60.112.157

158

Tracing route to 185.60.112.158 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms vodafone.broadband [192.168.1.1]
2 9 ms 9 ms 9 ms host-212-158-250-37.dslgb.com [212.158.250.37]
3 11 ms 10 ms 14 ms 63.130.172.41
4 12 ms 12 ms 12 ms lonap-ix.blizzardonline.net [5.57.81.160]
5 233 ms 183 ms 210 ms ae1-br01-eqld5.as57976.net [137.221.79.33]
6 * * * Request timed out.
7 * * * Request timed out.
8 17 ms 17 ms 17 ms et-0-0-31-pe01-eqam1.as57976.net [137.221.78.67]
9 18 ms 17 ms 17 ms 137.221.66.45
10 18 ms 18 ms 17 ms 185.60.112.158

159

Tracing route to 185.60.112.159 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms vodafone.broadband [192.168.1.1]
2 9 ms 10 ms 9 ms host-212-158-250-37.dslgb.com [212.158.250.37]
3 11 ms * * 63.130.172.41
4 29 ms 12 ms 12 ms lonap-ix.blizzardonline.net [5.57.81.160]
5 204 ms 219 ms 219 ms ae1-br01-eqld5.as57976.net [137.221.79.33]
6 * * * Request timed out.
7 * * * Request timed out.
8 25 ms 18 ms 17 ms 137.221.78.47
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.

195

Ok guys, let me share you what finally looks like worked for me The last thing I was missing to try. Uninstall all, retail and classic. And erase all files remaining in your system after that. I had files from classic, burning crusade and lich king in my wow folder. Erase all and start to instll all from 0. Hope this help some
EDIT____
This worked for a while, but I had lag and freezing issues again.

196

I worked perfectly for couple of hours now, until 30mins ago, now its again skyrocketing to 1800ms ++

197

As a last effort, I have now tried a complete re-install, however this hasnt worked for me. As its stands right now any critical grouped content like m+ is almost undoable with these massive lag spikes :frowning:

The really strange things is that I noticed the lag spikes particularly in cata classic but my in game latency stated 30ms on both home and world. As an example, one time I was casting the mage blink spell which is instant and I didnt see the result for about 2 seconds, but my latency was ~30ms :confused:

2 Likes
198

Tried it too. Didn’t work. Seems to be getting better in open world & in hub city. Can also attempt M+ (although still a fair bit of lag). Raid is unplayable though. Seriously it’s been like this for almost 2 weeks. I’m seeing improvements I’m trying all I can on my end. But not hearing from Blizzard support or not seeing this fixed sooner is giving me reservations about continuing my subscription.

2 Likes
199

Having the same issue for the last weeks or so. Have direct connection to pc without router. High ping / spikes during 5-6 pm ST till 8-9 pm ST. Tried to reset my UI, network adapter, checked drivers etc.

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
chb-b21-p4.ti.ru 0 809 809 0 1 40 0
msk-r1-m40-xe-2-2-6-910.ti.ru 0 809 809 0 1 21 0
178.176.191.136 0 809 809 0 1 19 3
No response from host 100 164 0 0 0 0 0
No response from host 100 164 0 0 0 0 0
No response from host 100 164 0 0 0 0 0
No response from host 100 164 0 0 0 0 0
83.169.204.78 0 809 809 34 35 83 34
netnod-ix-ge-a-sth-1500.blizzard.com 0 809 809 34 38 118 34
ae1-br01-eqsk1.as57976.net 0 809 809 50 58 909 51
et-0-0-3-br01-eqam1.as57976.net 4 696 673 50 134 4702 50
No response from host 100 164 0 0 0 0 0
et-0-0-31-pe02-eqam1.as57976.net 0 808 808 50 50 87 50
137.221.66.47 1 805 804 50 51 59 51
185.60.112.157 1 801 799 50 50 60 50
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
chb-b21-p4.ti.ru 0 781 781 0 1 37 0
msk-r1-m40-xe-2-2-6-910.ti.ru 0 781 781 0 1 22 1
178.176.191.136 0 781 781 0 1 14 8
No response from host 100 158 0 0 0 0 0
No response from host 100 158 0 0 0 0 0
No response from host 100 158 0 0 0 0 0
No response from host 100 158 0 0 0 0 0
83.169.204.82 0 781 781 33 34 51 34
netnod-ix-ge-b-sth-1500.blizzard.com 0 780 780 34 38 114 34
ae1-br01-eqsk1.as57976.net 0 781 781 50 58 873 50
et-0-0-3-br01-eqam1.as57976.net 4 668 645 50 136 4619 50
No response from host 100 158 0 0 0 0 0
137.221.78.51 0 780 780 50 50 75 50
137.221.66.45 2 739 728 50 50 57 50
185.60.112.158 0 780 780 50 50 60 50
200

ok, so I think I’ve gotten to the bottom of my issue, I’ve been testing it out for a few hours now and have so far it’s been solid locked in to ~30ms latency with no lag spikes.

After doing some research on the intermittent lack of latency stability when using IPv6, I wondered if my PC network config was set to this. I suspected this after I recently stopped using wireless in favor of a ethernet cable, and I recall Windows 11 stating its was using a high speed network connection or words to that effect.

So I checked the properties of the network connection, and it did in fact have IPv6 enabled on it, Windows 11 must have set this itself as I don’t recall setting it (or anything in the network config). Since I disabled this, I’ve had zero issues so far. I can only assume that my router isn’t configured or doesn’t “like” this more advanced protocol standard.

So this might be something to check for others too. Good luck to you all!

201

Hey Yryadorne can you please check with the IT engineers. We provided a lot of proof, my ticket got closed with automatic message.

ibb(dot)co/q0v4hRZ (You can notice the Package loss)
ibb(dot)co/48YhrC7 (for 57 IP)
ibb(dot)co/5vfX77m (for 58 IP)

The game only randomly works few hours / minutes per day on normal ping after that this happens.

From what i noticed its a peering problem of Blizzard’s partner, i even asked someone with more skills into this and he mentioned that i cannot do anything from my side / home. This is a problem from the blizzard partner for real-time traffic delivery.

Since its blizzard peering business partner none of us can do anything, but only to complain to Blizzard to change the partner or escalate the issue to them and solve it ASAP, its been 3 weeks.

1 Like
202

Have tried reinstalling and clearing out files like what was mentioned above, have tried resetting router and network settings. Nothing is working, the game is still completely unplayable with over 6000ms on average. Is there no response at all from Blizzard specifically about this issue? It’s been over two weeks now and no change

1 Like
203

Think they have this dumb system where if a blue responded in the topic they just don’t look at it at all anymore, maybe people need to create a new one but i doubt we’ll get a response there either.

Suits seem to not give a flying fk about this issue it seems.

1 Like
204

Have you tried another online game that’s not Blizzard?

I only really knew for sure it wasn’t Blizz until I downloaded GW2 and got the exact same behavior. So I know it was at my end, either ISP or in my case the IPv6 setting on my windows network connection config which should have been off as my ISP doesn’t support it.

205

Yep, I’ve been playing FFXIV and a number of other games with no problems connecting to servers in the EU and US. Only WoW seems to have any issues whatsoever. I’ve also tried with IPv6 settings on and off and there was no change at all on that unfortunately.

206

I opened another Ticket… US98777578

Getting tired of opening tickets just to be randomly closed by random bot message saying things that i already done them.

I hope they have humans who also answer to tickets

207

Update: 17 days.

2 Likes
208

only 9525 MS today and around 20% package loss…still no reply on my ticket, i guess they are in vacation

2 Likes
209

Quick update: since 8 hours ago its getting better, i had no more latency issue, now peak is around 400 ms World and 350 Home. Lets see how much it will last