Latency high since last update

Support Technical Support
1

Since the last minor update to the game, last Wednesday or Thursday or whenever it was, my latency has been around 50-70 for both home and world, so totalling 100-140. This doesn’t make the game totally unplayable but is very impactful having a delay between pressing a spell and it actually casting.

Before the recent update my latency was consistently around 15 for both world and home and was very playable.

No issues with speed test (380Mbps) or latency test (16ms) online. It’s just occurring on WoW.

Is this something Blizzard done and I just need to wait for them to rectify it in a future update or is there something I can do now?

I’m using a Mac with the M2 processor, if that is relevant.

Any help would be appreciated.

Thanks.

2

I usually have 45, but today its 300+, and on BG it’s very annoying.
Of course Blizzad will say that it’s my internet provider’s fault…

3

Here is my tracert:

Tracing route to 185.60.112.157 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     2 ms     1 ms     4 ms  57.red-81-41-220.staticip.rima-tde.net [81.41.220.57]
  4    12 ms    11 ms    11 ms  238.red-81-41-220.staticip.rima-tde.net [81.41.220.238]
  5    12 ms    12 ms    13 ms  77.red-80-58-96.staticip.rima-tde.net [80.58.96.77]
  6     *        *        *     Request timed out.
  7     *       12 ms    12 ms  50.red-80-58-96.staticip.rima-tde.net [80.58.96.50]
  8    12 ms    12 ms    12 ms  ae1-400-grtmadte1.net.telefonicaglobalsolutions.com [216.184.113.186]
  9    18 ms    22 ms    15 ms  ae-5.edge1.Madrid2.Level3.net [4.68.39.33]
 10    35 ms    32 ms    32 ms  ae1.3111.edge7.Paris1.level3.net [4.69.133.234]
 11    33 ms    33 ms    32 ms  BLIZZARD-EN.edge7.Paris1.Level3.net [213.19.199.110]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15   108 ms   106 ms   111 ms  137.221.78.49
 16   126 ms   124 ms   119 ms  137.221.66.43
 17   209 ms   206 ms   213 ms  185.60.112.157

Tracing route to 185.60.112.158 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     2 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    12 ms    12 ms    12 ms  be12-400-grtmadte2.net.telefonicaglobalsolutions.com [216.184.113.54]
  8    12 ms    12 ms     *     94.142.107.207
  9    37 ms    37 ms    37 ms  prs-bb1-link.ip.twelve99.net [213.155.131.152]
 10    36 ms    37 ms    36 ms  prs-b1-link.ip.twelve99.net [62.115.125.171]
 11    33 ms    32 ms    32 ms  blizzard-ic-348624.ip.twelve99-cust.net [62.115.178.205]
 12   173 ms   163 ms   162 ms  ae1-br02-eqpa4.as57976.net [137.221.77.35]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15    67 ms    67 ms    68 ms  137.221.78.53
 16   145 ms   148 ms   161 ms  185.60.112.158

Tracing route to 185.60.114.159 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     2 ms     1 ms     1 ms  57.red-81-41-220.staticip.rima-tde.net [81.41.220.57]
  4    13 ms    12 ms    12 ms  238.red-81-41-220.staticip.rima-tde.net [81.41.220.238]
  5    12 ms    12 ms    12 ms  77.red-80-58-96.staticip.rima-tde.net [80.58.96.77]
  6    12 ms    13 ms    12 ms  46.red-80-58-96.staticip.rima-tde.net [80.58.96.46]
  7     *        *        *     Request timed out.
  8    13 ms    12 ms    12 ms  be12-400-grtmadte2.net.telefonicaglobalsolutions.com [216.184.113.54]
  9    12 ms    12 ms    12 ms  94.142.107.207
 10     *        *        *     Request timed out.
 11    34 ms    34 ms    34 ms  prs-b1-link.ip.twelve99.net [62.115.125.167]
 12    30 ms    31 ms    30 ms  blizzard-ic-348624.ip.twelve99-cust.net [62.115.178.205]
 13    56 ms   216 ms   139 ms  ae1-br01-eqpa4.as57976.net [137.221.77.33]
 14    31 ms    30 ms    30 ms  et-0-0-0-pe03-eqpa4.as57976.net [137.221.77.55]
 15    30 ms    30 ms    30 ms  185.60.114.159

Trace complete.

Is that 137.221.77.33 Blizzard’s address? In tracert it goes after blizzard-ic-whatever…net

4

Did you guys find any update to this? Mine is usually around 70-80 and lately its never below 200.

5

You may post results of your traceroute here too, maybe some Blizzard’s employee will read it :–)

6

I login today and the latency is 400ms… It used to be 90ms.

Tracing route to 185.60.112.158 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.100.1
  2     3 ms     3 ms     3 ms  185.76.136.6
  3     4 ms     6 ms     4 ms  10.188.205.6
  4    63 ms    63 ms    63 ms  10.188.199.11
  5   130 ms   130 ms     *     80.249.208.83
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8   130 ms   130 ms   130 ms  137.221.78.47
  9   131 ms   134 ms   130 ms  137.221.66.41
 10   130 ms   130 ms   130 ms  185.60.112.158
7

Ive been having the same issue, since last Wednesday my latency seems to jump at times to over 200 or 300, this is effecting my gameplay as I’m unable to do keys because i have a 2 or 3 second delay on all my spells.

8

Same issue here. My latency is usually around 15 - 30 ms steady, now it fluctuates between 200 - 3k+. Even at ~200ms the skills take 1 or 2 seconds to launch, unplayable. Everything else I test outside the game works perfect (1ms - 15ms).

Powerful desktop PC, no addons, no VPN, tested with wire and wifi, closing all apps and battle.net after launching the game, no other apps consuming bandwith in the whole house, already run the “ipconfig /flushdns” command, restarted router and pc, disabled antivirus, no Windows/apps updates in progress … the strangest thing is that my girlfriend is playing wow here in the same network without any lag so I’m pretty sure is a problem in my WoW.

These are my traceroutes:

C:\Users\Jose>tracert 185.60.112.157

Tracing route to 185.60.112.157 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        2 ms     2 ms  192.168.144.1
  3     2 ms     2 ms     2 ms  49.red-81-46-65.customer.static.ccgg.telefonica.net [81.46.65.49]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        2 ms     2 ms  50.red-80-58-96.staticip.rima-tde.net [80.58.96.50]
  7     4 ms     2 ms     3 ms  ae1-400-grtmadte1.net.telefonicaglobalsolutions.com [216.184.113.186]
  8     2 ms     3 ms     3 ms  ae-5.edge1.Madrid2.Level3.net [4.68.39.33]
  9    19 ms    19 ms    22 ms  ae1.3111.edge7.Paris1.level3.net [4.69.133.234]
 10    19 ms    19 ms    19 ms  BLIZZARD-EN.edge7.Paris1.Level3.net [213.19.199.110]
 11   182 ms   172 ms   169 ms  ae1-br02-eqpa4.as57976.net [137.221.77.35]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   188 ms     *      179 ms  137.221.78.55
 15   120 ms   117 ms   128 ms  185.60.112.157

Trace complete.

C:\Users\Jose>tracert 185.60.112.158

Tracing route to 185.60.112.158 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        1 ms     1 ms  192.168.144.1
  3     *        *        *     Request timed out.
  4     2 ms     2 ms     2 ms  98.red-81-46-65.customer.static.ccgg.telefonica.net [81.46.65.98]
  5     2 ms     2 ms     2 ms  61.red-80-58-96.staticip.rima-tde.net [80.58.96.61]
  6     3 ms     2 ms     2 ms  46.red-80-58-96.staticip.rima-tde.net [80.58.96.46]
  7     *        *        2 ms  2.red-81-46-0.customer.static.ccgg.telefonica.net [81.46.0.2]
  8    55 ms     6 ms     3 ms  ae1-400-grtmadte1.net.telefonicaglobalsolutions.com [216.184.113.186]
  9     3 ms     3 ms     3 ms  ae-5.edge1.Madrid2.Level3.net [4.68.39.33]
 10    22 ms    21 ms    19 ms  ae1.3111.edge7.Paris1.level3.net [4.69.133.234]
 11    19 ms    19 ms    19 ms  BLIZZARD-EN.edge7.Paris1.Level3.net [213.19.199.110]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15   188 ms   186 ms   188 ms  137.221.78.51
 16   133 ms   132 ms   133 ms  137.221.66.45
 17   197 ms   195 ms   196 ms  185.60.112.158

Trace complete.

C:\Users\Jose>tracert 185.60.114.159

Tracing route to 185.60.114.159 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        2 ms  192.168.144.1
  3     *        *        2 ms  49.red-81-46-65.customer.static.ccgg.telefonica.net [81.46.65.49]
  4     2 ms     3 ms     2 ms  106.red-81-46-65.customer.static.ccgg.telefonica.net [81.46.65.106]
  5     2 ms     2 ms     2 ms  61.red-80-58-96.staticip.rima-tde.net [80.58.96.61]
  6     3 ms     3 ms     2 ms  46.red-80-58-96.staticip.rima-tde.net [80.58.96.46]
  7     *        *        2 ms  2.red-81-46-0.customer.static.ccgg.telefonica.net [81.46.0.2]
  8     3 ms     2 ms     2 ms  ae1-400-grtmadte1.net.telefonicaglobalsolutions.com [216.184.113.186]
  9     8 ms    25 ms    13 ms  ae-5.edge1.Madrid2.Level3.net [4.68.39.33]
 10    19 ms    20 ms    25 ms  ae1.3111.edge7.Paris1.level3.net [4.69.133.234]
 11    23 ms    19 ms    19 ms  BLIZZARD-EN.edge7.Paris1.Level3.net [213.19.199.110]
 12  1224 ms  1319 ms   879 ms  ae1-br02-eqpa4.as57976.net [137.221.77.35]
 13    23 ms    22 ms    23 ms  bond0-vs01-eqpa4.as57976.net [137.221.77.57]
 14    20 ms    19 ms    19 ms  185.60.114.159

Trace complete.
9

Same here , usually 20-30 of latency… now 150-200, the results of tracert, pathping and winmtr here:


TRACERT 185.60.112.157

Traza a 185.60.112.157 sobre caminos de 30 saltos como máximo.

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     1 ms     1 ms     1 ms  79.red-81-46-37.customer.static.ccgg.telefonica.net [81.46.37.79]
  3     3 ms     3 ms     3 ms  165.red-81-46-68.customer.static.ccgg.telefonica.net [81.46.68.165]
  4     *        *        *     Tiempo de espera agotado para esta solicitud.
  5     *        *        *     Tiempo de espera agotado para esta solicitud.
  6     *        *        *     Tiempo de espera agotado para esta solicitud.
  7    27 ms    20 ms    16 ms  ae1-400-grtmadte1.net.telefonicaglobalsolutions.com [216.184.113.186]
  8    18 ms    18 ms    16 ms  ae-5.edge1.Madrid2.Level3.net [4.68.39.33]
  9    31 ms    31 ms    31 ms  ae1.3111.edge7.Paris1.level3.net [4.69.133.234]
 10    45 ms    33 ms    33 ms  BLIZZARD-EN.edge7.Paris1.Level3.net [213.19.199.110]
 11     *        *        *     Tiempo de espera agotado para esta solicitud.
 12     *        *        *     Tiempo de espera agotado para esta solicitud.
 13     *        *        *     Tiempo de espera agotado para esta solicitud.
 14   184 ms   179 ms   200 ms  137.221.78.53
 15   211 ms   193 ms   187 ms  137.221.66.47
 16   198 ms   209 ms   211 ms  185.60.112.157
---------------------------------------------------------------------------------------------------------------------------------

PATHPING

Seguimiento de ruta a 185.60.112.157 sobre un máximo de 30 saltos.

  0  Jose-9700k [192.168.1.39] 
  1  192.168.1.1 
  2  79.red-81-46-37.customer.static.ccgg.telefonica.net [81.46.37.79] 
  3  165.red-81-46-68.customer.static.ccgg.telefonica.net [81.46.68.165] 
  4     *        *        *     
Procesamiento de estadísticas durante 75 segundos...
              Origen hasta aquí   Este Nodo/Vínculo
Salto  RTT    Perdido/Enviado = Pct  Perdido/Enviado = Pct  Dirección
  0                                           Jose-9700k [192.168.1.39] 
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1 
                              100/ 100 =100%   |
  2  ---     100/ 100 =100%     0/ 100 =  0%  79.red-81-46-37.customer.static.ccgg.telefonica.net [81.46.37.79] 
                                0/ 100 =  0%   |
  3  ---     100/ 100 =100%     0/ 100 =  0%  165.red-81-46-68.customer.static.ccgg.telefonica.net [81.46.68.165] 

Traza completa.

---------------------------------------------------------------------------------------------------------------------------------
WINMTR

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                             192.168.1.1 -    0 |   95 |   95 |    0 |    0 |    4 |    0 |

|79.red-81-46-37.customer.static.ccgg.telefonica.net -    0 |   95 |   95 |    1 |    3 |   18 |    2 |

|165.red-81-46-68.customer.static.ccgg.telefonica.net -    0 |   95 |   95 |    3 |    5 |   64 |    4 |

|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |

|ae1-400-grtmadte1.net.telefonicaglobalsolutions.com -    0 |   95 |   95 |   16 |   19 |   42 |   17 |

|           ae-5.edge1.Madrid2.Level3.net -    0 |   95 |   95 |   15 |   19 |   51 |   22 |

|        ae1.3111.edge7.Paris1.level3.net -   12 |   67 |   59 |   31 |   35 |   49 |   35 |

|     BLIZZARD-EN.edge7.Paris1.Level3.net -    0 |   95 |   95 |   33 |   37 |   96 |   33 |

|              ae1-br02-eqpa4.as57976.net -    5 |   81 |   77 |  131 |  155 |  249 |  159 |

|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |

|                           137.221.78.53 -    5 |   80 |   76 |  142 |  197 |  222 |  205 |

|                           137.221.66.47 -    2 |   92 |   91 |  107 |  193 |  215 |  196 |

|                          185.60.112.157 -    2 |   92 |   91 |   80 |  194 |  215 |  198 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider



Thanks in advance.
10

Same, I’ve had problems all week. normally around 30-50 now playing a bg and its 300+. Unplayable

11

Had this same issue 1 week ago. Now again, still on the same HOP. ZzZ

12

Well it was driving me crazy not knowing if it’s on my end.
Raised a ticket for this, last week. Reopened
Let’s see.

13

Same here, usually have around 180 ms ( yes this is normal, yay for no local servers ) but since yesterday my MS go from 300 to anything past 10k. Valdrakkan is nearly impossible to do anything in, once you leave the city it seems to calm down, but overall never drops below 800 at the best of times, even during raid last night.

My tracert times out after 4 hops, so locally all is fine, it’s once it leaves my country.

14

Just adding my issues to the list, it’s super high world ms, usually 4 figures now which renders it unplayable, especially in the Superbloom. The other day I was hanging on with an world ms of over 4K.

I’ve noticed this since I’ve switched up to a new PC just before Christmas. I am running the BNet Scan/Repair to see if something didn’t transfer right, but my partner who plays right next to me often has no issues, so I don’t think it’s either our VPN or network provider. UK here, using a UK based VPN occasionally to see if it helps improve it…

15

Just built a new PC, every other game apart from wow play flawless. My net is top notch but I get random times where my game is 300+ ping. I rubber band in bg’s and makes me just want to close down the game. If I don’t see a fix for this soon I will be getting a refund for war within. I quit another popular mmorpg due to lag and unplayable times.

16

have you thought of that the problem could be on your pc?
maybe your settings for wow is too high which cause the issue.

17

It’s irrelevant in this particular case - there’s a faulty node (been for a good few weeks) that Blizzard ignores as it involves a small part of the playerbase. There are a few threads on the issue too. Here’s the node in question:

https://i.imgur.com/m4ipPPk.png
18

no it isnt irrelevant since the issue isnt on blizzard’s side but good luck trying to figure it out.

19

Flushing DNS is a possible method for resolving many internet connectivity issues

20

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