High latency every evening

Support Technical Support
1

Hello. So for the last few days I’m experiencing latency issues every evening, ranging from “200-300ms and occasional freeze” to “literally unplayable 7-25k ms (whilst still not timing out from the server somehow)”. The latter only happened last week though, and it seemed to start instantly but also end instantly - sometimes 5 minutes, sometimes 30 minutes, and on the 23rd August it was a whole night. Now it just starts to be laggy and freezy at evenings, making gameplay very frustrating but possible.

Today is one of those days where it’s just frustrating. It seems that this problem only happens with the WoW server and nothing else - even the web services of the game are fine. Below are tracerts to the servers that the game process actually connects to (as taken from the resource monitor, i.e. imgur com/P3QQPHL.png), tracerts to the servers that the “how to tracert” support article mentions (the 185.60.114.159 one actually lags too, so maybe it’s related!), and the output from the Looking Glass tool (I play on EU-Tarren Mill). Not posting the pathping ones since they all came out like imgur com/WY1iPrg.png and I don’t think that’s informative. (Sorry for the scuffed links, the forum won’t let me post but it’s just imgur ones so it’s pretty safe…)

Tracert’s to the servers WoW.exe is connected to:

Tracing route to 37.244.36.190 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     1 ms    <1 ms    <1 ms  asr-1002-b2.yarnet.ru [212.232.63.64]
  4     2 ms     3 ms     2 ms  78.25.83.81
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    25 ms    24 ms    25 ms  83.169.204.144
  9    25 ms    25 ms    25 ms  netnod-ix-ge-a-sth-1500.blizzard.com [194.68.123.6]
 10   157 ms   157 ms   156 ms  ae1-br01-eqsk1.as57976.net [137.221.86.33]
 11   157 ms     *      157 ms  et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
 12   155 ms   153 ms   152 ms  et-0-0-29-br02-eqam1.as57976.net [137.221.65.33]
 13    53 ms    52 ms    53 ms  et-0-0-3-br02-eqpa4.as57976.net [137.221.65.92] 
 14   158 ms   157 ms   157 ms  be2-pe01-eqpa4.as57976.net [137.221.77.71]
 15   156 ms   156 ms   155 ms  137.221.66.33
 16   157 ms   156 ms   157 ms  185.60.115.155
 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.

–

Tracing route to 37.244.28.103 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     1 ms     1 ms     1 ms  asr-1002-b2.yarnet.ru [212.232.63.64]
  4     2 ms     2 ms     1 ms  78.25.83.81
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    27 ms    26 ms    26 ms  83.169.204.82
  9    26 ms    26 ms    26 ms  netnod-ix-ge-b-sth-1500.blizzard.com [194.68.128.6]
 10    54 ms    48 ms    45 ms  ae1-br01-eqsk1.as57976.net [137.221.86.33]
 11    45 ms    45 ms    53 ms  et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
 12    46 ms    67 ms    45 ms  et-0-0-31-pe02-eqam1.as57976.net [137.221.78.69]
 13    50 ms    49 ms    51 ms  137.221.66.47
 14    48 ms    47 ms    48 ms  185.60.114.173
 15    46 ms    44 ms    46 ms  37.244.28.103

–

Tracing route to 37.244.36.191 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     1 ms     1 ms     1 ms  asr-1002-b2.yarnet.ru [212.232.63.64]
  4     1 ms     2 ms     1 ms  78.25.83.81
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    25 ms    24 ms    24 ms  83.169.204.144
  9    27 ms    31 ms    25 ms  netnod-ix-ge-b-sth-1500.blizzard.com [194.68.128.6]
 10   157 ms   157 ms   162 ms  ae1-br01-eqsk1.as57976.net [137.221.86.33]
 11   159 ms     *      157 ms  et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
 12     *      152 ms   122 ms  et-0-0-29-br02-eqam1.as57976.net [137.221.65.33]
 13    53 ms    53 ms    54 ms  et-0-0-3-br02-eqpa4.as57976.net [137.221.65.92] 
 14    60 ms    60 ms    60 ms  be2-pe02-eqpa4.as57976.net [137.221.77.73]
 15    60 ms    60 ms    60 ms  137.221.66.37
 16    54 ms    54 ms    54 ms  185.60.115.149
 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.

–

Tracert’s to the servers listed in the “how to tracert/pathping” articles:

Tracing route to 185.60.114.159 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     1 ms     1 ms     1 ms  asr-1002-b2.yarnet.ru [212.232.63.64]
  4     2 ms     2 ms     3 ms  78.25.83.81
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    24 ms    24 ms    24 ms  83.169.204.144
  9    25 ms    25 ms    26 ms  netnod-ix-ge-a-sth-1500.blizzard.com [194.68.123.6]
 10    59 ms    59 ms    59 ms  ae1-br01-eqsk1.as57976.net [137.221.86.33]
 11   145 ms   157 ms   157 ms  et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
 12   154 ms   152 ms   152 ms  et-0-0-29-br02-eqam1.as57976.net [137.221.65.33]
 13   107 ms    74 ms    66 ms  et-0-0-3-br02-eqpa4.as57976.net [137.221.65.92] 
 14   157 ms   157 ms   158 ms  be2-pe01-eqpa4.as57976.net [137.221.77.71]
 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.

–

Tracing route to 185.60.112.158 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     1 ms     1 ms     1 ms  asr-1002-b2.yarnet.ru [212.232.63.64]
  4     1 ms     1 ms     2 ms  78.25.83.81
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    27 ms    28 ms    26 ms  83.169.204.146
  9    26 ms    26 ms    26 ms  netnod-ix-ge-a-sth-1500.blizzard.com [194.68.123.6]
 10    45 ms    45 ms    48 ms  ae1-br01-eqsk1.as57976.net [137.221.86.33]
 11    45 ms    44 ms    44 ms  et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
 12    45 ms    48 ms    46 ms  et-0-0-31-pe01-eqam1.as57976.net [137.221.78.67]
 13    45 ms    45 ms    46 ms  185.60.112.158

–

Tracing route to 185.60.112.157 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     1 ms     1 ms    <1 ms  asr-1002-b2.yarnet.ru [212.232.63.64]
  4     *        2 ms     2 ms  78.25.83.81
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    24 ms    24 ms    25 ms  83.169.204.144
  9    44 ms    26 ms    25 ms  netnod-ix-ge-b-sth-1500.blizzard.com [194.68.128.6]
 10    44 ms    44 ms    44 ms  ae1-br01-eqsk1.as57976.net [137.221.86.33]
 11    44 ms    44 ms    44 ms  et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
 12    44 ms    44 ms    44 ms  et-0-0-31-pe01-eqam1.as57976.net [137.221.78.67]
 13    44 ms    44 ms    44 ms  185.60.112.157

–

Output from the Looking Glass tool:

TRACEROUTE:
traceroute to 212.232.60.105 (212.232.60.105), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.386 ms  0.386 ms  0.389 ms
 2  37.244.24.130 (37.244.24.130)  0.541 ms  0.613 ms  0.666 ms
 3  Blizzard Blizzard  1.374 ms  1.452 ms  1.504 ms
 4  137.221.66.40 (137.221.66.40)  1.267 ms  1.267 ms  1.642 ms
 5  137.221.78.70 (137.221.78.70)  1.153 ms  1.187 ms  1.190 ms
 6  137.221.78.34 (137.221.78.34)  1.225 ms  2.006 ms  1.977 ms
 7  80.249.210.177 (80.249.210.177)  7.175 ms  8.387 ms  8.371 ms
 8  ysl06.ysl24.transtelecom.net (188.43.6.118)  55.458 ms  56.867 ms  56.883 ms
 9  Yarnet-gw.transtelecom.net (188.43.6.113)  55.158 ms  55.188 ms  55.188 ms
10  asr-1002-b2.yarnet.ru (212.232.63.64)  47.645 ms  47.658 ms  47.641 ms
11  ppp-vpdn-212.232.60.105.yarnet.ru (212.232.60.105)  49.510 ms  49.143 ms  49.123 ms


25/08/2019 18:06:18 UTC
--------------------

TRACEROUTE:
traceroute to 212.232.60.105 (212.232.60.105), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.333 ms  0.329 ms  0.330 ms
 2  37.244.24.130 (37.244.24.130)  0.558 ms  0.652 ms  0.774 ms
 3  Blizzard Blizzard  1.927 ms  1.972 ms  1.978 ms
 4  137.221.66.40 (137.221.66.40)  1.337 ms  1.360 ms  1.566 ms
 5  137.221.78.70 (137.221.78.70)  1.168 ms  1.190 ms  1.206 ms
 6  137.221.78.34 (137.221.78.34)  35.508 ms  33.752 ms  33.712 ms
 7  80.249.210.177 (80.249.210.177)  7.134 ms  7.345 ms  7.322 ms
 8  ysl06.ysl24.transtelecom.net (188.43.6.118)  55.297 ms  55.567 ms  55.588 ms
 9  Yarnet-gw.transtelecom.net (188.43.6.113)  55.148 ms  55.164 ms  55.163 ms
10  asr-1002-b2.yarnet.ru (212.232.63.64)  47.571 ms  47.694 ms  47.732 ms
11  ppp-vpdn-212.232.60.105.yarnet.ru (212.232.60.105)  49.261 ms  48.946 ms  48.909 ms


25/08/2019 18:06:18 UTC
--------------------

TRACEROUTE:
traceroute to 212.232.60.105 (212.232.60.105), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.347 ms  0.336 ms  0.336 ms
 2  37.244.25.2 (37.244.25.2)  1.155 ms  1.168 ms  1.169 ms
 3  Blizzard Blizzard  1.251 ms  1.251 ms  1.269 ms
 4  137.221.66.34 (137.221.66.34)  1.168 ms  1.197 ms  1.206 ms
 5  137.221.77.70 (137.221.77.70)  7.540 ms  7.562 ms  7.564 ms
 6  137.221.65.19 (137.221.65.19)  10.335 ms  8.997 ms  8.951 ms
 7  137.221.79.34 (137.221.79.34)  7.578 ms  7.582 ms  7.565 ms
 8  lnn11-ge500.501.transtelecom.net (195.66.224.212)  127.698 ms  127.743 ms  127.107 ms
 9  ysl06.ysl24.transtelecom.net (188.43.6.118)  162.472 ms  162.674 ms  162.771 ms
10  * Yarnet-gw.transtelecom.net (188.43.6.113)  163.018 ms  162.995 ms
11  asr-1002-b2.yarnet.ru (212.232.63.64)  157.109 ms  157.161 ms  157.227 ms
12  ppp-vpdn-212.232.60.105.yarnet.ru (212.232.60.105)  157.956 ms  157.949 ms  157.924 ms


25/08/2019 18:06:20 UTC
--------------------

TRACEROUTE:
traceroute to 212.232.60.105 (212.232.60.105), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.388 ms  0.386 ms  0.388 ms
 2  37.244.25.2 (37.244.25.2)  1.383 ms  1.406 ms  1.412 ms
 3  Blizzard Blizzard  1.515 ms  1.537 ms  1.607 ms
 4  137.221.66.34 (137.221.66.34)  1.356 ms  1.378 ms  1.381 ms
 5  137.221.77.70 (137.221.77.70)  7.765 ms  7.791 ms  7.797 ms
 6  137.221.65.19 (137.221.65.19)  7.563 ms  7.643 ms  7.618 ms
 7  137.221.79.34 (137.221.79.34)  7.683 ms  7.702 ms  7.688 ms
 8  lnn11-ge500.501.transtelecom.net (195.66.224.212)  116.460 ms  116.464 ms  116.464 ms
 9  ysl06.ysl24.transtelecom.net (188.43.6.118)  162.597 ms  162.483 ms  162.583 ms
10  Yarnet-gw.transtelecom.net (188.43.6.113)  163.073 ms  163.236 ms *
11  * asr-1002-b2.yarnet.ru (212.232.63.64)  157.099 ms  157.059 ms
12  ppp-vpdn-212.232.60.105.yarnet.ru (212.232.60.105)  157.697 ms  157.731 ms  157.723 ms


25/08/2019 18:06:23 UTC
--------------------

MTR:
Start: Sun Aug 25 18:06:18 2019 Blizzard  1.|-- Blizzard                             0.0%    10    0.3   0.3   0.3   0.4   0.0
  2.|-- 37.244.24.130                             0.0%    10    0.5   0.5   0.5   0.7   0.0
  3.|-- Blizzard                           0.0%    10    1.4   1.4   1.3   1.6   0.0
  4.|-- 137.221.66.40                             0.0%    10    1.4   1.2   1.1   1.4   0.0
  5.|-- 137.221.78.70                             0.0%    10    1.1   1.1   1.0   1.2   0.0
  6.|-- 137.221.78.34                             0.0%    10    1.3  13.4   1.2  55.8  21.2
  7.|-- 80.249.210.177                            0.0%    10    7.4   7.5   7.2   8.5   0.0
  8.|-- ysl06.ysl24.transtelecom.net              0.0%    10   55.8  55.9  55.2  58.1   0.7
  9.|-- Yarnet-gw.transtelecom.net                0.0%    10   55.3  55.3  55.1  55.6   0.0
 10.|-- asr-1002-b2.yarnet.ru                     0.0%    10   48.0  47.7  47.6  48.0   0.0
 11.|-- ppp-vpdn-212.232.60.105.yarnet.ru         0.0%    10   49.1  49.1  49.0  49.4   0.0


25/08/2019 18:06:18 UTC
--------------------

MTR:
Start: Sun Aug 25 18:06:18 2019 Blizzard  1.|-- Blizzard                             0.0%    10    0.4   0.4   0.3   0.6   0.0
  2.|-- 37.244.24.130                             0.0%    10    0.6   0.6   0.5   1.1   0.0
  3.|-- Blizzard                           0.0%    10    1.7   1.6   1.2   2.4   0.0
  4.|-- 137.221.66.40                             0.0%    10    1.4   3.7   1.1  25.9   7.8
  5.|-- 137.221.78.70                             0.0%    10    1.0   2.0   0.9  11.3   3.2
  6.|-- 137.221.78.34                             0.0%    10    5.0   2.9   1.0  10.9   3.1
  7.|-- 80.249.210.177                            0.0%    10    9.1   7.5   7.0   9.1   0.5
  8.|-- ysl06.ysl24.transtelecom.net              0.0%    10   55.5  55.9  55.1  57.3   0.5
  9.|-- Yarnet-gw.transtelecom.net                0.0%    10   55.1  55.2  55.0  55.5   0.0
 10.|-- asr-1002-b2.yarnet.ru                     0.0%    10   47.6  47.7  47.6  48.1   0.0
 11.|-- ppp-vpdn-212.232.60.105.yarnet.ru         0.0%    10   49.4  49.2  49.1  49.4   0.0


25/08/2019 18:06:18 UTC
--------------------

MTR:
Start: Sun Aug 25 18:06:19 2019 Blizzard  1.|-- Blizzard                        0.0%    10    0.4   0.4   0.3   0.7   0.0
  2.|-- 37.244.25.2                        0.0%    10    0.5   0.7   0.5   1.4   0.0
  3.|-- Blizzard                    0.0%    10    1.3   1.8   1.2   6.3   1.5
  4.|-- 137.221.66.34                      0.0%    10    1.2   1.1   1.0   1.3   0.0
  5.|-- 137.221.77.70                      0.0%    10    7.9  18.8   7.4  55.9  17.5
  6.|-- 137.221.65.19                      0.0%    10   29.2   9.7   7.5  29.2   6.8
  7.|-- 137.221.79.34                      0.0%    10    7.7  10.8   7.6  26.1   6.7
  8.|-- lnn11-ge500.501.transtelecom.net  10.0%    10  116.0 116.3 115.8 117.6   0.4
  9.|-- ysl06.ysl24.transtelecom.net      10.0%    10  201.6 166.8 162.2 201.6  13.0
 10.|-- Yarnet-gw.transtelecom.net        10.0%    10  163.1 163.3 163.1 163.7   0.0
 11.|-- asr-1002-b2.yarnet.ru             10.0%    10  157.3 157.3 157.1 157.5   0.0
 12.|-- ppp-vpdn-212.232.60.105.yarnet.ru 10.0%    10  157.8 158.6 157.7 163.5   1.7


25/08/2019 18:06:19 UTC
--------------------

MTR:
Start: Sun Aug 25 18:06:22 2019 Blizzard  1.|-- Blizzard                        0.0%    10    0.3   0.3   0.3   0.5   0.0
  2.|-- 37.244.25.2                        0.0%    10    0.8   0.6   0.5   0.9   0.0
  3.|-- Blizzard                    0.0%    10    1.3   1.3   1.1   1.6   0.0
  4.|-- 137.221.66.34                      0.0%    10    1.1   1.2   1.0   1.5   0.0
  5.|-- 137.221.77.70                      0.0%    10  116.3  19.8   7.4 116.3  34.2
  6.|-- 137.221.65.19                      0.0%    10    7.7   9.5   7.4  27.5   6.3
  7.|-- 137.221.79.34                      0.0%    10    7.7   7.7   7.6   7.8   0.0
  8.|-- lnn11-ge500.501.transtelecom.net  10.0%    10  115.9 116.0 115.8 116.7   0.0
  9.|-- ysl06.ysl24.transtelecom.net      10.0%    10  162.4 162.7 162.1 164.3   0.5
 10.|-- Yarnet-gw.transtelecom.net        10.0%    10  163.3 163.2 163.0 163.7   0.0
 11.|-- asr-1002-b2.yarnet.ru             20.0%    10  157.4 157.3 157.1 157.4   0.0
 12.|-- ppp-vpdn-212.232.60.105.yarnet.ru 10.0%    10  158.1 158.4 157.6 162.4   1.4


25/08/2019 18:06:22 UTC
--------------------
2

You have a lot of time outs when trying to access some of the hops of your ISP before it reaches the Blizzard servers. I suggest contacting your ISP to let them investigate this.

Also ensure you do not have any background processes running and that you are the only one connecting to your router. Also go cable if you aren’t yet.

3

Timeouts are normal in a tracert because some ISP’s do not have ICMP (ping) enabled on there routers.

I see another post on the forum from an other user who hase the same problem and it looks like some proxy or core routers of blizzard experiencing some problems. I you look up the ip on google you come across forums from overwatch aswell.

4

I won’t deny either, cuz I see this one multiple times and it’s where the ms jumps up:

ae1-br01-eqsk1.as57976.net [137.221.86.33]

That one is located in The Netherlands hosted by Blizzard. However, that they don’t have ping enabled is uncommon and should not be the case usually if they want to trace latency issues.

5

I won’t say the latency has been constant for me, but I’ve definitely noticed really bad lag spikes, and so have party members all at the same time.

6

I was talking about the providers and hops it has to go trough. An its very common.
What ping does is just ping the end server or just 1 ip you are looking for. A tracert pings all servers and hops in between. In some cases you wil go trough a hop that has ICMP disabled so you will see a timeout in your tracert. Even tough it knows trough witch hops it goes.

7

I am well aware what the differences are between a ping and a tracert, thank you.

If it is indeed spreading more, especially with people from the same area, then maybe it is a good time for Blizzard to check their accelerators.