Latency (Home) went from 27 to 160 (over 14h now)

Support Technical Support
1

Greetings
Ever since i can remember, ive always had 27-30ms in wow.
Yesterday evening i took a short break, turned off PC, came back after around 4 hours.
Right from the start after logging in i immediately felt a delay when killing mobs / moving items in the inventory.

I now have 155-159 MS (Home)

I have done the following, disabled all addons, checked with different toons on different realms, disabled my firewall, restarted router, checked other games aswell
(and its all fine there, runs at 30 ping like usual)

Also checking my speed from a site which also gives me exactly same results as usual, no issue there.

So what in gods name is happening?
It’s been like this since yesterday now, im up at around 14hours with 155-160 MS in Wow Classic Wotlk, playing on EU (Giantstalker) and like i already said, tried Realms with other toons such as Mirage Raceway, same there, 160ish ms (home)

If it dosent have anything to do with addons, or the realm itself, or my bandwidth speed, or even other games.

What could it possibly be?

Im alittle worried to be honest, because no one seems to have this issue when i ask guild/chat etc.

Only one other person in this reddit thread has responded with same issue since yesterday, i dont feel convinced that it’s on blizzards side tho.

Anyone else have this issue and wanna point that out?

What happend within those 4 hours i was away yesterday?
This is insane, i check the MS frequently, and i always have 27ms, and for as long as i can remember, 2018 when classic was brought up to begin with, this is actually the first time ive seen this happening.
And based on the attempts of conditions, ive got nothing left to try.

Any one got same or atleast familiar issue and got their resolved somehow?
Also created a reddit of this issue.

/Best Regards

2

Generally latency issues are not to do with Blizzard - if they were, the fora would be in meltdown over it.

Some things for you to try that you may not have already done (I did read what you’ve already tried).

  1. Flush the DNS on your computer. You can see how to do that here:
  1. I know you’ve disabled your addons, but I’d try an interface reset as well. You can see how to do that here:

With a router restart, I’d try leaving it powered off for at least 30 minutes if you haven’t done this already. If you have a seperate box between the router and your broadband line (some people do) remember that also needs to be turned off.

I assume you have run a system scan to eliminate any malware causing any issues ?

3

Run a traceroute and that will hopefully reveal where the delay is coming from. Probably just a temporary internet problem (either hardware failure or something has been configured wrongly) between you and the WoW servers and it’ll sort itself out in a day or two.

Details on running the traceroute here:

4

Well,
It does seem accurate right now, because it show 155-160 which is what ive currently got.

I tested all 3, and the results are the following.

185.60.112.157

1    <1 ms    <1 ms    <1 ms  OpenWrt.lan [192.168.1.1] 
2     4 ms     4 ms     4 ms  gw1-no160.tbcn.telia. com [78.70.64.1] 
3     *        *        *     Request timed out.
4     6 ms     6 ms     *     m-b-c1-link.se.telia.n et [81.228.89.16] 
5     6 ms     6 ms     6 ms  m-b-peer1-link.se.telia. net [81.228.84.95] 
6     7 ms     7 ms     7 ms  kbn-b1-link.ip.twelve99. net [62.115.123.158] 
7     9 ms    10 ms    10 ms  kbn-bb2-link.ip.twelve99. net [62.115.138.112] 
8     *       12 ms    12 ms  hbg-bb2-link.ip.twelve99. net [62.115.135.227] 
9    19 ms    19 ms    18 ms  adm-bb4-link.ip.twelve99. net [62.115.127.89] 
10    18 ms    18 ms    18 ms  adm-b10-link.ip.twelve99. net [62.115.120.229] 
11    19 ms    19 ms    19 ms  blizzard-ic348623-adm-b10.ip.twelve99-cust. net [62.115.178.203] 
12   151 ms   151 ms   159 ms  ae1-br01-eqam1.as57976. net [137.221.78.33] 
13     *        *        *     Request timed out.
14   153 ms   153 ms   153 ms  137.221.78.49 
15   151 ms   151 ms   151 ms  137.221.66.43 
16   151 ms   151 ms   151 ms  185.60.112.157 

Trace complete.

185.60.112.158

  1    <1 ms    <1 ms    <1 ms  OpenWrt.lan [192.168.1.1] 
  2     4 ms     4 ms     4 ms  gw1-no160.tbcn.telia.com [78.70.64.1] 
  3     *        *        *     Request timed out.
  4     *        *        6 ms  m-b-c1-link.se.telia.net [81.228.89.16] 
  5     6 ms     6 ms     6 ms  m-b-peer1-link.se.telia.net [81.228.84.95] 
  6     7 ms     7 ms     7 ms  kbn-b1-link.ip.twelve99.net [62.115.123.158] 
  7    10 ms    10 ms    10 ms  kbn-bb1-link.ip.twelve99.net [62.115.143.6] 
  8    14 ms    13 ms    13 ms  hbg-bb3-link.ip.twelve99.net [62.115.134.77] 
  9    19 ms    19 ms    19 ms  adm-bb1-link.ip.twelve99.net [80.91.252.42] 
 10    19 ms    19 ms    19 ms  adm-b10-link.ip.twelve99.net [62.115.120.227] 
 11    20 ms    19 ms    19 ms  blizzard-ic348623-adm-b10.ip.twelve99-cust.net [62.115.178.203] 
 12   152 ms   151 ms   152 ms  ae1-br01-eqam1.as57976.net [137.221.78.33] 
 13     *        *        *     Request timed out.
 14   154 ms   154 ms   154 ms  137.221.78.49 
 15   154 ms   154 ms   154 ms  185.60.112.158 

Trace complete.

185.60.114.159

  1    <1 ms    <1 ms    <1 ms  OpenWrt.lan [192.168.1.1] 
  2     4 ms     4 ms     4 ms  gw1-no160.tbcn.telia.com [78.70.64.1] 
  3     7 ms     7 ms     *     hs-b-c1-link.se.telia.net [81.228.93.6] 
  4     *        *        7 ms  ld-h-c1-link.se.telia.net [81.228.95.42] 
  5     7 ms     7 ms     7 ms  m-b-peer1-link.se.telia.net [81.228.86.13] 
  6     8 ms     8 ms     8 ms  kbn-b1-link.ip.twelve99.net [62.115.123.158] 
  7    10 ms    10 ms    10 ms  kbn-bb1-link.ip.twelve99.net [62.115.143.6] 
  8    14 ms    14 ms    14 ms  hbg-bb3-link.ip.twelve99.net [62.115.134.77] 
  9    19 ms    19 ms    19 ms  adm-bb1-link.ip.twelve99.net [80.91.252.42] 
 10    19 ms    19 ms    19 ms  adm-b10-link.ip.twelve99.net [62.115.120.227] 
 11    20 ms    20 ms    20 ms  blizzard-ic348623-adm-b10.ip.twelve99-cust.net [62.115.178.203] 
 12     *     3928 ms  2559 ms  ae1-br02-eqam1.as57976.net [137.221.78.35] 
 13   210 ms   179 ms   159 ms  et-0-0-3-br02-eqpa4.as57976.net [137.221.65.92] 
 14   159 ms   159 ms   159 ms  et-0-0-1-pe04-eqpa4.as57976.net [137.221.77.53] 
 15   159 ms   159 ms   159 ms  137.221.66.39 
 16   157 ms   157 ms   156 ms  185.60.114.159 

Trace complete.
6

Same here. Also EU.

  1    <1 ms    <1 ms <1 ms 192.168.1.1
  2     2 ms     5 ms     2 ms  132.red-81-46-38.customer.static.ccgg.telefonica.net [81.46.38.132]
  3     3 ms     2 ms     6 ms  5.red-81-46-34.customer.static.ccgg.telefonica.net [81.46.34.5]
  4     3 ms     3 ms     3 ms  137.red-81-46-34.customer.static.ccgg.telefonica.net [81.46.34.137]
  5     3 ms     3 ms     3 ms  46.red-80-58-81.staticip.rima-tde.net [80.58.81.46]
  6     3 ms     3 ms     3 ms  213.140.50.204
  7     *       11 ms    11 ms  176.52.248.189
  8    12 ms    11 ms    14 ms  213.140.36.146
  9    37 ms    11 ms    12 ms  ae-5.edge1.Madrid2.Level3.net [4.68.39.33]
 10    34 ms    43 ms    28 ms  ae1.3111.edge7.Paris1.level3.net [4.69.133.234]
 11    29 ms    28 ms    28 ms  BLIZZARD-EN.edge7.Paris1.Level3.net [213.19.199.110]
 12   170 ms   170 ms   170 ms  ae1-br01-eqpa4.as57976.net [137.221.77.33]
 13   187 ms   187 ms   189 ms  et-0-0-0-pe02-eqpa4.as57976.net [137.221.77.81]
 14   168 ms   168 ms   169 ms  137.221.66.35
 15   171 ms   171 ms   172 ms  185.60.114.159
7

Same for me since last night, EU-Gehennas

8

Really??? Haha im sorry but i cant help finding this positive.
This is definitely not just me then. Im crossing my fingers that it’d get fixed after the maintenance tomorrow.

9

Yeah im right there with you on that. I checked everything last night and even ordered a new ethernet cable since mine was gettin old. The joy when i saw this post is weird but yeah so much nicer to know more have the same tbh.

10

Not sure what happened with the .ar address before but I’m getting the expected results now:

1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.2.1]
2     *        *        *     Request timed out.
3     8 ms    17 ms    12 ms  renf-core-2a-xe-1106-0.network.virginmedia.net 
[62.252.128.217]
4     *        *        *     Request timed out.
5    21 ms    21 ms    27 ms  86.85-254-62.static.virginmediabusiness.co.uk 
[62.254.85.86]
6     *        *        *     Request timed out.
7    38 ms    30 ms    21 ms  uk-lon03a-ri2-ae-2-0.aorta.net [84.116.135.46]
8    38 ms    81 ms    27 ms  213.46.175.138
9   167 ms   162 ms   220 ms  ae1-br01-eqld5.as57976.net [137.221.79.33]
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12    49 ms    26 ms    27 ms  137.221.78.53
13    26 ms    26 ms    27 ms  137.221.66.47
14    26 ms    26 ms    25 ms  185.60.112.157

So you’re taking a slightly different route at the blizzard end to reach the final IP and your lag is appearing after you hit the first blizzard server.

11

Same issue here, exactly the same u explained. Nord VPN fixed tbe issue for me for now.

12

exactly the same issue here, in the range of 150-160 latency instead of the 13-22 i usually have

13

Yeah, ive never ever used a VPN before, but if the maintenance tomorrow hasent fixed this nonsense, im also gonna get it, either expressvpn, nord or freedome.

14

arccai does your latency stay at 150-160 at all times like mine does? or does it move up and down

15

It stays at 155-160 all times, jumping between those numbers. Ever since yesterday evening, and i’ve had 27 ms everyday since 2018 :stuck_out_tongue:

UPDATE, its back to normal everyone! :smiley: it lasted exactly 24 hours haha :slight_smile:
Lets hope that never happens again for another 5 years or so :smiley:

16

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