Cox_User_Who_Ne's profile

Cox_User_Who_Ne

Contributor

 • 

50 Messages

Closed

Horrible Packet Loss (Fix ASAP Cox)

Fix this cox.

Discussions

 • 

Updated 

9.4K

2

0

0

B

Becky

+2 more

Moderator

 • 

4.3K Messages

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

11

0

C
Cox_User_Who_Ne

Contributor

 • 

50 Messages

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.104

Trace 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.

Like

Reply

0

T
Tikerz

New Contributor II

 • 

7 Messages

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 PM

Hop 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]

Like

Reply

0

T
Tikerz

New Contributor II

 • 

7 Messages

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 PM

Hop 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]

Like

Reply

0

T
Tikerz

New Contributor II

 • 

7 Messages

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 PM

Hop 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]

Like

Reply

0

T
Tikerz

New Contributor II

 • 

7 Messages

Can you guys raise a support issue to Level3?

Like

Reply

H

harvey0773

New Contributor

 • 

1 Message

I suffer from the same problem. But with me it is with any game I play. Here is what a friend of mine tells me to look at and says there is interference someone in the lines. I have already replaced my modem, bypassed the router, swapped out both coax and ethernet cables and still have the problem. I have had a tech come out three times and they always say everything looks good. Any help in the near future?

Sep 17 2018 19:17:39 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:39 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:39 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:40 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:40 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:41 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:41 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:42 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:42 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:43 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:43 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:44 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:44 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:45 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:45 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:46 Critical (3) Ranging Request Retries exhausted
Sep 17 2018 19:17:46 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Sep 17 2018 19:17:47 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:47 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:48 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:48 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:49 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:49 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:50 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:50 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:51 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:51 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:52 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:53 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:53 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:53 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:54 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:54 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:55 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:55 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:56 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:56 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2018 19:17:57 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Sep 17 2018 19:17:57 Critical (3) No Ranging Response received - T3 time-out
Sep 18 2018 08:13:24 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 18 2018 08:13:25 Notice (6) TLV-11 - unrecognized OID
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables UnCorrectables
1 Locked QAM 256 33 357000000 Hz 6.6 dBmV 37.6 dB 10491 5363
2 Locked QAM 256 34 363000000 Hz 6.8 dBmV 37.6 dB 9509 5716
3 Locked QAM 256 35 369000000 Hz 6.9 dBmV 37.6 dB 8982 5148
4 Locked QAM 256 36 375000000 Hz 6.9 dBmV 37.3 dB 8089 5101
5 Locked QAM 256 37 381000000 Hz 6.9 dBmV 38.2 dB 4930 3350
6 Locked QAM 256 38 387000000 Hz 7.0 dBmV 38.2 dB 4807 3188
7 Locked QAM 256 41 405000000 Hz 7.0 dBmV 38.2 dB 3640 2695
8 Locked QAM 256 42 411000000 Hz 7.3 dBmV 38.2 dB 3279 2357
9 Locked QAM 256 43 417000000 Hz 7.4 dBmV 38.2 dB 2940 2280
10 Locked QAM 256 44 423000000 Hz 7.3 dBmV 38.6 dB 2747 2067
11 Locked QAM 256 45 429000000 Hz 7.5 dBmV 38.2 dB 2739 2032
12 Locked QAM 256 46 435000000 Hz 7.5 dBmV 38.2 dB 2413 1982
13 Locked QAM 256 1 783000000 Hz 9.3 dBmV 38.9 dB 1930 4635
14 Locked QAM 256 2 789000000 Hz 9.0 dBmV 38.6 dB 1301 1257
15 Locked QAM 256 3 795000000 Hz 8.9 dBmV 38.6 dB 1354 2170
16 Locked QAM 256 4 801000000 Hz 8.5 dBmV 38.9 dB 1317 1202
17 Locked QAM 256 9 831000000 Hz 8.9 dBmV 38.9 dB 5485 1390
18 Locked QAM 256 10 837000000 Hz 9.0 dBmV 38.9 dB 14480 141
19 Locked QAM 256 11 843000000 Hz 8.9 dBmV 38.6 dB 53335 3139
20 Locked QAM 256 12 849000000 Hz 9.1 dBmV 38.6 dB 22403 86
21 Locked QAM 256 17 879000000 Hz 9.5 dBmV 38.9 dB 386 29
22 Locked QAM 256 18 885000000 Hz 9.1 dBmV 38.6 dB 509 6
23 Locked QAM 256 19 891000000 Hz 9.4 dBmV 38.9 dB 473 36
24 Locked QAM 256 20 897000000 Hz 9.5 dBmV 38.9 dB 449 47
25 Locked QAM 256 21 903000000 Hz 9.0 dBmV 38.6 dB 361 119
26 Locked QAM 256 22 909000000 Hz 9.0 dBmV 38.6 dB 570 31
27 Locked QAM 256 25 927000000 Hz 9.1 dBmV 38.9 dB 28202 185
28 Locked QAM 256 26 933000000 Hz 9.5 dBmV 38.6 dB 1053 51
29 Locked QAM 256 27 939000000 Hz 9.6 dBmV 38.9 dB 645 93
30 Locked QAM 256 28 945000000 Hz 9.0 dBmV 38.6 dB 362 37
31 Locked QAM 256 29 951000000 Hz 8.9 dBmV 38.6 dB 356 8
32 Locked QAM 256 30 957000000 Hz 9.1 dBmV 38.9 dB 170 53
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 4 2560 Ksym/sec 18400000 Hz 36.0 dBmV
2 Locked ATDMA 3 5120 Ksym/sec 23300000 Hz 36.0 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 29800000 Hz 36.5 dBmV
4 Not Locked ATDMA 1 5120 Ksym/sec 36300000 Hz 37.5 dBmV
5 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV

1

0

C
ChrisL

Former Moderator

 • 

7.1K Messages

@Harvey0773

I see we have a maintenance ticket associated with your account to investigate further. I apologize for any inconvenience caused in the meanwhile.

-Chris

Like

Reply

Recent Discussions