High ping lately


#41

8 11 ms 11 ms 10 ms mmo-cr3.mmo-cr2.bahnhof.net [46.59.112.6]
9 24 ms 24 ms 24 ms pr01.eqfr5.blizzardonline.net [80.81.195.26]
10 24 ms 24 ms 24 ms ae1-br01-eqfr5.blizzardonline.net [137.221.80.33]
11 33 ms 33 ms 33 ms et-0-0-2-br01-eqpa4.blizzardonline.net [137.221.65.26]
12 33 ms 33 ms 33 ms be1-pe01-eqpa4.blizzardonline.net [137.221.77.67]
13 33 ms 33 ms 33 ms 185.60.114.159

This is the final stretch of my route, for comparison with someone not having issues while playing on the same servers. Notice the different path taken inside of the datacenter. The host that is the common factor between almost everyone having this issue is nowhere to be seen in my route, and I never get routed back to the same subnet, which is the case for the ones having issues.

Delmoryth, with all respect, yes there are a lot of people who has issues due to their ISPs, not to mention shoddy home wireless networks, but there is a malfunctioning device, or a mistake in a routing table, on the 137.221.78.0/24 network in the data center. That subnet stands out like firework in all of these threads, and that part of the route makes absolutely no sense.

This issue has been around for atleast half a year, and there is no way noone at Blizzard knows about it.

Edit: When testing another EU server instance, I manage to hit the same subnet. One hop.

9 24 ms 24 ms 24 ms pr01.eqfr5.blizzardonline.net [80.81.195.26]
10 24 ms 24 ms 24 ms ae1-br01-eqfr5.blizzardonline.net [137.221.80.33]
11 29 ms 29 ms 29 ms et-0-0-2-br01-eqam1.blizzardonline.net [137.221.65.29]
12 29 ms 29 ms 29 ms et-0-0-31-pe01-eqam1.blizzardonline.net [137.221.78.67]
13 30 ms 30 ms 30 ms 185.60.112.157

I fail to see why the packets from the clients having issues should ever have to double back, and that’s where the huge increase can be seen. Not sure if the problem only exists in the Amsterdam data center, or if that’s just coincidence.


#42

I agree with Exodus. The last Israeli hop may not send “TTL expired” messages properly, but it responds to all the pings, making it very unlikely to be the root cause. Combine that with people from other places experiencing the same problem, and the only explanation you can arrive at is a problem with the mentioned 137.221.78.0/24 subnet.


#43

Another interesting piece of information -
I have done all my tests against 185.60.112.157, which is one of the two addresses in the “Running a Pathping” article.
The second address, 185.60.114.159, doesn’t respond to ping at all. Running a tracert on it shows the following:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 6 ms 8 ms DESKTOP-I37SM18 [0.0.0.0]
3 12 ms 12 ms 12 ms 172.18.1.246
4 12 ms 12 ms 12 ms 172.17.10.154
5 15 ms * * 172.17.10.185
6 * * * Request timed out.
7 80 ms 81 ms 81 ms adm-b3-link.telia. net [213.248.69.129]
8 82 ms 83 ms 84 ms adm-bb3-link.telia. net [62.115.122.178]
9 82 ms 83 ms 82 ms adm-b2-link.telia. net [62.115.141.63]
10 99 ms 89 ms 83 ms 62.115.46.198
11 81 ms 83 ms 83 ms ae1-br02-eqam1.blizzardonline. net [137.221.78.35]
12 87 ms 87 ms 87 ms et-0-0-3-br02-eqpa4.blizzardonline. net [137.221.65.92]
13 164 ms 164 ms 167 ms be2-pe02-eqpa4.blizzardonline. net [137.221.77.73]
14 * * * Request timed out.
15 * * * Request timed out.

Again, high ping starts right at the last hop (this time 137.221.77.73) and after that the packets disappear.


#44

Wall of text coming up, as I hope this will clear things up for the support staff, and also help guide their troubleshooting at their provider, as I am fairly sure I know what’s wrong.

This post actually helped me quite a bit, as it made me look at the naming conventions and map that to real network topography types.

BR and PE are obviously the border and provider edge routers at the data center, and 01/02 are the different “legs” of the NLB setup. You are on leg 2, I’m on leg 1.

The chances that two legs for HA/NLB are designed with significantly different topologies from eachother are virtually zero. The most common case is that everything is connected exactly the same, and using the same addressing but on different subnets. Even if you use some other addressing convention, it is extremely unlikely that you will change the topology itself, in regard to netsizes and routing.

Now, notice how my path goes Internet -> Level 1 Border Router (country-level) -> Level 2 Border Router (site-level) -> Provider Edge Router. Yours does too in this last post. That’s what makes sense, and in a functioning datacenter-type network, that’s what will happen no matter if they use IS-IS or OSPF. Packets enter a topological layer on one interface, and get routed out through a different interface.

What should not happen, except in very special cases, is that the packets are routed out on the same interface they come in at. If the routing protocol used at the facility is IS-IS (which is the most common at service providers) it shouldn’t even be possible to have two areas on the same interface.

Another thing that are usually meant not to happen is that packets skip an entire level of routing. Say packets are coming in at “level 1” and are destined for “level 4”. As a service provider you design your network in a way that makes the packets go 1 -> 2 -> 3 -> 4. You don’t HAVE to do it, but you will want to, for several reasons. So if a packet comes in at 1, and gets routed to a device on level 3, you probably have misconfigured something.

If a packet comes in on level 1, and gets routed to a router on level 3, on the same interface it came in on, you can be sure you messed something up.

This is what happens. Not all the time, but “often”, and it explains a lot. Packets come in at 137.221.78.35, which is supposed to be a “level 1” router. It then gets routed to 137.221.78.73 (“level 3” router), which means it’s either getting sent back out on the same interface, or on another interface on the same network.

A router having two interfaces on the same network, in a network with any type of IGP, will confuse the hell out of atleast that router, and often routers on the level above it. The routing algorithms often spend tons of time in loops when trying to calculate the shortest path, and the packet won’t get routed until the algorithm has found a path.

If one piece of equipment has instead been placed on the wrong network, by mistake, that may create the situation where the incoming interface on the router effectively is a part of two areas, which is a violation of IS-IS, and in most cases a problem in OSPF.

Here we see clearly that packets are often routed from 137.221.78.0 to 137.221.78.0. Either .35 or .73 is on the wrong network, giving .35 a severe headache when it tries to find the best route for the packet. That headache will be affect every packet passing through .35, and the higher the throughput, the more this issue will be compounded, causing large variations.


#45

After spending way to much time on this (obviously much too long vacation) I’ve come to the conclusion there must be a routing mistake in one of the data centers. This leads to traffic being routed to the wrong plane on the first router, resulting in asymmetric routing, which in turn throws the cost calculations off all over Europe, so your packets are taking a MUCH longer way back home.

Large parts of Israel will, due to how they’re hooked into the internet, hit this particular data center…


#46

This makes a lot of sense, and would explain the problem and why we experience it. I would like to have some input from Blizzard regarding this.


#47

Can you try starting a custom game with AIs, hit shift+ctrl+n and run a tracert to the IP shown there while still in the game?

Once you hit the AWS DC connection you will likely not get any replies, but it would be interesting to see what it looks like until then.


#48

TheExodus: These are the results for me for that test. Ping in game is still 160~ ms.

Tracing route to 5.42.169.211 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms OpenWrt.lan [192.168.1.1]
2 6 ms 7 ms 7 ms 10.240.40.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 64 ms 70 ms 69 ms ldn-b4-link.telia .net [62.115.161.68]
7 67 ms 64 ms 66 ms blizzard-ic-316507-slou-b1.c.telia .net [62.115.145.217]
8 86 ms 70 ms 64 ms ae1-br01-eqld5.blizzardonline .net [137.221.79.33]
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.

| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
OpenWrt.lan - 0 229 229 0 0 2 1
10.240.40.1 - 0 229 229 6 8 14 9
172.18.11.9 - 89 51 6 0 8 13 13
BB-H2-B32.236-HFA-HOT-100G.hotnet.net.il - 87 52 7 9 11 15 11
10.255.200.1 - 73 59 16 64 65 67 65
ldn-b4-link.telia .net - 0 229 229 63 67 106 69
blizzard-ic-316507-slou-b1.c.telia .net - 0 229 229 63 66 91 70
ae1-br01-eqld5.blizzardonline .net - 0 229 229 64 69 229 71
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
No response from host - 100 46 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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


#49

Yeah, it appears that when routing to a server in AWS the very router that is likely to cause the issues doesn’t send TEM.


#50

Hopefully this gets fixed soon, thanks Exodus


#51

Is there any update on that, Blizzard? Ping is still high, and it looks like the ball is 100% in your court


#52

Wow. At least you have 160. What a blessing. I am getting spikes from 200 - 2000 from my ussual 80ms. World of Warcraft -> no problem. OW -> unplayable.


#53

Any news on this? Everything points to the problem being on the datacenter end, and knowing that it is atleast being investigated would be nice.


#54

Hey all,

We need some fresh logs to have this looked into further. If you are still experiencing this, please reply with the following:

■ Date/time you first experienced the issue :
■ City and country :
■ ISP :
Traceroute (created while experiencing the issue) :
Pathping (created while experiencing the issue) :
WinMTR test (created while experiencing the issue) :

In addition to these, please run the 3 available tests in our Looking-Glass tool as well. I know it seems like that does the same test, but it runs it in a different way which provides additional information to look into.


Have a few seconds to spare? Let me know how I’m doing!
https://www.surveymonkey.com/r/Nenyasqi


#55

You have been getting logs for half a year, all showing a massive increase in RTT after one of the Equinix border routers in Amsterdam. Is nothing being done there?


#56

i dont remember what was the date , but it’s happened on the day when hammond hit ptr

Israel

hotnet

Tracing route to 185.60.114.159 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  193.150.117.100
  2     8 ms     9 ms     8 ms  10.177.48.1
  3    15 ms    15 ms    16 ms  172.18.2.238
  4    15 ms    15 ms    16 ms  172.17.10.74
  5    18 ms    14 ms    14 ms  172.17.10.185
  6     *        *        *     Request timed out.
  7    85 ms    87 ms    98 ms  adm-b3-link.telia.net [213.248.69.129]
  8    87 ms    87 ms    90 ms  adm-bb3-link.telia.net [62.115.122.178]
  9    84 ms    85 ms    84 ms  adm-b2-link.telia.net [213.155.137.211]
 10    87 ms    84 ms    84 ms  62.115.46.198
 11    86 ms    95 ms    86 ms  ae1-br02-eqam1.blizzardonline.net [137.221.78.35]
 12    93 ms    93 ms    93 ms  et-0-0-3-br02-eqpa4.blizzardonline.net [137.221.65.92]
 13   165 ms   166 ms   164 ms  be2-pe02-eqpa4.blizzardonline.net [137.221.77.73]
 14   172 ms   172 ms   171 ms  185.60.114.159
        Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           DESKTOP-5K63HOI [193.150.117.67]
                            0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  193.150.117.100
                          100/ 100 =100%   |
  2  ---     100/ 100 =100%     0/ 100 =  0%  10.177.48.1
                            0/ 100 =  0%   |
  3  ---     100/ 100 =100%     0/ 100 =  0%  172.18.2.238
                            0/ 100 =  0%   |
  4  ---     100/ 100 =100%     0/ 100 =  0%  172.17.10.74
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         193.150.117.100 -    0 |  336 |  336 |    0 |    0 |    1 |    0 |
|                             10.177.48.1 -    0 |  336 |  336 |    7 |   11 |   37 |   37 |
|                            172.18.2.238 -    0 |  336 |  336 |   14 |   18 |   43 |   35 |
|                            172.17.10.74 -    0 |  336 |  336 |   14 |   19 |   43 |   35 |
|                           172.17.10.185 -   56 |  105 |   47 |    0 |   16 |   23 |   16 |
|BB-H2-B31.231-HFA-HOT-100G.hotnet.net.il -   54 |  107 |   50 |    0 |   15 |   23 |   15 |
|                   adm-b3-link.telia.net -    0 |  336 |  336 |   84 |   88 |  115 |   84 |
|                  adm-bb3-link.telia.net -    0 |  336 |  336 |   85 |   90 |  111 |   90 |
|                   adm-b2-link.telia.net -    0 |  336 |  336 |   83 |   87 |  110 |   97 |
|                           62.115.46.198 -    0 |  336 |  336 |   83 |   88 |  113 |   87 |
|       ae1-br02-eqam1.blizzardonline.net -    0 |  336 |  336 |   84 |   91 |  216 |   88 |
|  et-0-0-3-br02-eqpa4.blizzardonline.net -    0 |  336 |  336 |   90 |   95 |  252 |   93 |
|       be2-pe02-eqpa4.blizzardonline.net -    0 |  336 |  336 |  164 |  168 |  190 |  169 |
|                          185.60.114.159 -    0 |  336 |  336 |  169 |  174 |  199 |  170 |
|________________________________________________|______|______|______|______|______|______|
TRACEROUTE:
traceroute to 213.57.174.225 (213.57.174.225), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.369 ms  0.340 ms  0.336 ms
 2  37.244.24.130 (37.244.24.130)  0.550 ms  0.571 ms  0.651 ms
 3  Blizzard Blizzard  1.862 ms  1.878 ms  1.882 ms
 4  137.221.66.40 (137.221.66.40)  1.248 ms  1.256 ms  1.251 ms
 5  137.221.78.70 (137.221.78.70)  1.073 ms  1.080 ms  1.078 ms
 6  137.221.65.90 (137.221.65.90)  8.349 ms  6.873 ms  6.833 ms
 7  137.221.65.24 (137.221.65.24)  75.365 ms  76.580 ms  76.582 ms
 8  137.221.65.14 (137.221.65.14)  82.068 ms  82.082 ms  82.081 ms
 9  137.221.72.32 (137.221.72.32)  81.783 ms  81.806 ms  81.807 ms
10  * * *
11  frk1-cr1-te7-1-0.cprm.net (195.8.1.70)  89.805 ms  88.827 ms  88.797 ms
12  * * hotnet1.cprm.net (195.8.10.10)  140.013 ms
13  CON-HOT-100G-V231-HFA.hotnet.net.il (213.57.3.113)  138.547 ms  138.497 ms  139.104 ms
14  * * *
15  * * *


06/08/2018 04:23:22 UTC
--------------------

TRACEROUTE:
traceroute to 213.57.174.225 (213.57.174.225), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.347 ms  0.347 ms  0.359 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  137.221.65.16 (137.221.65.16)  78.993 ms  78.870 ms  78.833 ms
 7  137.221.72.32 (137.221.72.32)  78.790 ms  78.776 ms  78.894 ms
 8  * * *
 9  frk1-cr1-te7-1-0.cprm.net (195.8.1.70)  93.835 ms  91.937 ms  91.916 ms
10  * * hotnet1.cprm.net (195.8.10.10)  140.245 ms
11  CON-HOT-100G-V236-HFA.hotnet.net.il (213.57.3.117)  139.939 ms  140.463 ms *
12  * * *
13  * * *
14  * * *
15  * * *


06/08/2018 04:23:22 UTC
--------------------

PING:
PING 213.57.174.225 (213.57.174.225) 56(84) bytes of data.

--- 213.57.174.225 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms



06/08/2018 04:23:22 UTC
--------------------

PING:
PING 213.57.174.225 (213.57.174.225) 56(84) bytes of data.

--- 213.57.174.225 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms



06/08/2018 04:23:22 UTC
--------------------

MTR:
Start: Mon Aug  6 04:23:22 2018 Blizzard  1.|-- Blizzard                         0.0%    10    0.3   0.3   0.2   0.3   0.0
  2.|-- 37.244.25.3                          0.0%    10    0.4   0.5   0.4   0.6   0.0
  3.|-- Blizzard                      0.0%    10    0.9   1.2   0.9   1.4   0.0
  4.|-- 137.221.66.34                        0.0%    10    1.0   1.1   0.8   1.5   0.0
  5.|-- 137.221.77.66                        0.0%    10    0.7   0.9   0.7   1.0   0.0
  6.|-- 137.221.65.16                        0.0%    10   78.7  78.8  78.7  78.9   0.0
  7.|-- 137.221.72.32                        0.0%    10   78.6  78.7  78.6  78.9   0.0
  8.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0
  9.|-- frk1-cr1-te7-1-0.cprm.net            0.0%    10   92.0  92.7  90.9  94.5   1.3
 10.|-- hotnet1.cprm.net                    70.0%    10  139.8 139.7 139.6 139.8   0.0
 11.|-- CON-HOT-100G-V236-HFA.hotnet.net.il 70.0%    10  139.7 139.9 139.7 140.1   0.0
 12.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0


06/08/2018 04:23:22 UTC
--------------------

MTR:
Start: Mon Aug  6 04:23:22 2018 Blizzard  1.|-- Blizzard                             0.0%    10    0.3   0.4   0.3   0.7   0.0
  2.|-- 37.244.24.130                             0.0%    10    0.6   0.6   0.5   0.7   0.0
  3.|-- Blizzard                           0.0%    10    1.6   1.3   1.1   1.6   0.0
  4.|-- 137.221.66.40                             0.0%    10    1.0   0.8   0.7   1.0   0.0
  5.|-- 137.221.78.70                             0.0%    10    1.0   8.3   1.0  70.9  22.0
  6.|-- 137.221.65.90                             0.0%    10    6.7   9.6   6.7  34.8   8.8
  7.|-- 137.221.65.24                             0.0%    10   75.4  75.5  75.3  75.9   0.0
  8.|-- 137.221.65.14                             0.0%    10   80.9  81.0  80.8  81.6   0.0
  9.|-- 137.221.72.32                             0.0%    10   80.7  80.8  80.5  81.8   0.3
 10.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- frk1-cr1-te7-1-0.cprm.net                 0.0%    10   88.7  89.2  87.6  91.3   1.2
 12.|-- hotnet1.cprm.net                         50.0%    10  138.6 139.3 138.2 143.3   2.1
 13.|-- CON-HOT-100G-V231-HFA.hotnet.net.il      40.0%    10  138.7 138.6 138.5 138.8   0.0
 14.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0


06/08/2018 04:23:22 UTC
--------------------

#57

■ Date/time you first experienced the issue: Few months ago, not sure exactly (before the Hammond patch definitely)
■ City and country: Haifa, Israel
■ ISP: Hotnet
Traceroute (created while experiencing the issue):

> tracert 5.42.169.222

Tracing route to 5.42.169.222 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2     8 ms     8 ms     7 ms  10.240.40.1
  3     *        *        9 ms  172.18.11.9
  4     *        8 ms     *     BB-H2-B32.236-HFA-HOT-100G.hotnet.net.il [213.57.3.116]
  5    58 ms     *       66 ms  10.255.200.1
  6    59 ms    62 ms    59 ms  ldn-b4-link.telia.net [62.115.161.68]
  7    61 ms    64 ms    64 ms  blizzard-ic-316507-slou-b1.c.telia.net [62.115.145.217]
  8    60 ms    61 ms    60 ms  ae1-br01-eqld5.blizzardonline.net [137.221.79.33]
  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.

Trace complete.

Pathping (created while experiencing the issue):
(pretty useless results but there you go)

> pathping -q 30 5.42.169.222

Tracing route to 5.42.169.222 over a maximum of 30 hops

  0  my-computer.lan [192.168.1.173]
  1  OpenWrt.lan [192.168.1.1]
  2  10.240.40.1
  3     *        *     172.18.11.9
  4     *        *        *
Computing statistics for 75 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           my-computer.lan [192.168.1.173]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  OpenWrt.lan [192.168.1.1]
                              100/ 100 =100%   |
  2  ---     100/ 100 =100%     0/ 100 =  0%  10.240.40.1
                                0/ 100 =  0%   |
  3  ---     100/ 100 =100%     0/ 100 =  0%  172.18.11.9

Trace complete.

WinMTR test (created while experiencing the issue):

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             OpenWrt.lan -    0 |  153 |  153 |    0 |    0 |    1 |    0 |
|                             10.240.40.1 -    0 |  153 |  153 |    6 |    8 |   18 |    8 |
|                             172.18.11.9 -   72 |   39 |   11 |    0 |    9 |   13 |   13 |
|BB-H2-B32.236-HFA-HOT-100G.hotnet.net.il -   74 |   38 |   10 |    0 |   10 |   16 |    8 |
|                            10.255.200.1 -   62 |   44 |   17 |    0 |   61 |   65 |   60 |
|                   ldn-b4-link.telia.net -    0 |  153 |  153 |   58 |   63 |   81 |   71 |
|  blizzard-ic-316507-slou-b1.c.telia.net -    0 |  153 |  153 |   59 |   64 |   76 |   62 |
|       ae1-br01-eqld5.blizzardonline.net -    0 |  153 |  153 |   59 |   69 |  498 |   65 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    1 | 5357 | 5356 |    0 |    0 |    9 |    0 |
|                             10.240.40.1 -    0 | 5361 | 5361 |    6 |    8 |   76 |    8 |
|                             172.18.11.2 -   76 | 1333 |  324 |    0 |    9 |   36 |    8 |
|bb-h2-b31.231-hfa-hot-100g.hotnet.net.il -   81 | 1267 |  241 |    6 |   11 |  105 |   12 |
|                            10.255.200.1 -   57 | 1649 |  719 |   58 |   61 |   87 |   59 |
|                   ldn-b4-link.telia.net -    0 | 5361 | 5361 |   57 |   63 |  141 |   59 |
|  blizzard-ic-316507-slou-b1.c.telia.net -    0 | 5361 | 5361 |   58 |   62 |  132 |   76 |
|       ae1-br01-eqld5.blizzardonline.net -    0 | 5350 | 5350 |   59 |   72 | 4179 |   61 |
|  et-0-0-2-br02-eqpa4.blizzardonline.net -    0 | 5361 | 5361 |   65 |   71 |  358 |   70 |
|       be2-pe02-eqpa4.blizzardonline.net -    0 | 5361 | 5361 |  142 |  145 |  192 |  152 |
|                          185.60.114.157 -    0 | 5361 | 5361 |  145 |  148 |  186 |  150 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Looking glass results:

TRACEROUTE:
traceroute to 213.57.179.4 (213.57.179.4), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.309 ms  0.279 ms  0.275 ms
 2  37.244.24.130 (37.244.24.130)  0.663 ms  0.732 ms  0.810 ms
 3  Blizzard Blizzard  1.075 ms  1.102 ms  1.158 ms
 4  137.221.66.46 (137.221.66.46)  0.803 ms  0.887 ms  0.933 ms
 5  137.221.78.72 (137.221.78.72)  12.275 ms  12.288 ms  12.288 ms
 6  137.221.65.90 (137.221.65.90)  10.075 ms  8.485 ms  8.484 ms
 7  137.221.65.24 (137.221.65.24)  94.352 ms  96.160 ms  96.164 ms
 8  137.221.65.14 (137.221.65.14)  85.162 ms  85.172 ms  85.170 ms
 9  137.221.72.32 (137.221.72.32)  85.017 ms  80.700 ms  80.690 ms
10  * * *
11  frk1-cr1-te7-1-0.cprm.net (195.8.1.70)  88.292 ms  87.118 ms  87.092 ms
12  * hotnet1.cprm.net (195.8.10.10)  145.042 ms *
13  * CON-HOT-100G-V231-HFA.hotnet.net.il (213.57.3.113)  144.141 ms *
14  * * *
15  dynamic-213-57-179-4.hotnet.net.il (213.57.179.4)  150.159 ms  154.247 ms  152.737 ms


06/08/2018 18:41:51 UTC
--------------------

PING:
PING 213.57.179.4 (213.57.179.4) 56(84) bytes of data.
64 bytes from 213.57.179.4: icmp_seq=1 ttl=52 time=144 ms
64 bytes from 213.57.179.4: icmp_seq=2 ttl=52 time=148 ms
64 bytes from 213.57.179.4: icmp_seq=3 ttl=52 time=145 ms
64 bytes from 213.57.179.4: icmp_seq=4 ttl=52 time=143 ms

--- 213.57.179.4 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 143.864/145.736/148.756/1.902 ms


06/08/2018 18:41:50 UTC
--------------------

PING:
PING 213.57.179.4 (213.57.179.4) 56(84) bytes of data.
64 bytes from 213.57.179.4: icmp_seq=1 ttl=52 time=150 ms
64 bytes from 213.57.179.4: icmp_seq=2 ttl=52 time=150 ms
64 bytes from 213.57.179.4: icmp_seq=3 ttl=52 time=150 ms
64 bytes from 213.57.179.4: icmp_seq=4 ttl=52 time=149 ms

--- 213.57.179.4 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 149.985/150.568/150.987/0.535 ms


06/08/2018 18:41:51 UTC
--------------------

TRACEROUTE:
traceroute to 213.57.179.4 (213.57.179.4), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.302 ms  0.302 ms  0.302 ms
 2  * * *
 3  * * *
 4  137.221.66.36 (137.221.66.36)  1.617 ms  1.633 ms  2.107 ms
 5  * * 137.221.77.68 (137.221.77.68)  1.477 ms
 6  137.221.65.16 (137.221.65.16)  79.120 ms  79.034 ms  79.010 ms
 7  137.221.72.32 (137.221.72.32)  78.873 ms  78.966 ms  78.984 ms
 8  * * *
 9  frk1-cr1-te7-1-0.cprm.net (195.8.1.70)  90.650 ms  90.711 ms  90.709 ms
10  * * *
11  * * *
12  * * *
13  dynamic-213-57-179-4.hotnet.net.il (213.57.179.4)  143.099 ms  143.103 ms  147.349 ms


06/08/2018 18:41:50 UTC
--------------------

MTR:
Start: Mon Aug  6 18:41:51 2018 Blizzard  1.|-- Blizzard                         0.0%    10    0.3   0.2   0.2   0.3   0.0
  2.|-- 37.244.25.3                          0.0%    10    0.5   0.5   0.4   0.5   0.0
  3.|-- Blizzard                      0.0%    10    1.0   1.0   0.7   1.8   0.0
  4.|-- 137.221.66.36                        0.0%    10    0.9   0.9   0.8   1.2   0.0
  5.|-- 137.221.77.68                        0.0%    10    0.8   0.8   0.7   1.1   0.0
  6.|-- 137.221.65.16                        0.0%    10   78.8  79.0  78.7  80.8   0.6
  7.|-- 137.221.72.32                        0.0%    10   78.6  79.2  78.6  83.4   1.4
  8.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0
  9.|-- frk1-cr1-te7-1-0.cprm.net            0.0%    10   92.0  90.8  88.6  94.2   1.6
 10.|-- hotnet1.cprm.net                    50.0%    10  137.0 137.1 137.0 137.4   0.0
 11.|-- CON-HOT-100G-V236-HFA.hotnet.net.il 90.0%    10  137.2 137.2 137.2 137.2   0.0
 12.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0
 13.|-- dynamic-213-57-179-4.hotnet.net.il   0.0%    10  144.7 144.3 143.1 146.4   0.9


06/08/2018 18:41:50 UTC
--------------------

MTR:
Start: Mon Aug  6 18:41:51 2018 Blizzard  1.|-- Blizzard                             0.0%    10    0.2   0.3   0.2   0.4   0.0
  2.|-- 37.244.24.130                             0.0%    10    0.4   0.5   0.4   0.8   0.0
  3.|-- Blizzard                           0.0%    10    1.1   1.2   0.9   2.1   0.0
  4.|-- 137.221.66.46                             0.0%    10    0.7   0.8   0.6   1.3   0.0
  5.|-- 137.221.78.72                             0.0%    10    0.9   4.7   0.9  38.1  11.7
  6.|-- 137.221.65.90                             0.0%    10    6.7   6.8   6.7   7.0   0.0
  7.|-- 137.221.65.24                             0.0%    10   75.4  77.8  75.3 100.3   7.9
  8.|-- 137.221.65.14                             0.0%    10   80.8  82.0  80.8  92.7   3.7
  9.|-- 137.221.72.32                             0.0%    10   80.7  83.7  80.6  95.2   5.6
 10.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- frk1-cr1-te7-1-0.cprm.net                 0.0%    10   88.3  87.6  85.4  89.0   1.2
 12.|-- hotnet1.cprm.net                         70.0%    10  143.8 143.7 143.6 143.8   0.0
 13.|-- CON-HOT-100G-V231-HFA.hotnet.net.il      90.0%    10  143.9 143.9 143.9 143.9   0.0
 14.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
 15.|-- dynamic-213-57-179-4.hotnet.net.il        0.0%    10  151.9 151.1 150.2 152.6   0.3


06/08/2018 18:41:51 UTC
--------------------

Latency is still around 160ms. Pretty stable most time.

You can find some more relevant data by google searching 137.221.65.24 , 137.221.65.14 , 137.221.72.32 …


#58

Are there any news on this?


#59

Just came home today and my latency in game is ~80ms like it was before this problem started.

Not sure what caused it to come back, but i’m happy it’s better and hope it will stay that way.

Just for reference, here is my current MTR:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             OpenWrt.lan -    0 |  231 |  231 |    0 |    0 |    1 |    0 |
|                             10.240.40.1 -    0 |  231 |  231 |    6 |    8 |   45 |   14 |
|                             172.18.11.2 -   71 |   61 |   18 |    0 |    9 |   14 |   10 |
|BB-H2-B31.231-HFA-HOT-100G.hotnet.net.il -   84 |   54 |    9 |    0 |    8 |   11 |    9 |
|                            10.255.200.1 -   68 |   64 |   21 |   58 |   60 |   65 |   60 |
|                   ldn-b4-link.telia.net -    0 |  231 |  231 |   58 |   63 |  109 |   63 |
|  blizzard-ic-316507-slou-b1.c.telia.net -    0 |  231 |  231 |   59 |   63 |   77 |   71 |
|              ae1-br01-eqld5.as57976.net -    0 |  231 |  231 |   66 |   72 |  249 |   78 |
|         et-0-0-2-br02-eqpa4.as57976.net -    0 |  231 |  231 |   66 |   72 |  200 |   78 |
|              be2-pe02-eqpa4.as57976.net -    0 |  231 |  231 |   66 |   69 |   79 |   68 |
|                          185.60.114.157 -    0 |  231 |  231 |   66 |   69 |   88 |   75 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

#60

Wish I had the same luck, 130ms right now