High Latency Issues

Technical Support
1

TRACEROUTE:
traceroute to 121.75.154.140 (121.75.154.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.375 ms 0.361 ms 0.359 ms
2 24.105.18.2 (24.105.18.2) 0.638 ms 0.702 ms 0.780 ms
3 137.221.105.10 (137.221.105.10) 0.832 ms 0.846 ms 0.847 ms
4 137.221.66.16 (137.221.66.16) 0.462 ms 0.466 ms 0.471 ms
5 137.221.83.80 (137.221.83.80) 592.233 ms 592.222 ms 797.194 ms
6 * * *
7 137.221.65.31 (137.221.65.31) 5.929 ms 5.944 ms 6.021 ms
8 137.221.89.32 (137.221.89.32) 6.009 ms 6.079 ms 6.438 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

17/10/2020 00:20:53 UTC

TRACEROUTE:
traceroute to 121.75.154.140 (121.75.154.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.269 ms 0.266 ms 0.265 ms
2 37.244.23.3 (37.244.23.3) 0.465 ms 0.555 ms 0.649 ms
3 24.105.62.152 (24.105.62.152) 0.837 ms 0.846 ms 0.837 ms
4 137.221.66.10 (137.221.66.10) 1.765 ms 1.782 ms 1.784 ms
5 * * *
6 * * *
7 * * *
8 137.221.65.31 (137.221.65.31) 43.907 ms 43.962 ms 43.959 ms
9 137.221.89.32 (137.221.89.32) 44.500 ms 44.781 ms 44.785 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

17/10/2020 00:20:53 UTC

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

— 121.75.154.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

17/10/2020 00:20:53 UTC

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

— 121.75.154.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

17/10/2020 00:20:54 UTC

MTR:
Start: Sat Oct 17 00:20:52 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.3 0.3 0.5 0.0
2.|-- 24.105.18.2 0.0% 10 0.6 3.1 0.5 17.2 5.5
3.|-- 137.221.105.10 0.0% 10 0.9 1.1 0.8 1.9 0.0
4.|-- 137.221.66.16 0.0% 10 0.4 18.1 0.4 61.4 28.2
5.|-- 137.221.83.80 0.0% 10 48.8 671.2 48.8 1429. 442.9
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.65.31 0.0% 10 18.3 20.0 5.9 127.1 37.8
8.|-- 137.221.89.32 0.0% 10 6.0 10.3 5.9 33.8 9.1
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

17/10/2020 00:20:52 UTC

MTR:
Start: Sat Oct 17 00:20:53 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.23.3 0.0% 10 0.5 0.5 0.4 0.6 0.0
3.|-- 24.105.62.152 0.0% 10 1.1 2.3 0.7 15.8 4.7
4.|-- 137.221.66.10 0.0% 10 1.9 2.0 1.7 2.3 0.0
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8.|-- 137.221.65.31 0.0% 10 44.6 46.9 43.9 68.3 7.6
9.|-- 137.221.89.32 0.0% 10 44.6 50.2 44.4 89.2 14.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

17/10/2020 00:20:53 UTC

2

Hey, I moved you over to a new thread since the other one was inactive for 2 years here. Could you provide more details of whats been happening in-game?

The looking glass here looks fine, but its generally not as useful unless there’s a widespread issue and we request them directly. Could you provide a WinMTR test instead? Run the test until the problem occurs for 10 to 15 minutes. Copy and paste the text file created and paste it between two ~~~ like so:

~~~
WinMTR Here
~~~

If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)

3

Same problem on EU. After the Halloween event my Ping up to 100-110. Normal was 60-70.

WinMTR to 185.60.114.159, because 5.42. doesn’t have the final host.

Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 505 505 0 0 14 0
10.134.77.1 0 505 505 1 2 41 2
10.134.252.41 0 505 505 5 7 46 5
No response from host 100 102 0 0 0 0 0
No response from host 100 102 0 0 0 0 0
No response from host 100 102 0 0 0 0 0
No response from host 100 102 0 0 0 0 0
No response from host 100 102 0 0 0 0 0
No response from host 100 102 0 0 0 0 0
No response from host 100 102 0 0 0 0 0
No response from host 100 102 0 0 0 0 0
185.60.114.159 0 505 505 80 94 113 94

Netgraph / ams1 (5.42.169.90): https://prnt.sc/v1sxh7