Gorrnar,
Just for clarification’s sake, you don’t want to run two instances of WinMTR at a time. It can interfere with itself. Better to run one after the other for about 5 minutes, and no need to post it unless you’re still having problems.
Cox, 300 preferred customer. OKC based .
Blockquote
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus. com - 0 | 292 | 292 | 0 | 0 | 1 | 0 |
| 10.6.16.1 - 0 | 292 | 292 | 5 | 8 | 17 | 8 |
| 68.4.15.10 - 0 | 292 | 292 | 6 | 9 | 19 | 6 |
| ip68-4-11-98.oc.oc.cox .net - 0 | 292 | 292 | 8 | 13 | 23 | 20 |
| 68.1.1.61 - 0 | 292 | 292 | 9 | 15 | 85 | 11 |
| 68.105.30.130 - 0 | 292 | 292 | 11 | 15 | 45 | 12 |
| ae1-br01-eqla1.as57976 .net - 0 | 292 | 292 | 16 | 23 | 127 | 17 |
| et-0-0-2-br01-swlv10.as57976 .net - 0 | 292 | 292 | 16 | 23 | 108 | 55 |
| et-0-0-31-pe02-swlv10.as57976 .net - 0 | 292 | 292 | 16 | 19 | 39 | 25 |
| las-swlv10-ia-bons-04.as57976 .net - 0 | 292 | 292 | 17 | 19 | 45 | 19 |
| 137.221.105.2 - 0 | 292 | 292 | 13 | 19 | 44 | 19 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Still a little twitchy on the edge, but doing a bit better.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.0.1 - 0 | 60 | 60 | 0 | 0 | 3 | 0 |
| 10.10.128.1 - 0 | 60 | 60 | 6 | 9 | 28 | 9 |
| 100.126.4.160 - 0 | 60 | 60 | 7 | 9 | 29 | 8 |
| 100.126.4.142 - 0 | 60 | 60 | 4 | 12 | 61 | 6 |
| dalsbprj01-ae1.0.rd.dl. cox. net - 0 | 60 | 60 | 12 | 18 | 81 | 22 |
| 68.105.30.10 - 0 | 60 | 60 | 12 | 16 | 40 | 19 |
| ae1-br01-eqda6.as57976. net - 0 | 60 | 60 | 49 | 56 | 131 | 50 |
| et-0-0-4-br01-eqch2.as57976. net - 0 | 60 | 60 | 31 | 87 | 900 | 32 |
| be1-pe02-eqch2.as57976. net - 0 | 60 | 60 | 49 | 52 | 60 | 49 |
| 24.105.62.129 - 0 | 60 | 60 | 51 | 53 | 63 | 52 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I don’t run them concurrently on the same host. One is my game station, the other is another host. I’m 1g lan here to a bsd router on to cable. Still seeing some high spikes, but no real loss out of 300 packets sent. Same leg though, 137.221.65.38.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.50.1 - 0 | 312 | 312 | 0 | 0 | 1 | 0 |
| 10.10.192.1 - 1 | 308 | 307 | 5 | 8 | 17 | 10 |
| 100.126.0.210 - 0 | 312 | 312 | 6 | 9 | 19 | 8 |
| 100.126.0.182 - 1 | 308 | 307 | 5 | 11 | 78 | 10 |
| 68.1.2.109 - 0 | 312 | 312 | 10 | 15 | 126 | 16 |
| 68.105.30.10 - 1 | 308 | 307 | 10 | 14 | 36 | 15 |
| 137.221.74.33 - 1 | 308 | 307 | 47 | 53 | 179 | 47 |
| 137.221.65.38 - 1 | 306 | 305 | 29 | 70 | 2116 | 618 |
| 137.221.69.69 - 1 | 308 | 307 | 47 | 50 | 63 | 51 |
| 24.105.62.129 - 0 | 312 | 312 | 48 | 51 | 64 | 50 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Kaliah,
What issue are you currently having?
What kind of twitchiness are you having? That test looks pretty solid. Is your latency in game spiking or anything like that? Is it only in certain areas or anywhere in game?
I dunno, you tell me… 52% loss still… is that good?
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.0.1 - 4 | 115 | 111 | 2 | 12 | 39 | 11 |
| 10.100.224.1 - 4 | 115 | 111 | 7 | 13 | 61 | 15 |
| 172.27.15.48 - 4 | 115 | 111 | 9 | 14 | 62 | 15 |
| 172.27.15.34 - 5 | 111 | 106 | 8 | 15 | 53 | 11 |
| dalsbprj01-ae1.0.rd.dl.cox. net - 9 | 99 | 91 | 23 | 31 | 70 | 29 |
| 68.105.30.10 - 7 | 100 | 93 | 23 | 30 | 72 | 31 |
| ae1-br01-eqda6.as57976. net - 50 | 42 | 21 | 52 | 58 | 91 | 52 |
| et-0-0-4-br01-eqch2.as57976. net - 42 | 48 | 28 | 43 | 51 | 85 | 46 |
| be1-pe01-eqch2.as57976. net - 44 | 46 | 26 | 52 | 57 | 96 | 52 |
| 24.105.62.129 - 0 | 131 | 131 | 50 | 56 | 91 | 60 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
WinMTR Statistics
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| router.asus .com | 0 | 709 | 709 | 0 | 0 | 3 | 1 |
| 10.6.16.1 | 0 | 708 | 708 | 5 | 9 | 21 | 9 |
| 68.4.15.10 | 0 | 708 | 708 | 6 | 9 | 64 | 11 |
| ip68-4-11-98.oc.oc.cox .net | 0 | 708 | 708 | 8 | 13 | 31 | 14 |
| 68.1.1.61 | 1 | 705 | 704 | 9 | 15 | 109 | 21 |
| 68.105.30.130 | 0 | 708 | 708 | 11 | 15 | 45 | 13 |
| ae1-br01-eqla1.as57976 .net | 0 | 705 | 705 | 14 | 52 | **1979** | 18 |
| et-0-0-2-br01-swlv10.as57976 .net | 1 | 694 | 692 | 15 | 41 | **3767** | 17 |
| et-0-0-31-pe02-swlv10.as57976 .net | 0 | 708 | 708 | 16 | 19 | 39 | 17 |
| las-swlv10-ia-bons-04.as57976 .net | 0 | 708 | 708 | 15 | 19 | 45 | 17 |
| 137.221.105.2 | 0 | 708 | 708 | 13 | 19 | 67 | 22 |
Spoke too soon. A couple of spikes happened for sure on the edge. Still running MTR.
Went for US-Central as that’s where my realm’s located. I’m not sure if it’s good, but if it is, it could be a baseline? I know for certain my MS has stabilized with no gameplay jitter.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.0.1 - 11 | 236 | 212 | 3 | 10 | 32 | 8 |
| 10.80.0.1 - 11 | 232 | 207 | 7 | 10 | 28 | 9 |
| 100.127.77.12 - 13 | 224 | 197 | 8 | 11 | 19 | 9 |
| 100.120.100.36 - 15 | 212 | 182 | 11 | 17 | 58 | 16 |
| 68.1.4.252 - 45 | 120 | 67 | 22 | 28 | 115 | 24 |
| 68.105.30.130 - 37 | 136 | 87 | 22 | 26 | 48 | 43 |
| ae1-br01-eqla1.as57976. net - 29 | 153 | 109 | 77 | 231 | 1979 | 82 |
| et-0-0-2-br01-swlv10.as57976. net - 5 | 275 | 262 | 77 | 111 | 4912 | 82 |
| 137.221.65.133 - 8 | 250 | 230 | 59 | 96 | 2128 | 65 |
| be1-pe01-eqch2.as57976. net - 37 | 135 | 86 | 78 | 81 | 90 | 78 |
| chi-eqch2-ia-bons-02.as57976. net - 41 | 127 | 76 | 79 | 82 | 92 | 81 |
| 24.105.62.129 - 0 | 331 | 331 | 76 | 79 | 98 | 80 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
At this time, 39ms home 49ms world. No warmode on… going to que for epic bg and see if lag happens.
Your issue is between your router and PC - you’ve got 4% loss in your own house. If you’re on wifi I’d swap to ethernet and power cycle your connection. If you’re on ethernet already, just do the power cycle for about 5 minutes and retest.
You have the same problem that Eagleeyé has, try the troubleshooting above.
@ Gorrnar
Your loss actually starts right after your router, looks like. That said, it doesn’t persist through the whole test so it’s hard to see whether or not it’s real or just some packet deprioritization between your router and ISP or modem. If you have a separate modem/router, I’d bypass the router if you’re still having issues.
This is what i'm getting:
TRACEROUTE:
traceroute to 24.252.195.74 (24.252.195.74), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.261 ms 0.241 ms 0.242 ms Blizzard(24.105.18.3) 0.537 ms 0.607 ms 0.657 ms
3 137.221.105.12 (137.221.105.12) 0.600 ms 0.700 ms 0.843 ms
4 137.221.66.16 (137.221.66.16) 0.651 ms 0.811 ms 0.820 ms
5 137.221.83.66 (137.221.83.66) 5.867 ms 5.882 ms 5.916 ms
6 137.221.65.68 (137.221.65.68) 5.726 ms 5.785 ms 5.767 ms
7 137.221.68.32 (137.221.68.32) 5.493 ms 5.517 ms 5.511 ms
8 _langbbrj02-ae1.301.r2.la.cox.net (68.105.30.129) 5.347 ms 5.370 ms 5.358 ms
9 _macnhdrj02-ae3.0.rd.mc.cox.net (68.1.2.148) 52.336 ms 52.354 ms 52.356 ms
10 _lkhnslbf02.rd.at.cox.net (68.1.8.22) 53.016 ms 52.927 ms 52.989 ms
11 _lkhnslbf02.rd.at.cox.net (68.1.8.22) 52.772 ms 52.686 ms 52.724 ms
12 * * *
13 * * *
14 * * *
15 * * *
13/04/2019 19:52:45 UTC
--------------------
TRACEROUTE:
traceroute to 24.252.195.74 (24.252.195.74), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.005 ms 4.566 ms 4.572 ms Blizzard(24.105.18.3) 8.869 ms 8.907 ms 8.916 ms
3 137.221.105.12 (137.221.105.12) 4.537 ms 4.543 ms 4.551 ms
4 137.221.66.16 (137.221.66.16) 4.421 ms 4.467 ms 4.477 ms
5 137.221.83.66 (137.221.83.66) 8.873 ms 8.881 ms 8.887 ms
6 137.221.65.68 (137.221.65.68) 8.822 ms 8.449 ms 8.488 ms
7 137.221.68.32 (137.221.68.32) 8.130 ms 8.156 ms 8.160 ms
8 _langbbrj02-ae1.301.r2.la.cox.net (68.105.30.129) 8.066 ms 8.084 ms 8.078 ms
9 _macnhdrj02-ae3.0.rd.mc.cox.net (68.1.2.148) 54.939 ms 52.941 ms 52.941 ms
10 _lkhnslbf02.rd.at.cox.net (68.1.8.22) 53.195 ms 53.195 ms 52.940 ms
11 _lkhnslbf02.rd.at.cox.net (68.1.8.22) 52.697 ms 52.889 ms 54.106 ms
12 * * *
13 * * *
14 * * *
15 * * *
13/04/2019 19:52:46 UTC
--------------------
TRACEROUTE:
traceroute to 24.252.195.74 (24.252.195.74), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.313 ms 0.308 ms 0.353 ms Blizzard(24.105.18.3) 0.573 ms 0.728 ms 2.680 ms
3 137.221.105.12 (137.221.105.12) 0.576 ms 0.747 ms 0.904 ms
4 137.221.66.16 (137.221.66.16) 0.708 ms 0.922 ms 0.931 ms
5 137.221.83.66 (137.221.83.66) 6.074 ms 6.135 ms 6.146 ms
6 137.221.65.68 (137.221.65.68) 5.704 ms 5.872 ms 5.881 ms
7 137.221.68.32 (137.221.68.32) 5.880 ms 5.920 ms 5.924 ms
8 _langbbrj02-ae1.301.r2.la.cox.net (68.105.30.129) 5.879 ms 5.898 ms 5.903 ms
9 _macnhdrj02-ae3.0.rd.mc.cox.net (68.1.2.148) 53.249 ms 53.321 ms 53.343 ms
10 _lkhnslbf02.rd.at.cox.net (68.1.8.22) 52.957 ms 53.045 ms 52.996 ms
11 _lkhnslbf02.rd.at.cox.net (68.1.8.22) 52.751 ms 52.674 ms 52.794 ms
12 * * *
13 * * *
14 * * *
15 * * *
13/04/2019 19:52:48 UTC
--------------------
PING:
PING 24.252.195.74 (24.252.195.74) 56(84) bytes of data.
--- 24.252.195.74 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
13/04/2019 19:52:45 UTC
--------------------
PING:
PING 24.252.195.74 (24.252.195.74) 56(84) bytes of data.
--- 24.252.195.74 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3003ms
13/04/2019 19:52:46 UTC
--------------------
TRACEROUTE:
traceroute to 24.252.195.74 (24.252.195.74), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.044 ms 1.070 ms 1.079 ms Blizzard(24.105.18.3) 1.915 ms 1.936 ms 1.945 ms
3 137.221.105.12 (137.221.105.12) 4.621 ms 4.738 ms 4.762 ms
4 137.221.66.16 (137.221.66.16) 4.639 ms 4.677 ms 4.687 ms
5 137.221.83.66 (137.221.83.66) 6.593 ms 6.615 ms 6.639 ms
6 137.221.65.68 (137.221.65.68) 6.439 ms 6.024 ms 6.015 ms
7 137.221.68.32 (137.221.68.32) 5.824 ms 5.796 ms 5.784 ms
8 _langbbrj02-ae1.301.r2.la.cox.net (68.105.30.129) 5.732 ms 5.681 ms 5.703 ms
9 _macnhdrj02-ae3.0.rd.mc.cox.net (68.1.2.148) 52.637 ms 52.678 ms 52.678 ms
10 _lkhnslbf02.rd.at.cox.net (68.1.8.22) 53.054 ms 54.302 ms 53.650 ms
11 _lkhnslbf02.rd.at.cox.net (68.1.8.22) 53.002 ms 52.743 ms 52.628 ms
12 * * *
13 * * *
14 * * *
15 * * *
13/04/2019 19:52:51 UTC
--------------------
PING:
PING 24.252.195.74 (24.252.195.74) 56(84) bytes of data.
--- 24.252.195.74 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
13/04/2019 19:52:50 UTC
--------------------
PING:
PING 24.252.195.74 (24.252.195.74) 56(84) bytes of data.
--- 24.252.195.74 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
13/04/2019 19:52:53 UTC
--------------------
MTR:
Start: Sat Apr 13 19:52:45 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.6 0.7 0.5 0.8 0.0
3.|-- 137.221.105.12 0.0% 10 0.6 1.2 0.5 5.6 1.4
4.|-- 137.221.66.16 0.0% 10 0.7 0.7 0.6 0.9 0.0
5.|-- 137.221.83.66 0.0% 10 6.0 7.5 5.7 21.5 4.9
6.|-- 137.221.65.68 0.0% 10 10.3 8.2 5.7 22.1 5.1
7.|-- 137.221.68.32 0.0% 10 5.8 6.9 5.5 13.4 2.5
8.|-- _langbbrj02-ae1.301.r2.la.cox.net 0.0% 10 5.4 5.6 5.4 6.2 0.0
9.|-- _macnhdrj02-ae3.0.rd.mc.cox.net 0.0% 10 52.3 52.9 52.3 54.5 0.6
10.|-- _lkhnslbf02.rd.at.cox.net 0.0% 10 53.1 53.5 53.0 56.5 1.0
11.|-- _lkhnslbf02.rd.at.cox.net 0.0% 10 52.7 52.8 52.6 53.1 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13/04/2019 19:52:45 UTC
--------------------
MTR:
Start: Sat Apr 13 19:52:46 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.6 0.7 0.5 1.4 0.0
3.|-- 137.221.105.12 0.0% 10 0.6 0.9 0.5 2.9 0.5
4.|-- 137.221.66.16 0.0% 10 0.7 1.5 0.6 5.1 1.4
5.|-- 137.221.83.66 0.0% 10 5.8 8.3 5.7 27.4 6.7
6.|-- 137.221.65.68 0.0% 10 21.4 8.7 5.7 21.4 5.8
7.|-- 137.221.68.32 0.0% 10 5.7 6.5 5.5 13.4 2.4
8.|-- _langbbrj02-ae1.301.r2.la.cox.net 0.0% 10 5.6 5.8 5.4 7.8 0.7
9.|-- _macnhdrj02-ae3.0.rd.mc.cox.net 0.0% 10 52.6 52.4 52.3 52.6 0.0
10.|-- _lkhnslbf02.rd.at.cox.net 0.0% 10 53.1 53.1 53.0 53.3 0.0
11.|-- _lkhnslbf02.rd.at.cox.net 0.0% 10 52.8 52.8 52.7 52.9 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13/04/2019 19:52:46 UTC
--------------------
MTR:
Start: Sat Apr 13 19:52:48 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0 Blizzard 0.0% 10 0.8 0.7 0.5 0.9 0.0
3.|-- 137.221.105.12 0.0% 10 1.1 0.7 0.5 1.1 0.0
4.|-- 137.221.66.16 0.0% 10 0.6 1.2 0.5 6.2 1.6
5.|-- 137.221.83.66 0.0% 10 6.1 7.5 5.6 18.1 3.8
6.|-- 137.221.65.68 0.0% 10 6.0 12.0 5.7 60.3 17.0
7.|-- 137.221.68.32 0.0% 10 5.7 5.9 5.5 8.3 0.7
8.|-- _langbbrj02-ae1.301.r2.la.cox.net 0.0% 10 5.4 7.9 5.4 24.2 5.7
9.|-- _macnhdrj02-ae3.0.rd.mc.cox.net 0.0% 10 54.5 52.7 52.2 54.5 0.6
10.|-- _lkhnslbf02.rd.at.cox.net 0.0% 10 53.2 53.2 53.0 54.3 0.3
11.|-- _lkhnslbf02.rd.at.cox.net 0.0% 10 52.8 52.8 52.7 53.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13/04/2019 19:52:48 UTC
--------------------
MTR:
Start: Sat Apr 13 19:52:51 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0 Blizzard 0.0% 10 0.6 1.6 0.6 10.6 3.1
3.|-- 137.221.105.12 0.0% 10 0.6 0.9 0.6 2.7 0.3
4.|-- 137.221.66.16 0.0% 10 0.7 0.7 0.5 0.9 0.0
5.|-- 137.221.83.66 0.0% 10 5.6 6.8 5.6 15.5 3.1
6.|-- 137.221.65.68 0.0% 10 5.6 5.8 5.6 6.0 0.0
7.|-- 137.221.68.32 0.0% 10 5.6 6.6 5.5 11.8 2.0
8.|-- _langbbrj02-ae1.301.r2.la.cox.net 0.0% 10 5.5 5.6 5.3 6.0 0.0
9.|-- _macnhdrj02-ae3.0.rd.mc.cox.net 0.0% 10 52.4 52.4 52.3 52.7 0.0
10.|-- _lkhnslbf02.rd.at.cox.net 0.0% 10 53.2 54.0 52.9 62.4 2.8
11.|-- _lkhnslbf02.rd.at.cox.net 0.0% 10 52.8 52.9 52.7 53.6 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13/04/2019 19:52:51 UTC
--------------------
1 Like
At this time i am in wintergrasp and both world and home are 49ms
1 Like
Well, as you saw in my more recent post… Nothing changed on my end and seeing spikes like that is not a good indicator.
In my first post, twitchiness is seeing an uptick at 127 and 108 on the suspect locations when they were averaging sub 90s until then… Now at 1030+ tests… 2nd as57976 .net had more packet loss than the edge hop by 12 tests while the edge only dropped 4… And while I do have one Cox packet loss at 68.1.1.61, it did not spike up to 1979ms delay or 3767ms delay like the two as57976 .net hops did.
I’m hard wired on my PC… but i haven’t reset my router in a while so yeah I’ll give that a try… still getting MORE packets lost further down stream though…
Also @ Eagleeyé
Where WinMTR is concerned, that’s irrelevant. You always need to worry about the earliest seen packet loss. Any packet loss early on will skew results later down.
Those large latency spikes are actually probably just more dropped packets or deprioritized tests. Our internal packet loss tracking from your ISP shows packet loss down about 1000% so we’re pretty confident we’ve fixed the issue and anything else you’re seeing is an individual issue that needs troubleshooting.
just did my first bg in 3 days felt good so far so good
That’s a single packet lost at that hop. 308 sent, 307 rcv’d. I’m not concerned with a single packet out of 308. The issue earlier, was 16923 sent, and only 16248 received back:
| 137.221.65.38 - 4 | 16923 | 16248 | 25 | 53 | 4743 | 30 |
Currently, I’m not seeing an issue.
1 Like
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.0.1 - 0 | 23 | 23 | 5 | 44 | 629 | 13 |
| 10.17.176.1 - 6 | 19 | 18 | 9 | 16 | 102 | 9 |
| 100.122.110.72 - 6 | 19 | 18 | 10 | 54 | 630 | 12 |
| 100.122.109.64 - 6 | 19 | 18 | 9 | 18 | 104 | 13 |
Yeah, fair 'nuff. I cycled my cable modem and tried again… was still getting that same loss. Then I swapped out the RJ45 cable… loss went away on the first hop to my modem. But then from modem to the local COX office, I’m still getting some loss… so that’s strange…