Cox Packetloss, again.
I've made many posts about this issue over the years, and filed many FCC complaints, and thousands of emails later and still nothing to show for it but the packet loss. Like I mentioned I've had upstream loss for at least 4-5 years when i started to actually notice, cause then I started to get into online games, and it became difficult to play them, I've had at least 20-30 tech visits, most of the occurring in the past 3 years. Over a dozen linemen visits, and a few Supervisor visits, the original issue was backfeeding noise, that traveled into the node, causing the packet loss, they showed me a list of houses they needed to go to and fix the various problems to alleviate the noise, so it wouldn't backfeed and give packet loss, everyday the more work they did, the better the internet got, and eventually the internet was at it's prime. but since mid 2021 to now, it's been terrible. for the most part i gave up, because it consumed so much of my free time, monitoring the network via pingplotter for 4-5 hours when I know the packet loss will be present, and sending screenshots to the email support, just for them to tell me they don't see packet loss on their end. which hearing that every time really annoyed me, but i kept it up until I physically couldn't do it anymore, due to me working a full time job and coming home to deal with a headache, I like play online games with my buddies after work to keep entertained for the time i am home, but I can't seem to be able to do that at all anymore, gaming is completely ruined for me and is not fun due to the massive disadvantage it puts me at, and it gets frustrating so i choose to not play. I hope my efforts this time actually ensure a fix for me and the rest of my neighborhood, cause i know for a fact that they are experiencing it to, but they are ignorant to the issue and how to find it, or even know what packet loss is, cause most of my neighbors are older, or don't have the time to do what I am doing aka reporting it over and over. I highly doubt that I will actually get it fixed, due to how long I've been reporting it but one can hope, if you read through this and have cox affiliations please let the headquarters or email the team that works in Jeanerette Louisiana 70544, know that there is massive problems in this town for Cox. Thanks. -Michael530Views0likes3CommentsIs there anyway to contact the tech dispatch directly?
I'm not trying to contact support. I want to actually speak to the guys working on the lines. Been sitting on severe packet loss going on two months soon. Field Tech Supervisor finally came out and identified issue on the pole outside. Said every port or whatever was bad when he tried to switch me over. Noise feeding back into the line or something. Well, the problem has been found. But getting an actual person out here on the bucket truck is taking way too long. I literally can't do anything with this packet loss. At least when you schedule a service appointment you are given a date and time. When it comes to them submitting tickets to their field crew or whatever you are left in the dark. I would just like to be given a time frame on when I can expect to have someone coming out here on the truck to fix this. I've even called Corporate and the best thing I was told was "I've sent an email to them". Bro.568Views0likes0Comments10 Percent Packet Loss Throughout the Day, Tech's Fixes haven't helped
I've been experiencing packet loss issues for at least a few weeks. I notice this constantly in online games and when I remote desktop into my work computer from home.Sometimes I just completely lose internet on all my devices for 3-5 minutes. There ARE periods of time where the connection is totally smooth, but these are rare. I just had a tech over today who said he removed some old unused connections and fixed a broken connector. He also added a coax cable attenuator pad to my coax cable. None of this seems to have done anything for the packet loss. I've started using PingPlotter recently after looking into this problem. I attached an image of 10minutes worth of PingPlotter with Google DNS as the target for reference. I'm already experiencing about 10% loss at the second hop. Is there anything else I can do about this? I'm located in Kenner, Louisiana if that helps. Thanks for reading. https://imgur.com/Zd2QPE3735Views0likes0CommentsUpload speeds range from 0.00mbps to 0.05mbps + 5% - 10% packet loss on cox hardware and a wired connection.
Title speaks for itself. My company shifted everyone to working from home. With my upload speed. Which lets be honest i dont have any upload speed i cannot even upload files that are less than 1 megabyte. I work in accounting. I cannot email invoices, i cannot save changes to excel sheets on the company cloud. I LITERALLY CANT WORK!!!!. I have contacted cox more times than i can count regarding this I have let then know many times my livelihood is at stake, AND THEY COULD CARE LESS! Agents and tier 1 supervisors are useless. They will spout nonsense saying they see no issue on their end or that my signal levels are strong. They blame my equipment which i had to go rent a cox modem to prove to these crooks the issue was on their end. Tech arrives and says the issue is at the tap on their end WOOP TEE DOO how suprising!! Submits a ticket and says the problem will be fixed in a 3-4 days. 10 days later my internet is STILL barefully functional. I call to find out the ticket is still open! And these useless reps cant give me any details other than that the ticket is open, this was on thursday. On friday the ticket is closed as "resolved" and my internet is STILL in the state described in the title. Here is my most recent speedtest. KEEP IN MIND THIS WAS DONE AT 3 AM!!! I am paying for 100 down and 10 up! https://www.speedtest.net/result/9849250742 50 down and 0.02 up!!!!!! + 6% packet loss!!!! I pay these crooks 83 dollars per month! What will cox do when i get fired because i cant work!? On Monday that will be the third consecutive day that I CANNOT DO MY JOB!!!! if i cox rep responds to this asking me to restart my router i am going to freak out! FIX YOUR GARBAGE INFRASTRUTURE!!! A class action lawsuit NEEDS to happen, these levels of service are abhorrent!2.2KViews0likes3CommentsInternet constantly dropping for the past week
Hello, My internet has been constantly dropping for the past couple of days, making it impossible for my parents to work from home and for my brother and I to connect to class zoom meetings for school. The problem started getting significantly worse a couple of days ago to the point where it is impossible to be connected for any reasonable amount of time. I decided to check the status and logs for my modem and it shows this. Any help is appreciated. Modem Model: ARRIS SURFboard SB8200 Status: Procedure Status Comment Acquire Downstream Channel 951000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables 29 Locked QAM256 951000000 Hz 6.4 dBmV 39.0 dB 105 382 1 Locked QAM256 783000000 Hz 6.1 dBmV 39.0 dB 200 591 2 Locked QAM256 789000000 Hz 6.2 dBmV 39.0 dB 159 655 3 Locked QAM256 795000000 Hz 6.2 dBmV 39.1 dB 191 516 4 Locked QAM256 801000000 Hz 5.9 dBmV 38.7 dB 182 570 5 Locked QAM256 807000000 Hz 5.6 dBmV 38.6 dB 149 468 6 Locked QAM256 813000000 Hz 5.3 dBmV 38.5 dB 195 553 7 Locked QAM256 819000000 Hz 4.8 dBmV 38.3 dB 194 498 8 Locked QAM256 825000000 Hz 5.0 dBmV 38.4 dB 206 521 9 Locked QAM256 831000000 Hz 5.2 dBmV 38.5 dB 185 521 10 Locked QAM256 837000000 Hz 5.5 dBmV 38.6 dB 184 503 11 Locked QAM256 843000000 Hz 5.4 dBmV 38.6 dB 194 417 12 Locked QAM256 849000000 Hz 5.4 dBmV 38.6 dB 149 399 13 Locked QAM256 855000000 Hz 5.6 dBmV 38.8 dB 198 454 14 Locked QAM256 861000000 Hz 5.8 dBmV 38.7 dB 164 399 15 Locked QAM256 867000000 Hz 5.6 dBmV 38.8 dB 118 444 16 Locked QAM256 873000000 Hz 6.0 dBmV 38.9 dB 171 418 17 Locked QAM256 879000000 Hz 6.1 dBmV 39.0 dB 116 419 18 Locked QAM256 885000000 Hz 6.3 dBmV 39.0 dB 116 477 19 Locked QAM256 891000000 Hz 6.2 dBmV 38.9 dB 120 401 20 Locked QAM256 897000000 Hz 6.4 dBmV 38.9 dB 164 503 21 Locked QAM256 903000000 Hz 6.4 dBmV 38.9 dB 112 387 22 Locked QAM256 909000000 Hz 6.5 dBmV 39.1 dB 114 425 23 Locked QAM256 915000000 Hz 6.2 dBmV 38.9 dB 71 390 24 Locked QAM256 921000000 Hz 6.4 dBmV 39.1 dB 100 422 25 Locked QAM256 927000000 Hz 6.3 dBmV 39.0 dB 94 384 26 Locked QAM256 933000000 Hz 6.6 dBmV 39.1 dB 99 402 27 Locked QAM256 939000000 Hz 6.7 dBmV 39.2 dB 86 370 28 Locked QAM256 945000000 Hz 6.8 dBmV 39.3 dB 117 413 30 Locked QAM256 957000000 Hz 6.1 dBmV 39.0 dB 80 447 31 Locked QAM256 963000000 Hz 6.0 dBmV 38.9 dB 91 386 32 Locked QAM256 969000000 Hz 5.8 dBmV 38.7 dB 111 442 159 Locked Other 300000000 Hz 10.5 dBmV 0.0 dB 376365871 4356 Upstream Bonded Channels Channel Channel ID Lock Status US Channel Type Frequency Width Power 1 6 Locked SC-QAM Upstream 14600000 Hz 3200000 Hz 37.0 dBmV 2 1 Locked SC-QAM Upstream 19400000 Hz 6400000 Hz 43.0 dBmV 3 2 Locked SC-QAM Upstream 25800000 Hz 6400000 Hz 37.0 dBmV 4 3 Locked SC-QAM Upstream 32200000 Hz 6400000 Hz 41.0 dBmV 5 4 Locked SC-QAM Upstream 38600000 Hz 6400000 Hz 38.0 dBmV Logs: Date Time Event ID Event Level Description 07/30/2020 22:25 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:25 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:05 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:05 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:05 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:05 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:04 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:04 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:04 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:04 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:04 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:04 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:04 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:04 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:03 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:03 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:03 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:03 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:03 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:03 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:03 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:03 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:02 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:02 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:02 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:02 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:02 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 22:02 2436694061 5 "Dynamic Range Window violation" 07/30/2020 22:02 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:50 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:50 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:50 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:50 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:50 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:50 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:49 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:49 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:49 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:49 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:49 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:49 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:49 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:49 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:45 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:45 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:40 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:40 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:36 2436694061 5 "Dynamic Range Window violation" 07/30/2020 21:36 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=18:9c:27:fb:50:21;CMTS-MAC=00:59:dc:79:0a:3c;CM-QOS=1.1;CM-VER=3.1;" 07/30/2020 21:35 2436694061 5 "Dynamic Range Window violation" If anyone has any insights or solutions to this problem, it would be greatly appreciated. Sorry for the long post and thanks for reading.281Views0likes0CommentsCOX Packetloss Only At Night.
Hi, my name is Michael Bienvenu. I have been a COX Customer for over 2 and a half years, and my time with COX has been a terrible experience, Constant Packetloss for the first 2 years, and as of this last year I have been having a multitude of issues, my speeds were not what I was paying for, packetloss (as usual with any cox customer) i have been emailing the support team for over 2 months, and still nothing, a tech that came to my house recently, said that what I am experiencing is a RF leakage. Cause for the past year or so I have been getting pretty decent connection during the day, no packetloss at all, but when it hits around 7:30pm ish, my loss is back, causes issues with gaming, and VOIP. I don't even think I will ever get a fix but gotta hope I will. Then everytime they send a tech out, it's always the same thing, "I don't see any loss" "my tests came back clear" and they leave. a couple techs in the past have seen issues, then for the past week my modem has been resetting once a day, I emailed them and a rep told me that they are doing "nightly maintenance" and they send the modem resets in the area, I dont know if that is true or not, and to rub salt into the wound, I was in contact with a field tech, we were emailing back and forth and one day he just stopped emailing me all together, and he hasn't messaged me back since, so back to square one. I really feel like cox doesn't care about the user experience, and just want the money. that is how I am taking it. then with the covid around, i am literally home all day, and at night is when all my friends get on and we game, I havent been able to do that since the lockdowns.352Views0likes1CommentI'm tired of having terrible service.
I have a post from 5 months ago, and the problem is still going on. My upload speeds around 11pm go to 0 - 0.7. Yep, you seen that right, BELOW 1. I pay for 500 mbps down and 10 up. I have a strait line from the pole to my panoramic modem you provide me. I have had a tech to come and replace the drop but was too lazy to do it so he cut the wire at my carport and just ran a new wire from there to my modem. I fail to understand why nobody has found the issues thus far. Even with gigablast, I still had nothing but problems with my upstream. Here are my signals.... Downstream Index 2 1 3 4 9 10 11 12 17 18 19 20 21 22 25 26 27 28 29 30 33 34 35 36 37 38 41 42 43 44 45 46 159 Lock Status Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Locked Frequency 687 MHz 681 MHz 693 MHz 699 MHz 729 MHz 735 MHz 741 MHz 747 MHz 777 MHz 783 MHz 789 MHz 795 MHz 801 MHz 807 MHz 825 MHz 831 MHz 837 MHz 843 MHz 849 MHz 855 MHz 357 MHz 363 MHz 369 MHz 375 MHz 381 MHz 387 MHz 405 MHz 411 MHz 417 MHz 423 MHz 429 MHz 435 MHz 300 MHz 203600000 SNR 41.2 dB 41.3 dB 41.4 dB 41.3 dB 41.2 dB 41.3 dB 41.2 dB 41.2 dB 41.2 dB 41.2 dB 41.0 dB 41.0 dB 40.9 dB 40.6 dB 39.9 dB 39.6 dB 39.3 dB 39.0 dB 38.7 dB 38.5 dB 41.0 dB 41.6 dB 41.3 dB 41.4 dB 41.6 dB 41.6 dB 41.5 dB 41.5 dB 41.5 dB 41.5 dB 41.4 dB 41.5 dB 43.8 dB NA Power Level 2.5 dBmV 2.2 dBmV 2.4 dBmV 2.4 dBmV 2.6 dBmV 2.8 dBmV 2.9 dBmV 2.7 dBmV 2.6 dBmV 2.4 dBmV 2.5 dBmV 2.2 dBmV 2.2 dBmV 1.8 dBmV 0.5 dBmV 0.0 dBmV 0.5 dBmV 0.8 dBmV -1.4 dBmV -1.6 dBmV 2.3 dBmV 2.3 dBmV 2.1 dBmV 2.0 dBmV 2.2 dBmV 2.2 dBmV 2.2 dBmV 2.2 dBmV 2.1 dBmV 2.2 dBmV 2.1 dBmV 2.0 dBmV 5.8 dBmV NA Modulation 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM 256 QAM OFDM OFDM Upstream Index 1 2 3 4 Lock Status Locked Locked Locked Locked Frequency 36 MHz 30 MHz 23 MHz 17 MHz Symbol Rate 5120 5120 5120 5120 Power Level 34.8 dBmV 34.8 dBmV 35.3 dBmV 35.3 dBmV Modulation QAM QAM QAM QAM Channel Type ATDMA ATDMA ATDMA ATDMA537Views0likes1CommentHigh latency and packet loss
For about three weeks now I’ve been having issues with high ping and packet loss. I’m most definitely sure it’s not my hardware, I’ve replaced cables, tried a new router, looked at modem power levels fo anomalies and everything checks out. I’ve contacted cox multiple times and all I get are the generic troubleshooting efforts. I’ve ran pingplotter and can see I’m loosing packets at a cox IP address. I’m in San Diego, is there a bad node somewhere? It’s irritating paying full price for a service that can’t be fully utilized well. Anyone else having the same issues?496Views0likes1CommentUpload speed and constant packet loss
Hello, I'm currently experiencing severe packet loss when trying to stream games. I'm using gigablast and should have no issue with 5000 bit rate however the trend continues with dropped packets. I'm directly connected to my router there are no splitters or amplifiersin between. My jitter is roughly 13-15 range when running a test and a when running a traceroute I find I'm dropping on the 8th hop or so outside my home network. What are my options?497Views0likes0CommentsPacketloss In Games and Discord.
Hi, My name is Michael Bienvenu, I live in Jeanerette Louisiana, and cox is the only ISP in my area that is worth having. I have been having ongoing internet issues, Packetloss on every single game I have ever played, I just got a new Router, I have tried a new ethernet Cable, and have gotten a new modem, multiple techs have came out to my house in the past year to help fix this but none of them have been able to permanently fix my Packetloss. I know that it's my internet and not the game servers because when I start to lag in game I check my discord and I see 100% packetloss and 10000 ping. Then it goes away and comes back every 10-15 mins. I have just ordered and received a new pci e network card for my pc. I tried gaming on call of duty modern warfare and had discord open and I started to lag the same as before. So it didn't work, Might as well keep the new nic installed, not hurting anything, my router is the Netgear Nighthawk AC 2100, I had the Panoramic Wifi Gateway and it also gave lag in games and discord. I had another router and tried it also, but same issue. I then got a dedicated modem from cox. and it is the same issue, Had linemens come out and say that the drop looks fine, I am thinking now that it is cox and how they route stuff or something, or it may be noise in the line,but the last tech said that they don't detect any noise, or packetloss, when I run a test and shows packetloss using ping plotter. I have tried bypassing my router and connecting my pc to the modem and I couldn't get a connection. I have talked to people over the internet and they too have lag in all games and discord too. Downstream QAM Downstream # DCID Freq Power SNR Modulation Octets Correcteds Uncorrectables 1 1 681.00 MHz 4.20 dBmV 40.37 dB 256QAM 301673428 0 0 2 2 687.00 MHz 4.10 dBmV 40.37 dB 256QAM 301426504 0 0 3 3 693.00 MHz 4.00 dBmV 38.98 dB 256QAM 301509553 0 0 4 4 699.00 MHz 3.60 dBmV 38.61 dB 256QAM 362960913 0 0 5 9 729.00 MHz 4.00 dBmV 38.98 dB 256QAM 360882703 8 0 6 10 735.00 MHz 3.50 dBmV 38.98 dB 256QAM 367049828 4 0 7 11 741.00 MHz 3.70 dBmV 38.98 dB 256QAM 367376426 2 0 8 12 747.00 MHz 3.60 dBmV 38.98 dB 256QAM 222983079 0 0 9 17 777.00 MHz 2.80 dBmV 38.98 dB 256QAM 223427239 4 0 10 18 783.00 MHz 2.70 dBmV 38.98 dB 256QAM 222335966 2 0 11 19 789.00 MHz 2.50 dBmV 38.98 dB 256QAM 222308444 0 0 12 20 795.00 MHz 2.40 dBmV 38.98 dB 256QAM 222375259 2 0 13 21 801.00 MHz 2.50 dBmV 38.98 dB 256QAM 327737400 0 0 14 22 807.00 MHz 1.80 dBmV 38.98 dB 256QAM 292661953 0 0 15 25 825.00 MHz 1.00 dBmV 38.98 dB 256QAM 292970266 0 0 16 26 831.00 MHz 0.80 dBmV 38.61 dB 256QAM 285558664 0 0 17 27 837.00 MHz 0.70 dBmV 38.61 dB 256QAM 285320117 2 0 18 28 843.00 MHz 0.60 dBmV 38.61 dB 256QAM 287791096 8 0 19 29 849.00 MHz 0.90 dBmV 38.61 dB 256QAM 389608699 3 0 20 30 855.00 MHz 1.50 dBmV 38.98 dB 256QAM 310833435 0 0 21 33 357.00 MHz 2.30 dBmV 40.37 dB 256QAM 201600990 31 0 22 34 363.00 MHz 2.60 dBmV 40.37 dB 256QAM 201337260 78 0 23 35 369.00 MHz 2.70 dBmV 40.37 dB 256QAM 201421351 71 0 24 36 375.00 MHz 2.70 dBmV 38.98 dB 256QAM 200771061 61 0 25 37 381.00 MHz 2.40 dBmV 40.37 dB 256QAM 201189504 35 0 26 38 387.00 MHz 2.60 dBmV 38.98 dB 256QAM 364462704 84 0 27 41 405.00 MHz 2.90 dBmV 40.37 dB 256QAM 261948035 76 0 28 42 411.00 MHz 2.60 dBmV 40.37 dB 256QAM 257973930 133 120 29 43 417.00 MHz 2.80 dBmV 40.37 dB 256QAM 257818897 69 0 30 44 423.00 MHz 2.90 dBmV 38.98 dB 256QAM 282927143 2 0 31 45 429.00 MHz 3.30 dBmV 40.37 dB 256QAM 282050407 6 0 32 46 435.00 MHz 3.50 dBmV 40.37 dB 256QAM 1087953048 0 0 Upstream QAM Upstream # UCID Freq Power Channel Type Symbol Rate Modulation 1 2 32.30 MHz 44.00 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM 2 4 19.40 MHz 42.00 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM 3 3 25.90 MHz 43.50 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM 4 1 38.70 MHz 45.00 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM DOCSIS(CM) Events Date Time Event ID Event Level Description 1/1/2020 19:53 68001102 3 Config File Rejected due to Invalid or Unexpected TLV 11;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/1/2020 19:53 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:14 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:14 84020200 5 Lost MDD Timeout;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:16 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:16 84020200 5 Lost MDD Timeout;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:17 82000400 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:19 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:19 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:19 73040100 6 TLV-11 - unrecognized OID;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:19 68001102 3 Config File Rejected due to Invalid or Unexpected TLV 11;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:19 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:27 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:27 84020200 5 Lost MDD Timeout;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:27 82000400 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:35 84020100 4 Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:35 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:35 73040100 6 TLV-11 - unrecognized OID;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:35 68001102 3 Config File Rejected due to Invalid or Unexpected TLV 11;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:35 84000700 5 RCS Partial Service;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 10:36 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 15:44 84020200 5 Lost MDD Timeout;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/2/2020 18:49 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/4/2020 12:48 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/4/2020 12:48 73040100 6 TLV-11 - unrecognized OID;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/4/2020 12:48 68001102 3 Config File Rejected due to Invalid or Unexpected TLV 11;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/4/2020 12:48 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/4/2020 15:17 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/4/2020 15:17 73040100 6 TLV-11 - unrecognized OID;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/4/2020 15:17 68001102 3 Config File Rejected due to Invalid or Unexpected TLV 11;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/4/2020 15:17 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/10/2020 17:09 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/10/2020 17:09 73040100 6 TLV-11 - unrecognized OID;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/10/2020 17:09 68001102 3 Config File Rejected due to Invalid or Unexpected TLV 11;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 1/10/2020 17:09 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/3/2020 20:24 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/3/2020 20:24 73040100 6 TLV-11 - unrecognized OID;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/3/2020 20:24 68001102 3 Config File Rejected due to Invalid or Unexpected TLV 11;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/3/2020 20:24 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/15/2020 23:09 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/15/2020 23:09 73040100 6 TLV-11 - unrecognized OID;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/15/2020 23:09 68001102 3 Config File Rejected due to Invalid or Unexpected TLV 11;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/15/2020 23:09 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/19/2020 19:22 82000300 3 Ranging Request Retries exhausted;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/19/2020 19:22 82000600 3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/19/2020 19:39 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/20/2020 15:36 90000000 5 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/20/2020 15:36 73040100 6 TLV-11 - unrecognized OID;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/20/2020 15:36 68001102 3 Config File Rejected due to Invalid or Unexpected TLV 11;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 2/20/2020 15:36 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=20:f1:9e:1f:94:ba;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;1.5KViews0likes1Comment