Latency Correction - West Coast - Alaska

Technical Support
1

I’m not sure how to analyze my test results from looking-glass, but I’m desperate to find if there is any way to improve my latency. My results are below, is there anything that stands out as unusual or something that I could potentially fix?

TRACEROUTE:
traceroute to 24.237.98.27 (24.237.98.27), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.950 ms 0.929 ms 0.927 ms
2 24.105.18.3 (24.105.18.3) 1.684 ms 1.683 ms 1.685 ms
3 137.221.105.12 (137.221.105.12) 1.529 ms 1.541 ms 1.544 ms
4 137.221.66.20 (137.221.66.20) 1.621 ms 1.632 ms 1.633 ms
5 137.221.83.68 (137.221.83.68) 31.281 ms 31.285 ms 31.289 ms
6 137.221.65.68 (137.221.65.68) 31.256 ms 30.530 ms 30.492 ms
7 137.221.65.1 (137.221.65.1) 30.484 ms 30.492 ms 30.493 ms
8 137.221.65.7 (137.221.65.7) 30.466 ms 30.484 ms 30.484 ms
9 137.221.65.116 (137.221.65.116) 30.384 ms 30.762 ms 30.766 ms
10 137.221.65.41 (137.221.65.41) 30.314 ms 30.608 ms 30.441 ms
11 137.221.73.32 (137.221.73.32) 30.791 ms 30.569 ms 30.556 ms
12 six2.gci(.)net (206.81.81.63) 30.016 ms 30.185 ms 30.283 ms
13 * * *
14 * * *
15 * * *

24/08/2019 08:55:15 UTC

TRACEROUTE:
traceroute to 24.237.98.27 (24.237.98.27), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.738 ms 0.800 ms 0.810 ms
2 24.105.18.3 (24.105.18.3) 2.157 ms 2.165 ms 2.174 ms
3 137.221.105.12 (137.221.105.12) 1.943 ms 1.984 ms 1.990 ms
4 137.221.66.20 (137.221.66.20) 2.039 ms 2.050 ms 2.058 ms
5 137.221.83.68 (137.221.83.68) 30.911 ms 30.938 ms 30.951 ms
6 137.221.65.68 (137.221.65.68) 30.602 ms 30.659 ms 30.640 ms
7 137.221.65.1 (137.221.65.1) 31.035 ms 31.028 ms 31.034 ms
8 137.221.65.7 (137.221.65.7) 31.092 ms 31.104 ms 31.126 ms
9 137.221.65.116 (137.221.65.116) 30.466 ms 30.946 ms 30.963 ms
10 137.221.65.41 (137.221.65.41) 30.593 ms 30.169 ms 30.468 ms
11 137.221.73.32 (137.221.73.32) 30.322 ms 30.281 ms 30.429 ms
12 six2.gci(.)net (206.81.81.63) 29.942 ms 30.081 ms 30.449 ms
13 * * *
14 * * *
15 * * *

24/08/2019 08:55:15 UTC

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

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

24/08/2019 08:55:15 UTC

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

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

24/08/2019 08:55:15 UTC

MTR:
Start: Sat Aug 24 08:55:15 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 0.8 0.5 3.0 0.6
3.|-- 137.221.105.16 0.0% 10 1.0 1.0 0.7 1.2 0.0
4.|-- 137.221.66.18 0.0% 10 45.6 6.4 0.9 45.6 13.9
5.|-- 137.221.83.66 0.0% 10 30.2 30.2 30.1 30.4 0.0
6.|-- 137.221.65.68 0.0% 10 48.9 74.3 30.1 208.1 62.9
7.|-- 137.221.65.1 0.0% 10 175.3 110.5 30.2 607.7 180.3
8.|-- 137.221.65.7 0.0% 10 30.3 30.2 30.1 30.3 0.0
9.|-- 137.221.65.116 0.0% 10 30.3 31.8 30.1 46.4 5.1
10.|-- 137.221.65.41 0.0% 10 30.3 30.2 30.0 30.4 0.0
11.|-- 137.221.73.32 0.0% 10 30.3 39.2 30.3 75.7 18.2
12.|-- six2.gci(.)net 0.0% 10 30.0 30.0 29.8 30.1 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

24/08/2019 08:55:14 UTC

MTR:
Start: Sat Aug 24 08:55:15 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 0.7 0.5 1.6 0.0
3.|-- 137.221.105.16 0.0% 10 0.9 1.0 0.8 1.2 0.0
4.|-- 137.221.66.18 0.0% 10 1.0 3.9 0.9 28.4 8.6
5.|-- 137.221.83.66 0.0% 10 30.1 33.6 30.0 61.3 9.8
6.|-- 137.221.65.68 0.0% 10 117.1 81.4 30.1 223.1 67.1
7.|-- 137.221.65.1 0.0% 10 231.8 118.5 30.0 674.8 205.4
8.|-- 137.221.65.7 0.0% 10 30.1 30.2 30.1 30.4 0.0
9.|-- 137.221.65.116 0.0% 10 30.1 35.2 30.1 80.7 16.0
10.|-- 137.221.65.41 0.0% 10 30.1 31.0 30.1 38.5 2.6
11.|-- 137.221.73.32 0.0% 10 42.0 31.4 30.2 42.0 3.7
12.|-- six2.gci(.)net 0.0% 10 30.2 30.0 29.8 30.9 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

24/08/2019 08:55:15 UTC

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

| WinMTR statistics |

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

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

| TOAST-S - 0 | 681 | 681 | 0 | 0 | 9 | 0 |

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

| 10.128.18.109 - 0 | 681 | 681 | 6 | 9 | 17 | 11 |

| 10.128.17.230 - 1 | 666 | 662 | 6 | 8 | 14 | 6 |

| 10.128.118.217 - 18 | 402 | 332 | 7 | 10 | 22 | 11 |

| 10.128.0.166 - 11 | 478 | 427 | 22 | 24 | 38 | 25 |

| 10.128.0.170 - 20 | 386 | 312 | 42 | 45 | 59 | 49 |

| 10.128.0.114 - 16 | 418 | 352 | 42 | 45 | 53 | 44 |

| six.blizzardonline’net - 0 | 681 | 681 | 43 | 48 | 106 | 44 |

| ae1-br01-eqse2.as57976’net - 0 | 681 | 681 | 67 | 72 | 173 | 68 |

| xe-0-0-0-1-br01-eqsv5.as57976’net - 0 | 681 | 681 | 67 | 72 | 168 | 92 |

| et-0-0-29-br02-eqsv5.as57976’net - 0 | 680 | 680 | 67 | 73 | 1727 | 67 |

| xe-0-0-1-1-br02-eqla1.as57976’net - 0 | 678 | 678 | 67 | 118 | 1985 | 67 |

| be2-pe01-eqla1.as57976’net - 0 | 681 | 681 | 67 | 70 | 83 | 71 |

| 24.105.30.129 - 0 | 681 | 681 | 68 | 70 | 83 | 69 |

|________________________________________________|______|______|______|______|______|______|

2

It looks like some of your traffic isn’t making it to Blizzard in the earlier tests, but in the WinMTR things look okay. Those big numbers on the Blizzard hops are because they are designed to ignore a lot of ping traffic (what these tests use) and therefore it inflates the number. What kind of latency are you seeing in game? If it’s around 83ms that sounds about right?

3

I am seeing that at the lowest ends, I think it’s around 88-95 most of the time. So it’s normal behavior?

4

Sounds normal. If I connect to LA from Florida my ping is 76-86. You’re connecting from Alaska to LA, so about 300-1200 more miles than me, and slightly higher ping than me.

5

Figured it was normal, oh well! Thanks for taking a look anyways!

6

I’m having about 44 ping before the game freezes, had some issues earlier today with lag spikes up to 3-4k ping