Forum Discussion

yolesnoobs's avatar
yolesnoobs
New Contributor III
5 years ago

Las Vegas/Henderson packet loss for months

Problem: Constant packet loss (tested via pingplotter) to different sites such as amazon, google, yahoo and while gaming with nobody else on the network. Packet loss is guaranteed when testing for 10+ minutes. It is a large enough issue to disrupt online work, VoIP and gaming sessions. Has been happening as long as I've been living here (~1.5 years).

Attempted Tests: 3 different modems, new coax cables, new ethernet cables, different PC, direct connection to modem, no splitters. At least 5 Cox field techs have checked for ingress and says everything looks fine.

Pingplotter: https://imgur.com/a/Do0hCDU

Modem Signals:

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
41 Locked QAM256 405000000 Hz -3.7 dBmV 36.9 dB 751 1425
1 Locked QAM256 783000000 Hz 0.2 dBmV 39.1 dB 747 2154
2 Locked QAM256 789000000 Hz 0.3 dBmV 39.1 dB 808 2076
3 Locked QAM256 795000000 Hz 0.1 dBmV 39.2 dB 704 2050
4 Locked QAM256 801000000 Hz 0.0 dBmV 39.0 dB 695 1995
9 Locked QAM256 831000000 Hz -0.9 dBmV 38.8 dB 1421 2065
10 Locked QAM256 837000000 Hz -1.0 dBmV 38.7 dB 671 1850
11 Locked QAM256 843000000 Hz -1.4 dBmV 38.4 dB 602 1900
12 Locked QAM256 849000000 Hz -1.7 dBmV 38.4 dB 612 1896
17 Locked QAM256 879000000 Hz -1.6 dBmV 38.4 dB 610 1872
18 Locked QAM256 885000000 Hz -1.6 dBmV 38.4 dB 716 1876
19 Locked QAM256 891000000 Hz -1.8 dBmV 38.2 dB 677 1966
20 Locked QAM256 897000000 Hz -1.9 dBmV 38.1 dB 862 1951
21 Locked QAM256 903000000 Hz -1.6 dBmV 38.0 dB 1133 1964
22 Locked QAM256 909000000 Hz -1.5 dBmV 38.0 dB 1355 1984
25 Locked QAM256 927000000 Hz -1.2 dBmV 38.4 dB 4609 2134
26 Locked QAM256 933000000 Hz -1.0 dBmV 38.7 dB 7104 2255
27 Locked QAM256 939000000 Hz -0.8 dBmV 38.8 dB 10430 2365
28 Locked QAM256 945000000 Hz -1.1 dBmV 38.8 dB 19112 3225
29 Locked QAM256 951000000 Hz -0.8 dBmV 38.9 dB 34773 5728
30 Locked QAM256 957000000 Hz -0.4 dBmV 39.1 dB 52122 9629
33 Locked QAM256 357000000 Hz -4.4 dBmV 36.7 dB 1092 2931
34 Locked QAM256 363000000 Hz -4.4 dBmV 36.6 dB 1117 2944
35 Locked QAM256 369000000 Hz -4.3 dBmV 36.8 dB 1073 2894
36 Locked QAM256 375000000 Hz -4.1 dBmV 36.7 dB 1136 2814
37 Locked QAM256 381000000 Hz -4.1 dBmV 36.7 dB 954 2723
38 Locked QAM256 387000000 Hz -4.1 dBmV 36.7 dB 1102 2747
42 Locked QAM256 411000000 Hz -4.1 dBmV 36.7 dB 1081 2340
43 Locked QAM256 417000000 Hz -3.9 dBmV 36.8 dB 1103 2128
44 Locked QAM256 423000000 Hz -3.8 dBmV 37.0 dB 1047 2180
45 Locked QAM256 429000000 Hz -3.8 dBmV 37.0 dB 995 2310
46 Locked QAM256 435000000 Hz -3.7 dBmV 36.9 dB 1068 2433
159 Locked Other 300000000 Hz -2.2 dBmV 37.5 dB 2016613922 81


Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 3 Locked SC-QAM Upstream 23500000 Hz 6400000 Hz 43.0 dBmV
2 1 Locked SC-QAM Upstream 36300000 Hz 6400000 Hz 44.0 dBmV
3 2 Locked SC-QAM Upstream 29900000 Hz 6400000 Hz 44.0 dBmV
4 4 Locked SC-QAM Upstream 16900000 Hz 6400000 Hz 42.0 dBmV


Modem Event Log:

Date Time Event ID Event Level Description
06/17/2019 23:48 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:95:69:fc:ae:b9;CMTS-MAC=d4:2c:44:7d:85:d1;CM-QOS=1.1;CM-VER=3.1;"
06/17/2019 10:39 2436694061 5 "Dynamic Range Window violation"
06/17/2019 10:39 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=2c:95:69:fc:ae:b9;CMTS-MAC=d4:2c:44:7d:85:d1;CM-QOS=1.1;CM-VER=3.1;"
06/16/2019 13:40 2436694061 5 "Dynamic Range Window violation"
06/16/2019 13:40 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=2c:95:69:fc:ae:b9;CMTS-MAC=d4:2c:44:7d:85:d1;CM-QOS=1.1;CM-VER=3.1;"
06/16/2019 13:26 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:95:69:fc:ae:b9;CMTS-MAC=d4:2c:44:7d:85:d1;CM-QOS=1.1;CM-VER=3.1;"
06/16/2019 12:28 2436694061 5 "Dynamic Range Window violation"
06/16/2019 12:28 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=2c:95:69:fc:ae:b9;CMTS-MAC=d4:2c:44:7d:85:d1;CM-QOS=1.1;CM-VER=3.1;"
06/16/2019 08:03 68010300 4 "DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=2c:95:69:fc:ae:b9;CMTS-MAC=d4:2c:44:7d:85:d1;CM-QOS=1.1;CM-VER=3.1;"
06/16/2019 02:21 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:95:69:fc:ae:b9;CMTS-MAC=d4:2c:44:7d:85:d1;CM-QOS=1.1;CM-VER=3.1;"

21 Replies

  • Hi xuboji, I was looking into this and am currently seeing packet loss from you and others in the area. I have informed our network operations team and they are sending this to our field team for investigation. I also saw your email about this, but am just going to respond here since this was your initial contact method.

    Brian
    Cox Support Forum Moderator
    • BrianM's avatar
      BrianM
      Moderator

      This looks to be resolved now. I am not seeing any further packet loss to your modem.

      Brian
      Cox Support 

      • yolesnoobs's avatar
        yolesnoobs
        New Contributor III

        I'm running ping tests and still seeing packet loss. May need to run the test for 5+ min to see it. 

  • BlackWat3r's avatar
    BlackWat3r
    New Contributor III

    By the way for those that live in Las Vegas, you do have another option in Century Link. Even have fiber gigabit in some areas for $65.

    I had them for one year on a free plan that was included in my condo and honestly never had any problems. For those that game my ping was in the 30-40s in most games. Never once did I have high ping with century link.

    Compare that to my base ping of 80 right now and constant pack loss/high ping spikes, it's looking like I'm switching back.

    I have had packet loss for over two months now, over 6 cox tech visits and a line guy come out to my house. It wasn't until the last visit did they even admit the node I am on is at 100% usage. But they still haven't fixed the issue and I honesly don't think they will.

    Google search this issue, fine me one thread where someone has come back and said this specific issue has been fix. You won't find any, everyone says the same thing that they have had this problem for months and cox won't/cant fix it.