Horrible Packet Loss (Fix ASAP Cox)
Fix this cox.
Forum Discussion
Hi User, since you've posted on several other threads regarding packet loss and the AWS servers, you know that my team and the network engineering team are investigating these reports. Please bypass your router, connect a device directly to your modem, and reset the modem. Then, run 2 traceroutes (or PingPlotters) to the AWS server in question and one traceroute to www.google.com. Post your results here or email them to cox.help@cox.com. -Becky, Cox Support Forums Moderator
Can you guys raise a support issue to Level3?
File an FCC claim if you want a direct line to management. I would recommend that anyone who is frustrated with COX file a claim within the next month so the pressure on them keeps mounting. Don't let them ignore this.
doing that right now thanks.
yes please
C:\Users\mark>tracert www.google.com
Tracing route to www.google.com [108.177.104.104]
over a maximum of 30 hops:1 10 ms 7 ms 7 ms 10.71.32.1
2 11 ms 12 ms 10 ms 100.120.104.132
3 76 ms 54 ms 9 ms 100.120.104.12
4 * 25 ms 34 ms 68.1.1.167
5 19 ms 10 ms 11 ms 72.14.196.240
6 26 ms * 23 ms 108.170.247.243
7 * 20 ms 11 ms 108.170.234.37
8 76 ms 93 ms 81 ms 209.85.251.128
9 78 ms 80 ms 78 ms 209.85.250.37
10 78 ms 80 ms 78 ms 108.170.230.179
11 78 ms 81 ms 80 ms 209.85.252.57
12 80 ms 77 ms 77 ms 216.239.59.41
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 93 ms 76 ms 77 ms 108.177.104.104Trace complete.
C:\Users\mark>tracert 52.42.109.244
Tracing route to ec2-52-42-109-244.us-west-2.compute.amazonaws.com [52.42.109.244]
over a maximum of 30 hops:1 10 ms 10 ms 8 ms 10.71.32.1
2 17 ms 11 ms 9 ms 100.120.104.134
3 9 ms 13 ms 19 ms 100.120.104.14
4 23 ms 11 ms 23 ms 68.1.1.61
5 17 ms 12 ms 11 ms 52.95.218.214
6 57 ms 60 ms 52 ms 54.239.102.100
7 14 ms 12 ms 12 ms 54.239.102.111
8 35 ms 35 ms 36 ms 54.239.42.122
9 * * * Request timed out.
10 40 ms 103 ms 100 ms 52.93.12.122
11 45 ms 35 ms 35 ms 52.93.12.109
12 53 ms 57 ms 64 ms 52.93.12.144
13 39 ms 38 ms 37 ms 52.93.12.167
14 * 72 ms 78 ms 52.93.240.67
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.Trace complete.
Here's pingplotter from my latest RL game.
You can see huge packet loss to Level3.net servers.
Target Name: 104.153.85.100
IP: 104.153.85.100
Date/Time: 9/10/2018 11:37:01 PM - 9/10/2018 11:47:01 PMHop Sent PL% Min Max Avg Host Name / [IP]
1 19 0 0.83 55.14 7.55 192.168.1.1 [192.168.1.1]
2 19 0 9.45 14.51 11.28 10.48.128.1 [10.48.128.1]
3 19 0 8.12 146.06 25.53 100.127.74.28 [100.127.74.28]
4 19 0 8.49 98.42 24.88 100.120.100.12 [100.120.100.12]
5 18 67 11.20 22.42 13.85 lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]
6 5 80 63.52 63.52 63.52 ae-1-3502.ear2.Washington12.Level3.net [4.69.140.117]
7 19 0 66.78 171.64 79.90 INTERACTIVE.ear2.Washington12.Level3.net [4.16.76.162]
8 19 0 65.17 287.28 80.31 104.153.85.100 [104.153.85.100]And another one to a different server.
Target Name: 162.245.206.44
IP: 162.245.206.44
Date/Time: 9/10/2018 11:40:19 PM - 9/10/2018 11:50:19 PMHop Sent PL% Min Max Avg Host Name / [IP]
1 20 0 1.10 2.11 1.64 192.168.1.1 [192.168.1.1]
2 20 0 7.93 16.79 10.16 10.48.128.1 [10.48.128.1]
3 20 0 8.46 13.29 10.37 100.127.74.28 [100.127.74.28]
4 20 0 8.17 19.08 10.48 100.120.100.12 [100.120.100.12]
5 20 70 10.07 11.83 11.00 lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]
6 18 67 25.92 30.89 27.20 ae-1-51.ear1.LosAngeles6.Level3.net [4.69.210.93]
7 20 0 33.19 45.60 37.47 INTERACTIVE.ear1.LosAngeles6.Level3.net [4.26.2.134]
8 19 0 33.05 44.10 36.31 162.245.206.44 [162.245.206.44]And one to www.google.com.
No packet loss.
Target Name: www.google.com
IP: 172.217.5.68
Date/Time: 9/10/2018 11:41:26 PM - 9/10/2018 11:51:26 PMHop Sent PL% Min Max Avg Host Name / [IP]
1 14 0 0.81 5.82 1.93 192.168.1.1 [192.168.1.1]
2 14 0 7.27 14.14 9.54 10.48.128.1 [10.48.128.1]
3 14 0 8.87 15.11 11.00 100.127.74.30 [100.127.74.30]
4 14 0 8.58 14.31 10.83 100.120.100.16 [100.120.100.16]
5 14 0 19.36 29.75 22.09 68.1.4.252 [68.1.4.252]
6 14 0 20.51 24.85 21.85 72.215.224.173 [72.215.224.173]
7 13 100 0 0 0 [-]
8 14 0 21.11 24.52 22.95 108.170.237.140 [108.170.237.140]
9 14 0 19.43 22.32 20.75 108.170.237.113 [108.170.237.113]
10 14 0 18.92 29.70 21.24 www.google.com [172.217.5.68]
