Next chance I get to play, I will follow @DamnVoices and report packet loss as I connect to individual ports.
I am also in Bellevue, WA on Wave Broadband and have been experiencing these issues only since the Winter Event update.
Washington WaveBroadband User currently getting f*cked by a ātier 1ā company.
Looking Glass:
PING:
PING Blizzard Blizzard 56(84) bytes of data.
ā Blizzardping statistics ā
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
17/12/2018 21:13:45 UTC
PING:
PING Blizzard Blizzard 56(84) bytes of data.
ā Blizzardping statistics ā
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
17/12/2018 21:13:45 UTC
TRACEROUTE:
traceroute to Blizzard Blizzard, 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.388 ms 1.391 ms 1.971 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
17/12/2018 21:13:45 UTC
TRACEROUTE:
traceroute to Blizzard Blizzard, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.571 ms 0.581 ms 0.590 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
17/12/2018 21:13:45 UTC
MTR:
Start: Mon Dec 17 21:13:45 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
17/12/2018 21:13:45 UTC
MTR:
Start: Mon Dec 17 21:13:45 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.4 0.2 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
17/12/2018 21:13:45 UTC
[]
[]
[]
[]
WinMTR #1
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 99 | 86 | 1 | 4 | 4 | 4 | 4 |
| 172.92.192.1 - 0 | 421 | 421 | 9 | 25 | 119 | 9 |
| cr1-camano-a-be150.bb.as11404net - 0 | 421 | 421 | 9 | 21 | 32 | 16 |
| 174.127.149.104 - 0 | 421 | 421 | 12 | 23 | 35 | 21 |
| cr1-nr-hu-t-0-6-0-21-0.bb.as11404net - 0 | 421 | 421 | 10 | 23 | 36 | 16 |
| cr2-sea-a-hu-0-6-0-20-0.bb.as11404net - 0 | 421 | 421 | 9 | 22 | 35 | 27 |
| cr2-sea-b-be1.bb.as11404net - 0 | 421 | 421 | 12 | 24 | 42 | 14 |
| six.blizzardonlinenet - 0 | 421 | 421 | 11 | 23 | 52 | 24 |
| ae1-br01-eqse2.as57976net - 0 | 421 | 421 | 39 | 52 | 186 | 48 |
| xe-0-0-0-1-br01-eqsv5.as57976net - 0 | 421 | 421 | 37 | 52 | 102 | 45 |
| xe-0-0-1-1-br02-eqla1.as57976net - 1 | 410 | 409 | 36 | 82 | 4408 | 36 |
| be2-pe02-eqla1.as57976net - 4 | 366 | 352 | 34 | 49 | 65 | 46 |
| lax-eqla1-ia-bons-03.as57976net - 0 | 421 | 421 | 36 | 49 | 71 | 42 |
| 24.105.30.129 - 0 | 421 | 421 | 33 | 50 | 71 | 48 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
[]
[]
[]
MTR #2
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.0.1 - 99 | 138 | 2 | 2 | 3 | 4 | 2 |
| 172.92.192.1 - 1 | 659 | 654 | 0 | 28 | 1332 | 19 |
| cr1-camano-a-be150.bb.as11404net - 1 | 659 | 654 | 0 | 24 | 1496 | 16 |
| 174.127.149.104 - 1 | 659 | 654 | 0 | 24 | 1528 | 21 |
| cr1-nr-hu-t-0-6-0-21-0.bb.as11404net - 1 | 659 | 654 | 0 | 24 | 42 | 24 |
| cr2-sea-a-hu-0-6-0-20-0.bb.as11404net - 1 | 662 | 658 | 9 | 28 | 1555 | 19 |
| cr2-sea-b-be1.bb.as11404net - 1 | 659 | 654 | 0 | 26 | 1456 | 29 |
| six.blizzardonlinenet - 1 | 663 | 659 | 0 | 31 | 1208 | 20 |
| ae1-br01-eqse2.as57976net - 1 | 663 | 659 | 0 | 55 | 1291 | 42 |
| xe-0-0-0-1-br01-eqsv5.as57976net - 1 | 663 | 659 | 0 | 56 | 1504 | 47 |
| 137.221.65.6 - 1 | 652 | 647 | 33 | 74 | 4733 | 41 |
| be2-pe02-eqla1.as57976net - 4 | 602 | 583 | 33 | 58 | 1555 | 44 |
| lax-eqla1-ia-bons-03.as57976net - 1 | 659 | 654 | 0 | 54 | 1246 | 53 |
| 24.105.30.129 - 1 | 659 | 654 | 0 | 49 | 69 | 49 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
[[WinMTR3]]
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.0.1 - 100 | 158 | 1 | 3 | 3 | 3 | 3 |
| 172.92.192.1 - 0 | 782 | 782 | 10 | 25 | 126 | 16 |
| cr1-camano-a-be150.bb.as11404net - 0 | 782 | 782 | 8 | 20 | 43 | 20 |
| 174.127.149.104 - 0 | 782 | 782 | 7 | 22 | 129 | 25 |
| cr1-nr-hu-t-0-6-0-21-0.bb.as11404net - 0 | 782 | 782 | 11 | 23 | 46 | 28 |
| cr2-sea-a-hu-0-6-0-20-0.bb.as11404net - 0 | 782 | 782 | 11 | 23 | 44 | 29 |
| cr2-sea-b-be1.bb.as11404net - 0 | 782 | 782 | 7 | 23 | 58 | 24 |
| six.blizzardonlinenet - 0 | 782 | 782 | 11 | 24 | 65 | 33 |
| ae1-br01-eqse2.as57976net - 0 | 782 | 782 | 34 | 51 | 162 | 43 |
| xe-0-0-0-1-br01-eqsv5.as57976net - 1 | 779 | 778 | 34 | 52 | 212 | 62 |
| xe-0-0-1-1-br02-eqla1.as57976net - 0 | 782 | 782 | 33 | 53 | 1276 | 45 |
| be2-pe02-eqla1.as57976net - 4 | 675 | 648 | 34 | 49 | 83 | 52 |
| lax-eqla1-ia-bons-03.as57976net - 0 | 782 | 782 | 37 | 51 | 137 | 53 |
| 24.105.30.129 - 0 | 782 | 782 | 33 | 49 | 76 | 57 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
+1 similar issues from Seattle, on WaveG. Additional information posted into the Bug Forums (oops): LAT Spikes During Normal Play. Will run debug tools and report back.
From what I can tell, the training grounds may connect you to geographically remote server ā if you look at the advanced network diagnostics graphs, you can see the server IP; by repeatedly joining, leaving, then waiting a couple minutes for training grounds, I have gotten some AWS servers based in Brazil and Australia.
In this case, the PING should be naturally higher (the servers are further away from you) ā this however doesnāt necessarily mean higher packet loss, i.e. the connection should still be stable. What we seem to be observing is that the underlying connection itself is unstable.
Update: I can confirm @DamnVoices data.
Repeatedly spamming training ground connections and filtering out non-LAX1 connections, I am able to find several problematic occurrences, listed below.
(Looks like I canāt post any URLs yet, which means the hostnames picked up by MTR / LookingGlass will trigger sanitization ā Iāve replaced the period preceding the gTLD with a comma. Apologies.)
Stray Observations
- Anecdotally, the average LAT metric (from detailed network stats, not the LAT reported alongside FPS / VRM, etc.) increases slightly if I do additional actions, e.g. roll around, fan the hammer, high noon.
- The average LAT metric observed in-game is ~30ms for a problematic game, way above the normal <1ms OK average (from below).
- I have not had a chance to look at LookingGlass / MTR during a problematic game ā this is only for training ground.
- I have not looked at LOSS IN during a problematic game.
- Connection issues are persistent through the entire connection duration (e.g. for the whole 15m I stayed connected to the training ground).
- xe-0-0-1-1-br02-eqla1.as57976,net shows up in both MTR reports with a couple of packet losses; however, Overwatch hosts with different ports but the same IP would trigger the same MTR, which indicates this server may not be the root problem.
EDIT
If I keep a connection to a problematic server open, after about half an hour, the connection state changes (for the worse):
| HOST | START | STOP | NETWORK LAT | LOSS IN | NOTES |
|---|---|---|---|---|---|
| LAX1 24.105.15.227:26578 | 22:30 PST | NEXT | LAT 0 / 2 / (33 - 50) | LOSS IN ~10% | NULL |
| LAX1 24.105.15.227:26578 | 23:00 PST | 23:04 PST | LAT 0 / 10 / (80 - 100) | LOSS IN ~10% | [3] |
Some update would be appreciated, thanks.
| HOST | START | STOP | NETWORK LAT | LOSS IN | NOTES |
|---|---|---|---|---|---|
| LAX1 24.105.15.197:26576 | 21:28 PST | NEXT | LAT 0 / 0.1 / 16 (OK) | LOSS IN ~0% (OK) | NULL |
| LAX1 24.105.15.205:26527 | 21:32 PST | NEXT | OK | OK | NULL |
| LAX1 24.105.15.227:26584 | 21:34 PST | NEXT | OK | OK | NULL |
| LAX1 24.105.15.227:26508 | 21:35 PST | NEXT | OK | OK | NULL |
| LAX1 24.105.15.227:26578 | 21:36 PST | NEXT | OK | OK | NULL |
| LAX1 24.105.10.147:26562 | 21:36 PST | NEXT | LAT 0 / 2 / (33 - 50) | LOSS IN ~10% | [1] |
| LAX1 24.105.15.205:26519 | 21:50 PST | NEXT | OK | OK | NULL |
| LAX1 24.105.15.227:26571 | 21:52 PST | 22:04 PST | LAT 0 / 2 / (33 - 50) | LOSS IN ~10% | [2] |
[1] LookingGlass
TRACEROUTE:
traceroute to HEINEBOREL, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.264 ms 0.236 ms 0.233 ms Blizzard(24.105.18.2) 0.531 ms 0.583 ms 0.723 ms
3 137.221.105.14 (137.221.105.14) 0.542 ms 0.636 ms 0.730 ms
4 137.221.66.18 (137.221.66.18) 0.565 ms 0.564 ms 0.747 ms
5 137.221.83.66 (137.221.83.66) 13.131 ms 13.172 ms 13.173 ms
6 137.221.65.68 (137.221.65.68) 12.775 ms 12.901 ms 12.836 ms
7 137.221.65.1 (137.221.65.1) 13.236 ms 13.517 ms 13.503 ms
8 137.221.65.7 (137.221.65.7) 12.954 ms 12.953 ms 12.948 ms
9 137.221.70.32 (137.221.70.32) 12.695 ms 12.557 ms 12.546 ms
10 cr1-sjo-p200.bb.spectrumnet,us (206.223.116.182) 12.562 ms 12.905 ms 13.090 ms
11 cr1-pdx-a-hu-0-7-0-1.bb.as11404,net (192.175.28.239) 33.273 ms 33.418 ms 33.324 ms
12 cr2-sea-a-hu-0-7-0-6.bb.as11404,net (174.127.141.70) 32.867 ms 36.345 ms 53.901 ms
13 cr1-sea-be100-4000.bb.as54858,net (216.243.28.206) 33.170 ms 33.180 ms 33.184 ms
14 HEINEBOREL 34.542 ms 34.444 ms 34.875 ms
18/12/2018 05:40:38 UTC
TRACEROUTE:
traceroute to HEINEBOREL, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.341 ms 0.343 ms 0.345 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 condointernet-2-sea-10000m.demarc.spectrumnet,us (216.243.24.106) 32.429 ms 32.445 ms 32.449 ms
14 HEINEBOREL 33.962 ms 33.984 ms 33.987 ms
18/12/2018 05:40:38 UTC
MTR:
Start: Tue Dec 18 05:40:38 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18/12/2018 05:40:38 UTC
MTR:
Start: Tue Dec 18 05:40:38 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.2 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18/12/2018 05:40:38 UTC
[1] WinMTR
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| HEINEBOREL - 0 | 415 | 415 | 0 | 0 | 11 | 0 |
| HEINEBOREL_ISP_GATEWAY - 0 | 415 | 415 | 1 | 1 | 55 | 1 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| agg2-sea-b-t9-4.bb.spectrumnet,us - 0 | 415 | 415 | 0 | 1 | 11 | 1 |
| six.blizzardonline,net - 0 | 415 | 415 | 0 | 1 | 25 | 1 |
| ae1-br01-eqse2.as57976,net - 0 | 415 | 415 | 26 | 28 | 162 | 26 |
| xe-0-0-0-1-br01-eqsv5.as57976,net - 0 | 415 | 415 | 21 | 23 | 144 | 22 |
| xe-0-0-1-1-br02-eqla1.as57976,net - 1 | 386 | 383 | 26 | 86 | 4306 | 4175 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 83 | 0 | 0 | 0 | 0 | 0 |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
[2] LookingGlass
TRACEROUTE:
traceroute to HEINEBOREL, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.301 ms 0.278 ms 0.278 ms Blizzard(24.105.18.2) 1.064 ms 1.080 ms 1.084 ms
3 137.221.105.14 (137.221.105.14) 0.652 ms 0.723 ms 0.801 ms
4 137.221.66.18 (137.221.66.18) 1.144 ms 1.163 ms 1.165 ms
5 137.221.83.66 (137.221.83.66) 12.859 ms 12.875 ms 12.877 ms
6 137.221.65.68 (137.221.65.68) 12.728 ms 13.211 ms 13.193 ms
7 137.221.65.1 (137.221.65.1) 12.990 ms 12.974 ms 12.970 ms
8 137.221.65.7 (137.221.65.7) 12.946 ms 12.800 ms 12.787 ms
9 137.221.70.32 (137.221.70.32) 12.669 ms 12.787 ms 12.775 ms
10 cr1-sjo-p200.bb.spectrumnet,us (206.223.116.182) 12.836 ms 20.642 ms 20.069 ms
11 cr1-pdx-a-hu-0-7-0-1.bb.as11404,net (192.175.28.239) 33.297 ms 33.531 ms 33.356 ms
12 cr2-sea-a-hu-0-7-0-6.bb.as11404,net (174.127.141.70) 33.273 ms 33.297 ms 33.297 ms
13 cr1-sea-be100-4000.bb.as54858,net (216.243.28.206) 33.216 ms 33.255 ms 33.241 ms
14 HEINEBOREL 34.198 ms 34.135 ms 34.490 ms
18/12/2018 05:54:06 UTC
TRACEROUTE:
traceroute to HEINEBOREL, 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.068 ms 2.512 ms 2.513 ms Blizzard(24.105.18.2) 2.471 ms 2.476 ms 2.479 ms
3 137.221.105.14 (137.221.105.14) 2.575 ms 2.577 ms 2.579 ms
4 137.221.66.18 (137.221.66.18) 2.500 ms 2.522 ms 2.536 ms
5 137.221.83.66 (137.221.83.66) 13.611 ms 13.620 ms 13.624 ms
6 137.221.65.68 (137.221.65.68) 13.637 ms 14.220 ms 14.225 ms
7 137.221.65.1 (137.221.65.1) 14.471 ms 14.488 ms 14.474 ms
8 137.221.65.7 (137.221.65.7) 13.482 ms 13.448 ms 13.438 ms
9 137.221.70.32 (137.221.70.32) 17.080 ms 15.790 ms 15.770 ms
10 cr1-sjo-p200.bb.spectrumnet,us (206.223.116.182) 15.155 ms 12.794 ms 12.935 ms
11 cr1-pdx-a-hu-0-7-0-1.bb.as11404,net (192.175.28.239) 33.298 ms 33.280 ms 33.053 ms
12 cr2-sea-a-hu-0-7-0-6.bb.as11404,net (174.127.141.70) 37.254 ms 33.256 ms 33.323 ms
13 cr1-sea-be100-4000.bb.as54858,net (216.243.28.206) 33.686 ms 33.136 ms 33.122 ms
14 HEINEBOREL 36.864 ms 36.384 ms 36.344 ms
18/12/2018 05:54:06 UTC
MTR:
Start: Tue Dec 18 05:54:06 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.6 0.0 Blizzard 0.0% 10 0.6 0.6 0.5 0.8 0.0
3.|-- 137.221.105.14 0.0% 10 0.7 0.6 0.5 0.7 0.0
4.|-- 137.221.66.18 0.0% 10 0.8 0.7 0.5 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 15.4 14.8 12.8 29.6 5.2
6.|-- 137.221.65.68 0.0% 10 12.8 12.9 12.7 13.9 0.0
7.|-- 137.221.65.1 0.0% 10 12.9 13.7 12.7 20.6 2.3
8.|-- 137.221.65.7 0.0% 10 12.9 17.1 12.7 55.2 13.4
9.|-- 137.221.70.32 0.0% 10 12.6 12.7 12.6 12.8 0.0
10.|-- cr1-sjo-p200.bb.spectrumnet,us 0.0% 10 12.9 12.8 12.6 13.1 0.0
11.|-- cr1-pdx-a-hu-0-7-0-1.bb.as11404,net 0.0% 10 33.3 33.3 33.2 33.6 0.0
12.|-- cr2-sea-a-hu-0-7-0-6.bb.as11404,net 0.0% 10 32.9 33.0 32.8 33.8 0.0
13.|-- cr1-sea-be100-4000.bb.as54858,net 0.0% 10 33.0 33.1 33.0 33.4 0.0
14.|-- HEINEBOREL 0.0% 10 33.9 34.1 33.9 34.7 0.0
18/12/2018 05:54:06 UTC
MTR:
Start: Tue Dec 18 05:54:07 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.6 0.6 0.5 0.6 0.0
3.|-- 137.221.105.14 0.0% 10 0.7 0.6 0.5 0.7 0.0
4.|-- 137.221.66.18 0.0% 10 0.6 1.2 0.6 5.9 1.6
5.|-- 137.221.83.66 0.0% 10 13.1 14.7 12.8 30.5 5.5
6.|-- 137.221.65.68 0.0% 10 12.9 12.9 12.6 13.4 0.0
7.|-- 137.221.65.1 0.0% 10 12.8 14.6 12.7 28.6 4.9
8.|-- 137.221.65.7 0.0% 10 13.0 16.4 12.8 48.7 11.3
9.|-- 137.221.70.32 0.0% 10 12.6 12.7 12.5 13.1 0.0
10.|-- cr1-sjo-p200.bb.spectrumnet,us 0.0% 10 13.0 13.0 12.6 14.0 0.3
11.|-- cr1-pdx-a-hu-0-7-0-1.bb.as11404,net 0.0% 10 33.6 33.3 33.2 33.7 0.0
12.|-- cr2-sea-a-hu-0-7-0-6.bb.as11404,net 0.0% 10 33.0 33.0 32.6 33.2 0.0
13.|-- cr1-sea-be100-4000.bb.as54858,net 0.0% 10 33.3 33.2 33.0 33.4 0.0
14.|-- HEINEBOREL 0.0% 10 34.8 34.9 34.2 38.4 1.2
18/12/2018 05:54:06 UTC
[2] MTR
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| HEINEBOREL - 0 | 455 | 455 | 0 | 0 | 10 | 5 |
| HEINEBOREL_ISP_GATEWAY - 0 | 455 | 455 | 1 | 1 | 22 | 2 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| agg2-sea-b-t9-4.bb.spectrumnet,us - 0 | 455 | 455 | 0 | 1 | 11 | 1 |
| six.blizzardonline,net - 0 | 455 | 455 | 0 | 1 | 20 | 1 |
| ae1-br01-eqse2.as57976,net - 0 | 455 | 455 | 26 | 27 | 146 | 26 |
| xe-0-0-0-1-br01-eqsv5.as57976,net - 0 | 455 | 455 | 21 | 24 | 109 | 22 |
| xe-0-0-1-1-br02-eqla1.as57976,net - 1 | 441 | 440 | 26 | 67 | 4872 | 26 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
[3] WinMTR
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| HEINEBOREL - 0 | 325 | 325 | 0 | 0 | 7 | 0 |
| HEINEBOREL_ISP_GATEWAY - 0 | 325 | 325 | 1 | 2 | 70 | 2 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| agg2-sea-b-t9-4.bb.spectrumnet,us - 0 | 325 | 325 | 0 | 1 | 7 | 1 |
| six.blizzardonline,net - 0 | 325 | 325 | 0 | 1 | 38 | 1 |
| ae1-br01-eqse2.as57976,net - 0 | 325 | 325 | 26 | 27 | 64 | 40 |
| xe-0-0-0-1-br01-eqsv5.as57976,net - 0 | 325 | 325 | 21 | 23 | 144 | 22 |
| xe-0-0-1-1-br02-eqla1.as57976,net - 0 | 325 | 325 | 26 | 41 | 894 | 47 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I should add, all my data is taken from Competitive playlist. Not training ground.
PACKET LOSS IS STILL HAPPENING. Came back hard today. 30% INBOUND. and now there is added outbound loss of 2-3% concurrently. I will try to log whats going on this afternoon with this continuous mess. over 2 months now off and on. Terrible experience. Blizzard isnāt doing anything. Wave isnāt doing anything. BLIZZARD CAN YOU NOT HELP OUT AND WORK WITH WAVE ON THIS LIKE YOU DID WITH WAVE PREVIOUSLY when this was an issue? Like I said, no one seems to want to help from either end, nor claim responsibility.
IDK what to tell all of you but this issue is really troublesome. Iām almost inclined to quit playing OW all together, just not worth the effort anymore sadly.
Iāve logged and logged, trace route and mtr-ed. Looking glass and lots of my own network engineer experience has gone into presenting so much information over the months. Iāve ran my ticket into the ground reaching the MAX amount of replies the ticket could accept. Had to open new tickets and go through merges that CS has been doing every time I need to reply with more info. I have been supporting this thread and gone beyond in helping provide important trace info and observations and i the end, CS still says they donāt know and donāt have enough info to contact WAVE.
SO WHATāS THE DEAL BLIZZARD CS? PLEASE ANSWER AS IF YOU CARE.
SORRY Iām now a little beyond frustrated at the commitment to fixing this issue.
1 Like
OK MORE TESTING:
ATTENTION BLIZZARD CS!!!
This issue is 100% Overwatch Server IP/PORT connection related. Period, regardless of any other info implicating WAVE ISP. This is IMPORTANT!!!
Why do I say this? Well lookā¦
NOTE: ALL CONNECTIONS ARE CONTINUOUS UNTIL I MANUALLY DISCONNECT. Also, Looking Glass could not produce
a proper trace/mtr result during this time. Posted below as well.
I kept establishing connections to LAX1 continuously for 2 minute durations. The 2 times problematic server connections were made, packet loss was evident immediately upon connection, persisting without end until the connection was manually terminated by me. I went one step further. When encountering a problem server IP/PORT, I left the connection running for 10 minutes instead of 2 min, so I could further prove that the packet loss is connection oriented for the longer duration. Then upon connecting to a following server IP/PORT right after this, there was ZERO packet loss from beginning to end. Also run for 10 min PROBLEM FREE.
BLIZZARD SERVERS ARE DIRECTLY RESPONSIBLE HERE aside from any other issues that may or may not be present implicating WAVE customers.
Intermediate routing issues or issues with ISP vs intermediary peering partners WOULD NOT CREATE this kind of connection based problem that falls on Blizzards end. SO CS please look into this, I cannot stress this data Iāve collected meticulously.
24.105.15.227:26565 NO PROBLEM FOR DURATION OF CONNECTION 3:00-3:02 (2 min in training) PM PST 12-18-18
24.105.15.227:26504 NO PROBLEM FOR DURATION OF CONNECTION 3:02-3:04 (2 min in training) PM PST 12-18-18
24.105.11.2:26548 NO PROBLEM FOR DURATION OF CONNECTION 3:04-3:06 (2 min in training) PM PST 12-18-18
24.105.11.2:26512 NO PROBLEM FOR DURATION OF CONNECTION 3:06-3:08 (2 min in training) PM PST 12-18-18
24.105.15.227:26540 NO PROBLEM FOR DURATION OF CONNECTION 3:08-3:10 (2 min in training) PM PST 12-18-18
24.105.15.227:26581 NO PROBLEM FOR DURATION OF CONNECTION 3:10-3:12 (2 min in training) PM PST 12-18-18
24.105.11.2:26529 !!15-20% PACKET LOSS!!! FOR DURATION OF CONNECTION 3:12-3:22 (10 min in training) PM PST 12-18-18
24.105.15.227:26551 NO PROBLEM FOR DURATION OF CONNECTION 3:22-3:32 (10 min in training) PM PST 12-18-18
24.105.15.227:26519 NO PROBLEM FOR DURATION OF CONNECTION 3:32-3:34 (2 min in training) PM PST 12-18-18
24.105.11.2:26564 NO PROBLEM FOR DURATION OF CONNECTION 3:34-3:36 (2 min in training) PM PST 12-18-18
24.105.11.2:26518 NO PROBLEM FOR DURATION OF CONNECTION 3:36-3:38 (2 min in training) PM PST 12-18-18
24.105.11.2:26547 NO PROBLEM FOR DURATION OF CONNECTION 3:38-3:40 (2 min in training) PM PST 12-18-18
24.105.11.2:26547 !!15-20% PACKET LOSS!!! FOR DURATION OF CONNECTION 3:40-3:50 (10 min in training) PM PST 12-18-18
24.105.11.2:26540 NO PROBLEM FOR DURATION OF CONNECTION 3:50-3:52 (2 min in training) PM PST 12-18-18
24.105.15.227:26596 NO PROBLEM FOR DURATION OF CONNECTION 3:52-3:54 (2 min in training) PM PST 12-18-18
Looking Glass:
TRACEROUTE:
traceroute to 76.14.108.xxx (76.14.108.xxx), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.254 ms 0.252 ms 0.900 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
18/12/2018 23:44:34 UTC
TRACEROUTE:
traceroute to 76.14.108.xxx (76.14.108.xxx), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.256 ms 0.255 ms 0.258 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
18/12/2018 23:44:34 UTC
MTR:
Start: Tue Dec 18 23:44:34 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18/12/2018 23:44:34 UTC
MTR:
Start: Tue Dec 18 23:44:34 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.2 0.2 0.3 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18/12/2018 23:44:34 UTC
Hey yāall,
Just wanted to let you know that we are collecting these reports and will be getting this further investigated. Thanks for letting us know!
Thanks for the reply!
Iām sure that we will be happy to help with any other diagnostics we can run from our end.
Whatās the time frame for WA customers?
Thread was made Nov 23rd.
2 Likes
I found that this situation started in October. At the beginning, latency only occasionally delayed to 200, and then it was normal. Until now, a whole game could not be normal. The latency was over 200 and it was extremely unstable. It was completely impossible to play. I really like this game, I play overwatch when it is released. Even if I came to another country, I still bought a new account game. But this game has a lot of major problems. and canāt fix it until now!!!
. I am very disappointed now
I have to give up this game.
BTW I know overwatch team never care about report record of the competitive mode, so I give up
good work
12-19-18
NOTE: ALL CONNECTIONS ARE CONTINUOUS UNTIL I MANUALLY DISCONNECT. Connections with packet loss were run
for 10 minutes straight showing loss throughout the connection. If the following connection was free of
issues it was also run for 10 minutes showing continuous good connection for 10 minutes until disconnect.
LAX1 24.105.11.0:26513 NO PROBLEM FOR DURATION OF CONNECTION 1:00-1:02 PM PST (2 min in training) 12-19-18
LAX1 24.105.11.0:26520 NO PROBLEM FOR DURATION OF CONNECTION 1:02-1:04 PM PST (2 min in training) 12-19-18
LAX1 24.105.115.227:26519 NO PROBLEM FOR DURATION OF CONNECTION 1:04-1:06 PM PST (2 min in training) 12-19-18
LAX1 24.105.15.227:26545 !!!11-17% PACKET LOSS!!! FOR DURATION OF CONNECTION 1:06-1:16 PM PST (10 min in training) 12-19-18
LAX1 24.105.11.0:26533 NO PROBLEM FOR DURATION OF CONNECTION 1:16-1:26 PM PST (10 min in training) 12-19-18
LAX1 24.105.115.227:26590 NO PROBLEM FOR DURATION OF CONNECTION 1:26-1:28 PM PST (2 min in training) 12-19-18
LAX1 24.105.115.227:26531 NO PROBLEM FOR DURATION OF CONNECTION 1:28-1:30 PM PST (2 min in training) 12-19-18
LAX1 24.105.115.227:26513 NO PROBLEM FOR DURATION OF CONNECTION 1:30-1:32 PM PST (2 min in training) 12-19-18
LAX1 24.105.115.227:26550 NO PROBLEM FOR DURATION OF CONNECTION 1:32-1:34 PM PST (2 min in training) 12-19-18
LAX1 24.105.11.0:26540 NO PROBLEM FOR DURATION OF CONNECTION 1:34-1:36 PM PST (2 min in training) 12-19-18
LAX1 24.105.11.0:26514 !!!10-15% PACKET LOSS!!! 1:36-1:46 PM PST (10 min in training) 12-19-18
LAX1 24.105.115.227:26552 NO PROBLEM FOR DURATION OF CONNECTION 1:46-1:56 PM PST (10 min in training) 12-19-18
LAX1 24.105.115.227:26543 NO PROBLEM FOR DURATION OF CONNECTION 1:56-1:58 PM PST (10 min in training) 12-19-18
LAX1 24.105.11.0:26538 NO PROBLEM FOR DURATION OF CONNECTION 1:58-2:00 PM PST (2 min in training) 12-19-18
Note: One thing that is good about this issue being connection based to Blizzards servers is that I can check upon connection for Packet Loss and if there is none I stay for a good game, if there is loss I leave and restart a new game until I make a good connection. Once in game without packet loss the connection stays problem free til the end. Itās cumbersome and you suffer from leaver penalties of course, but itās all i have left to try and play. FORGET COMP.
Thank you for chiming in and letting us know about this. Very interesting that you too notice the same symptoms exactly. I am told that Blizzard GNOC monitors this thread for info, as described to me by James form CS, who also responded to this thread a few posts back.
This info is golden because it adds another dimension of information that seems to diverge from this problem being completely ISP or Intermediary 3rd party (peering partner) routing issue.
If blizzard is seriously pushing this to be primarily ISP related issue, it is imperative they are able to distinguish this connection related information provided them first as it appears to be THEIR issue affecting much more than Wave ISP. Lets start with this first.
Thanks again for the update, much appreciated!
Iāve been getting more problematic games lately. I posted earlier in the thread but hereās my latest WinMTR:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| www,routerlogin,com - 0 | 450 | 450 | 0 | 0 | 9 | 0 |
| 172.16.0.1 - 0 | 450 | 450 | 0 | 0 | 10 | 2 |
| 108.161.17.121 - 0 | 450 | 450 | 1 | 2 | 36 | 1 |
| hurricaneelectric.nwax,net - 0 | 450 | 450 | 1 | 3 | 38 | 1 |
| 100ge14-1.core1.sea1.he,net - 1 | 446 | 445 | 4 | 4 | 11 | 4 |
| eqix-se2.blizzardentertainment,com - 0 | 450 | 450 | 5 | 6 | 43 | 5 |
| ae1-br01-eqse2.as57976,net - 0 | 450 | 450 | 27 | 29 | 103 | 27 |
| xe-0-0-0-1-br01-eqsv5.as57976,net - 0 | 450 | 450 | 21 | 23 | 130 | 21 |
| xe-0-0-1-1-br02-eqla1.as57976,net - 0 | 450 | 450 | 27 | 34 | 163 | 30 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
^^ Thanks for the added info.
Just a note, to everyone actually. Since the packet loss occurring here is most part INBOUND PACKET LOSS, which means the packets are being lost on the preferred routing BACK to you from Bilzzards Servers. The routing used on the return route is where the primary scrutiny lies. Routing TO a Server can be VERY different than the routing back.
Traceroute and WinMTR etc only show routing to a destination.
Preferably everyone can also include a MTR/Trace from Overwatch Servers back to your IP using Blizzardās Looking Glass here, just choose United States and Overwatch from the drop downs:
us-looking-glass.battle. net
^^Blizz wont let me post urlās even to their own service, sighā¦ added an extra space after the dot
That was super helpful. This makes it look to be my ISPās fault, at least in my case.
MTR:
Start: Fri Dec 21 01:22:46 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.6 0.6 0.5 0.7 0.0
3.|-- 137.221.105.10 0.0% 10 0.6 0.6 0.5 0.8 0.0
4.|-- 137.221.66.20 0.0% 10 0.6 0.6 0.5 0.8 0.0
5.|-- 137.221.83.68 0.0% 10 12.9 16.9 12.9 40.0 8.9
6.|-- 137.221.65.68 0.0% 10 13.0 17.7 12.8 37.9 9.1
7.|-- 137.221.65.1 0.0% 10 12.8 13.9 12.8 23.4 3.3
8.|-- 137.221.65.7 0.0% 10 12.9 13.2 12.8 16.1 1.0
9.|-- 137.221.70.32 0.0% 10 12.7 14.1 12.5 26.4 4.3
10.|-- as11404.sfmix,org 0.0% 10 14.5 14.8 14.5 16.1 0.3
11.|-- cr1-200p-b-be-4.as11404,net 10.0% 10 14.8 14.7 14.4 14.8 0.0
12.|-- cr1-9greatoaks-hu-0-6-0-21-0.bb.as11404,net 0.0% 10 14.1 14.3 14.1 14.5 0.0
13.|-- cr1-pdx-a-hu-0-7-0-1.bb.as11404,net 0.0% 10 34.7 34.8 34.6 35.1 0.0
14.|-- FiberSphere-10000M-PDX.demarc.spectrumnet,us 0.0% 10 34.7 37.5 34.4 64.3 9.4
15.|-- pdx-core-b.fibersphere,net 0.0% 10 34.2 35.4 33.9 47.5 4.2
16.|-- 108.161.17.122 60.0% 10 35.0 37.8 34.6 46.9 6.0
17.|-- x.x.x.x 0.0% 10 35.2 35.5 34.9 36.8 0.3
Spamming a couple of LookingGlass lookups ā it looks like the route between Blizzard and me changes pretty regularly. This is one of the runs in which I can actually see the route taken.
Unless Iām mistaken, 137.221.x.x is in the Netherlands; considering Iām in Seattle, this seems like a rather odd path to take for a CA -> WA route. Iām assuming that this path is the same path that any outbound Overwatch packets would have taken.
Assuming I have traffic routing through Europe regularly, this may explain some of the issues that weāve been having. Can anyone in CA confirm the results? @DamnVoices I see Netherland hops in your LookingGlass probes as wellā¦
The other outcome for a LookingGlass probe is useless, as all traffic is blocked along the path, aside from the endpoints. It seems like the ratio of blocked:useful probes from LookingGlass matches the ratio of good:bad Overwatch connection attempts. Maybe the blocked traceroutes are going through a more sensible path?
If the route is pre-calculated for the life of a Overwatch server connection, it may also explain the static nature of the connection, whether good or bad.
TRACEROUTE:
traceroute to HEINEBOREL, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.303 ms 0.274 ms 0.271 ms Blizzard(24.105.18.2) 0.537 ms 0.586 ms 0.671 ms
3 137.221.105.14 (137.221.105.14) 0.906 ms 0.908 ms 0.906 ms
4 137.221.66.18 (137.221.66.18) 0.933 ms 0.936 ms 0.947 ms
5 137.221.83.66 (137.221.83.66) 12.872 ms 12.882 ms 12.881 ms
6 * * *
7 * * *
8 137.221.65.7 (137.221.65.7) 12.810 ms 12.968 ms 12.942 ms
9 137.221.70.32 (137.221.70.32) 12.910 ms 12.630 ms 12.595 ms
10 cr1-sjo-p200.bb.spectrumnet.us (206.223.116.182) 12.745 ms 12.819 ms 12.802 ms
11 cr1-pdx-a-hu-0-7-0-1.bb.as11404.net (192.175.28.239) 33.240 ms 33.130 ms 33.423 ms
12 cr2-sea-a-hu-0-7-0-6.bb.as11404.net (174.127.141.70) 33.075 ms 33.130 ms 33.023 ms
13 cr1-sea-be100-4000.bb.as54858.net (216.243.28.206) 33.100 ms 32.971 ms 33.098 ms
14 HEINEBOREL 34.095 ms 34.080 ms 33.777 ms
21/12/2018 03:15:26 UTC
--------------------
TRACEROUTE:
traceroute to HEINEBOREL, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.266 ms 0.262 ms 0.264 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 condointernet-2-sea-10000m.demarc.spectrumnet.us (216.243.24.106) 32.648 ms 32.667 ms 32.672 ms
14 HEINEBOREL 33.352 ms 33.471 ms 33.539 ms
21/12/2018 03:15:26 UTC
--------------------
MTR:
Start: Fri Dec 21 03:15:26 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21/12/2018 03:15:26 UTC
--------------------
MTR:
Start: Fri Dec 21 03:15:26 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21/12/2018 03:15:26 UTC
--------------------