Cox port data throttle question
Multiple people in my house are trying to play the same game. The game needs to communicate over ports: TCP 54992-54994, 55006-55007, 55021-55040 From working at spectrum/charter in the past, I know there is a throttle limit for data when it comes to uncommon ports. I know service reps also have no idea what I am talking about if I were to call them. Most of our "head end" techs were unaware of this as well. My question is, who do customers contact or how do we convey to our ISP that data over certain ports shouldn'tbe throttled when multiple users need to use them?
High packet loss, extremely slow speeds, and modem errors
Hello! As of a few days ago after I have recently purchased an aftermarket modem (Netgear cm600) I have noticed that at during certain times of the day the connection of the internet will just drop incredibly low and will pertain for quite a few hours. I have always had high ping on one game abnormally named League of Legends, where I usually sit at 78-85 ping which instead should be 50-55 ping. That's not really the issue as of right now though, as I end up having about 92 ping on the game whenever this happens but on top of that I end up dealing with 15-25% packet loss which is extremely detrimental and makes the game feel like I'm playing on 300 ping. From just general research on the internet of where people have had similar problems, I've seen that sometimes the registration processes just haven't been fully done which would be generally possible since this router has just been registered recently. There is also the possibility that the line near my house is faulty and needs to be updated, but other than that I guess that would be up to you guys to figure out. If I could nip this in the butt and to also possibly figure out why I am not getting the ping I should be getting in my video games I would greatly appreciate that. I'd like to for sure figure out why I am dealing with this packet loss though as this is extremely detrimental. I can't surf the internet without pages taking a long time to load and my games feel torturous. Here are my modem logs ever since I have received it. 2020-05-11, 13:08:25 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-11, 11:48:31 Warning (5) Unicast DSID PSN startup error 2020-05-11, 11:46:05 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-11, 11:37:30 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-11, 11:36:25 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-11, 11:36:11 Notice (6) TLV-11 - unrecognized OID;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-10, 12:50:01 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-06, 23:10:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-05, 16:04:53 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-04, 14:12:10 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-04, 14:10:12 Critical (3) Resetting the cable modem due to docsDevResetNow 2020-05-04, 14:09:39 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-04, 14:06:55 Critical (3) Resetting the cable modem due to docsDevResetNow 2020-05-03, 16:56:12 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2019-06-02, 15:16:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=redacted;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;