Upstream packet loss and jitter
Hey Guys, Non-stop packetloss all day.
Cox is saying everything is okay, I have been graphing/monitoring the loss for months.
What resolutions do we have besides switching ISPs? Are there any ...
Forum Discussion
After the reboot 4~ hours ago. There are no uncorrectables or corrected, but still packet loss.
That means the large number of uncorrectables you saw before was probably the result of overnight maintenance. The good news is that you probably don't have a major noise ingress problem, but that bad news is that it's a more complicated problem to solve. Hopefully Cox can figure it out.
The have seen everything I posted here. They could care less it seems. Finally after 30 email replies and filing an FCC complaint they admit they can at least see the packet loss (after multiple modem/cox care upsell attempts). Technician comes Thursday morning. I do not have any high hopes of resolutions based of my current experience with them.
I dont get why they are not regulated to monitor customer connections and pro-actively respond. They can likely see multiple modems in the same area having this issue. Instead of sending techs one by one to houses to resolve nothing.
They can oversell, they try to charge you to send techs. Im guessing after all is said and done I will be in the same boat.
Crazy that 4G is higher speed, lower ping, no packetloss in 2021 and cox could care less.
I dont get why they are not regulated to monitor customer connections and pro-actively respond. They can likely see multiple modems in the same area having this issue. Instead of sending techs one by one to houses to resolve nothing.
I don't know for sure, but I have a theory. If they monitored all modems and looked for areas of trouble, that might create a legal responsibility for them to repair those problems in order to continue selling their service. If they knew about problems but chose not to fix them, that might count as knowingly selling a defective product.
Also, most people use their connections mainly for light web browsing and some video streaming. Those people are unaffected by moderate upstream packet loss, so Cox has no reason to repair those connections until the users complain. The cable network is old and fragile so it's possible they just wouldn't be able to keep up with repairs if they fixed every single problem with the network. Instead they wait for people to complain and only fix the areas where people are affected by the problems.
Again I don't know anything for sure. This is just a theory.
Uncorrectables are back in the thousands. More events.
After days of emailing/dealing with COX help/support we have got no where. They will not even admit seeing the issue in the ping plotters. Showing the packet loss starting and going to the end, across multiple external endpoints.
Ive also started to ping plotter only internal routes to cox. 10.x.128.1 etc. and they all have the same packet loss at the same time as the external routes drop.
Tue Jul 06 03:01:09 2021 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 03:02:16 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 04:19:26 2021 3 No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 04:49:00 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:46:14 2021 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:46:16 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:55:21 2021 3 No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:56:08 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 10:52:29 2021 5 Lost MDD Timeout;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 10:58:00 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 03:01:09 2021 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 03:02:16 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 04:19:26 2021 3 No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 04:49:00 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:46:14 2021 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:46:16 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:55:21 2021 3 No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 08:56:08 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 10:52:29 2021 5 Lost MDD Timeout;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Tue Jul 06 10:58:00 2021 5 RCS Partial Service;CM-MAC=d4:04:cd:24:d5:f9;CMTS-MAC=84:8a:8d:33:77:23;CM-QOS=1.1;CM-VER=3.0; Lost MDD timeout and RCS partial service during the day (not during maintenance window) are not normal. Has Cox looked at your modem logs yet? What did they say?
