I'm having 3-5% packet loss on Ethernet connection. I've ran through different ping tests on cmd and the problem only arises when pinging other websites, pinging my own IP results in 0% loss. Also, plugging directly into the modem did not resolved the issue. I can attach the cmd tests as well if need be.
Thanks
Here are some tests I did. The biggest issue is when I'm gaming, but i dont have the trace route to the servers only game logs of packet loss so here are some tests to websites.
C:\Users\liamm>pathping www.google.com
Tracing route to www.google.com [2607:f8b0:400e:c04::6a]
over a maximum of 30 hops:
0 DESKTOP-TKFACCN [2600:8802:5600:814:7181:abd7:7ff5:5a23]
1 2600:8802:5600:814:1ad6:c7ff:fe24:199a
2 2600:8802:56ff:ffff::1111
3 2001:578:400:fff0:7000::50
4 2001:578:400:fff0::1a
5 2001:578:1:0:172:17:249:33
6 2001:578:20:a100::7:1
7 2607:f8b0:8000:202::1:1
8 2001:4860:0:1::2da
9 2001:4860:0:1110::13
10 2001:4860::c:4000:de41
11 2001:4860::c:4001:12d4
12 2001:4860::2:0:9100
13 * * *
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-TKFACCN [2600:8802:5600:814:7181:abd7:7ff5:5a23]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 2600:8802:5600:814:1ad6:c7ff:fe24:199a
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% 2600:8802:56ff:ffff::1111
0/ 100 = 0% |
3 11ms 1/ 100 = 1% 1/ 100 = 1% 2001:578:400:fff0:7000::50
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% 2001:578:400:fff0::1a
0/ 100 = 0% |
5 18ms 0/ 100 = 0% 0/ 100 = 0% 2001:578:1:0:172:17:249:33
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 2001:578:20:a100::7:1
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% 2607:f8b0:8000:202::1:1
0/ 100 = 0% |
8 17ms 0/ 100 = 0% 0/ 100 = 0% 2001:4860:0:1::2da
0/ 100 = 0% |
9 16ms 0/ 100 = 0% 0/ 100 = 0% 2001:4860:0:1110::13
0/ 100 = 0% |
10 17ms 0/ 100 = 0% 0/ 100 = 0% 2001:4860::c:4000:de41
0/ 100 = 0% |
11 46ms 0/ 100 = 0% 0/ 100 = 0% 2001:4860::c:4001:12d4
0/ 100 = 0% |
12 41ms 0/ 100 = 0% 0/ 100 = 0% 2001:4860::2:0:9100
Trace complete.
C:\Users\liamm>tracert cox.com
Tracing route to cox.com [45.60.45.167]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 7 ms 8 ms 68.4.15.40
4 14 ms 12 ms 13 ms ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
5 20 ms 13 ms 19 ms 68.1.1.63
6 41 ms 21 ms 23 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 22 ms 15 ms 16 ms ae-3.r00.lsanca20.us.bb.gin.ntt.net [129.250.2.253]
8 35 ms 35 ms 36 ms ae-6.r22.lsanca07.us.bb.gin.ntt.net [129.250.6.46]
9 16 ms 15 ms 15 ms ae-1.r01.lsanca07.us.bb.gin.ntt.net [129.250.3.123]
10 16 ms 14 ms 14 ms 192.80.17.102
11 13 ms 15 ms 16 ms 45.60.45.167
Trace complete.
C:\Users\liamm>
Tracing route to google.com [172.217.1.238]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 16 ms 13 ms rsmtdsrc01-gew03020996.rd.oc.cox.net [68.4.15.4]
4 14 ms 14 ms 15 ms ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
5 16 ms 14 ms 14 ms 68.1.1.167
6 16 ms 22 ms 15 ms 72.215.224.175
7 * * * Request timed out.
8 36 ms 37 ms 34 ms 108.170.237.112
9 22 ms 18 ms 14 ms 108.170.247.212
10 30 ms 30 ms 38 ms 108.170.230.121
11 56 ms 48 ms 80 ms 216.239.43.146
12 50 ms 49 ms 49 ms 108.170.228.83
13 * * * Request timed out.
14 50 ms 51 ms 50 ms 216.239.40.47
15 49 ms 48 ms 50 ms lax17s02-in-f14.1e100.net [172.217.1.238]
Trace complete.
C:\Users\liamm>
good luck with that question, NO ONE AT COX knows how to help in packet loss, if they did there would be devices and software that COULD make a difference. they dont care.
@wmoyers,
Thanks for providing the requested information. Please send us an email with your full address to cox.help@cox.com so we can research this issue further for you.
Thanks,
Allan - Cox Support Forums Moderator.
