Random high Latency on EU servers

Technical Support
1

I’ve seen a few of these posts before but I’ve been getting the issue in every match. My Lat is at around 40 then it randomly jumps to 60+. Making it unplayable for about 15 seconds. I’ve spoken to my internet provider and they can’t find any issues. I did the Looking Glass test. Not sure if it’s kept up to date or not.

I was playing on the American servers last night and the issue never occured. Although I did experience some high lat but nothing game killing.

I’d really love some Blizzard help on this issue.

TRACEROUTE:
traceroute to 150.143.211.255 (150.143.211.255), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.766 ms 0.742 ms 0.736 ms
2 37.244.25.2 (37.244.25.2) 1.011 ms 1.167 ms 1.313 ms Blizzard Blizzard 1.956 ms 1.978 ms 1.982 ms
4 137.221.66.38 (137.221.66.38) 0.873 ms 0.896 ms 0.900 ms
5 137.221.77.52 (137.221.77.52) 8.023 ms 8.052 ms 8.060 ms
6 137.221.65.19 (137.221.65.19) 7.881 ms 7.459 ms 7.428 ms
7 137.221.79.34 (137.221.79.34) 7.466 ms 7.477 ms 7.477 ms
8 195.66.227.42 (195.66.227.42) 7.133 ms 7.394 ms 7.399 ms
9 62.172.103.223 (62.172.103.223) 8.461 ms 8.293 ms 8.309 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

19/09/2020 19:54:35 UTC

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

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

19/09/2020 19:54:35 UTC

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

— 150.143.211.255 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3006ms

19/09/2020 19:54:35 UTC

TRACEROUTE:
traceroute to 150.143.211.255 (150.143.211.255), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.363 ms 0.359 ms 0.360 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

19/09/2020 19:54:35 UTC

MTR:
Start: Sat Sep 19 19:54:35 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

19/09/2020 19:54:35 UTC

MTR:
Start: Sat Sep 19 19:54:35 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- 37.244.25.2 0.0% 10 0.7 0.7 0.6 0.9 0.0 Blizzard 0.0% 10 1.0 0.9 0.7 1.0 0.0
4.|-- 137.221.66.38 0.0% 10 49.9 5.5 0.4 49.9 15.6
5.|-- 137.221.77.52 0.0% 10 7.5 7.6 7.4 9.0 0.3
6.|-- 137.221.65.19 0.0% 10 7.4 10.5 7.4 37.3 9.4
7.|-- 137.221.79.34 0.0% 10 7.6 9.4 7.5 25.1 5.5
8.|-- 195.66.227.42 0.0% 10 7.2 9.9 7.2 19.2 4.4
9.|-- 62.172.103.223 0.0% 10 8.4 8.5 8.3 8.8 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

19/09/2020 19:54:35 UTC

2

Hello Banana,

The Looking Glass measures the connection starting from the Blizzard servers to your home network, so in these cases is not useful to see the problem. You need to see what route your ISP takes to connect you to the Blizzard servers and to do so you need an MTR test. Make the test during the usual timeframe in which you play the game and post the results here.

You can also try the steps in this guide

3

I gave WinMTR a try. I think it was working correctly but I’m not 100% sure. I got the IP from Overwatch, stopped the game. Put the IP into WinMTR pressed Start and played a Match of Overwatch. The issue did occur during Gameplay.

It’s a lot of No response from host so I feel like I did something wrong.
I also had to replace the . with - so it would let me post as I can’t attach the file.
Not sure if you wanted me to post this here.
But Thank you for the help.

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

| WinMTR statistics |

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

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

| dsldevice.lan - 1 | 544 | 543 | 0 | 16 | 2786 | 0 |

| 172.16.16.196 - 1 | 544 | 543 | 12 | 32 | 2900 | 14 |

| 137-hiper04-sheff-dial-plus-net-uk - 98 | 114 | 3 | 0 | 1150 | 3413 | 18 |

| 136-hiper04-sheff-dial-plus-net-uk - 1 | 544 | 543 | 19 | 38 | 2792 | 23 |

| 195.99.125.134 - 1 | 544 | 543 | 18 | 37 | 2792 | 22 |

| peer1-et-7-0-5-interxion-ukcore-bt-net - 1 | 544 | 543 | 19 | 41 | 2792 | 23 |

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

| ae1-br02-eqld5-as57976-net - 1 | 544 | 543 | 27 | 47 | 2799 | 27 |

| et-0-0-2-br02-eqpa4-as57976-net - 1 | 541 | 540 | 27 | 119 | 2998 | 32 |

| et-0-0-1-pe04-eqpa4-as57976-net - 1 | 544 | 543 | 26 | 49 | 2858 | 29 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|____________|||||||

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

4

Banana your first hop to your router is very bad. Are you using wifi? If so please try switching to ethernet cable.

If the issue persists please turn off the device for 10 mins, ensure that it is properly ventilated and not overheating. Check for damaged or kinked ethernet cables, rusted or damaged plugs, turn it back on (after 10 mins) and check how it goes with no-one else connected to the router.

The No response from host lines aren’t a problem. It just means that hop has blocked or deprioritized icmp (ping) traffic.

5

Thank you for the reply. I’m using an Ethernet cable and not Wifi. Is the issue down to the router and the internet provider then?

I’ll try out some things with the router and see what happens. If just strange that when I switched to the US servers the issue didn’t come up during a two hour long play time; all but once for a second. But on the EU servers it happens often and goes on for 10-30 seconds. On a game like Overwatch I’d be a pretty easy kill.

6

That’s not something we can determine. All we can see from your MTR is that there’s maybe an issue with the connectivity between your computer and the router. This is sometimes a problem with the router, but it could even be your network card, CPU usage, network card configuration, a hardware conflict such as a USB Bus interfering with the Ethernet adapter, etc etc. This kind of zeroing in is beyond the scope of support we can provide, but hopefully trying another router will work out for you.

You’ve probably done it already, but be sure to update your network drivers, particularly for killer-networks cards.