Game unplayable starting today (latency)

Technical Support
1

I have been having extreme latency starting today in what appears to be only HotS.

looking glass:

TRACEROUTE:
traceroute to 50.89.33.78 (50.89.33.78), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.471 ms 3.460 ms 3.461 ms
2 24.105.18.3 (24.105.18.3) 3.478 ms 3.479 ms 3.479 ms
3 137.221.105.16 (137.221.105.16) 3.477 ms 3.478 ms 3.477 ms
4 137.221.66.18 (137.221.66.18) 3.390 ms 3.391 ms 3.391 ms
5 137.221.83.82 (137.221.83.82) 6.728 ms 6.742 ms 6.743 ms
6 137.221.65.68 (137.221.65.68) 14.205 ms 11.734 ms 11.728 ms
7 137.221.68.32 (137.221.68.32) 11.791 ms 11.798 ms 12.225 ms
8 ae34.pr1.lax10.tbone.rr (66.109.9.160) 11.256 ms 5.609 ms 5.667 ms
9 66.109.5.240 (66.109.5.240) 68.662 ms 66.286 ms 66.292 ms
10 bu-ether16.dllstx976iw-bcr00.tbone.rr (66.109.6.1) 66.984 ms 64.464 ms 64.452 ms
11 bu-ether11.hstqtx0209w-bcr00.tbone.rr (66.109.6.38) 70.106 ms 64.928 ms 64.931 ms
12 bu-ether11.tamsflde20w-bcr00.tbone.rr (66.109.1.71) 64.710 ms 64.706 ms 66.175 ms
13 66.109.6.43 (66.109.6.43) 62.412 ms 62.028 ms 62.018 ms
14 hun0-0-0-0.tamp20-car2.bhn (72.31.3.96) 69.368 ms 69.294 ms 69.213 ms
15 bu-14-orld71-car2.bhn (71.44.1.215) 69.938 ms 69.838 ms 69.880 ms

04/06/2020 21:15:14 UTC

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

— 50.89.33.78 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3003ms

04/06/2020 21:15:14 UTC

MTR:
Start: Thu Jun 4 21:15:14 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- 24.105.18.3 0.0% 10 0.6 0.6 0.5 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 0.8 0.9 0.8 1.3 0.0
4.|-- 137.221.66.18 0.0% 10 0.4 1.3 0.4 7.6 2.1
5.|-- 137.221.83.82 0.0% 10 5.8 8.9 5.7 35.2 9.2
6.|-- 137.221.65.68 0.0% 10 6.1 6.2 5.7 7.9 0.5
7.|-- 137.221.68.32 0.0% 10 6.0 8.9 5.9 34.9 9.1
8.|-- ae34.pr1.lax10.tbone.rr 0.0% 10 5.6 7.6 5.5 17.3 4.3
9.|-- 66.109.5.240 0.0% 10 68.5 65.2 61.2 68.8 2.7
10.|-- bu-ether16.dllstx976iw-bcr00.tbone.rr 0.0% 10 63.8 64.8 61.7 67.8 2.3
11.|-- bu-ether11.hstqtx0209w-bcr00.tbone.rr 0.0% 10 61.4 64.5 61.4 68.6 2.6
12.|-- bu-ether11.tamsflde20w-bcr00.tbone.rr 0.0% 10 68.8 64.9 61.3 68.8 2.4
13.|-- 66.109.6.43 0.0% 10 61.9 62.7 61.8 63.6 0.3
14.|-- hun0-0-0-0.tamp20-car2.bhn 0.0% 10 69.8 69.7 68.6 70.4 0.3
15.|-- bu-14-orld71-car2.bhn 0.0% 10 69.8 69.0 68.1 69.8 0.0
16.|-- 072-031-220-139.res.spectrum 0.0% 10 70.0 69.2 67.8 70.7 0.8
17.|-- bundle-ether2.orld41-ser2.bhn 0.0% 10 68.7 68.5 68.3 68.7 0.0
18.|-- 072-031-218-095.res.spectrum 0.0% 10 67.6 67.7 67.6 68.0 0.0
19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

04/06/2020 21:15:14 UTC

100% packets lost? Happens each time.

This started with the patch today.

Edit:Had to remove all the .coms on the sites apparently, no links allowed?

2

Hey there Korsair! Thanks for reaching out with that LookingGlass test data. Let’s go ahead and have you run a WinMTR network test so that we can further investigate the problem. Here are the instructions:

  1. Download the tool from this page
  2. Enter the game IP into the “host” field. The IP address for our games are listed on the winMTR instructions page
  3. Start the test and play the affected game for at least 15 minutes. Ensure the problem happens while the winMTR tool is running.
  4. After recording the problem data, click “export text” and save the winMTR file in an easy to find location.
  5. Once you have that made, open the file. You’ll need to copy and paste the contents of the Text document into the post, and put four Tilde (~) marks above the winMTR. It’ll look like this:
WinMTR goes here

If you have issues pasting here, please use Pastebin and post the link (ex: Pastebin (dot) com/123456).

3

htt ps://pastebin.com/uvQLE9Qm

Game steadily gains ping, starting at 30ish up to 300+ when it becomes a slideshow

4

Korsair,

Your latency appears to begin between your PC and router. You’ve got an average of 10 ms there, but you also have spikes up into the several hundred ms. If you’re on a wifi connection, see if swapping to ethernet improves the connection. You should also power cycle your router/restart your PC. If neither works, let’s get a new winMTR run while on ethernet - that should let us see if the problem there is fixed, which will keep it from messing with the rest of the test. (With WinMTR - issues earlier in the test make anything after that point mostly useless, unfortunately.)