ContributionsMost RecentMost LikesSolutionsUpstream Issues So, last few days have had a few issues with connectivity and went to check the cable status on a CAX 80 and this is the status...any help? Support is just "reset modem" Cable Diagnostic Status: Poor Action: [Partial Service] If the Partial Service mode does not go away within a few hours (Click the Refresh button after each step): 1) Make sure the coaxial cable is tightly connected. 2) Remove any unnecessary splitters. 3) Replace any required ones. 4) Contact your service provider for troubleshooting help. Internet Access: Good Downstream Status: Good Downstream Power Level: Good Downstream SNR: Good Upstream Status: Poor Partial Service: Poor Cable modem is in partial service mode. Your service provider might be under maintenance. Most of the time it won't affect your traffic and will automatically clear when work is complete. Upstream Power Level: Good Current time: Fri Jun 10 18:53:18 2022 Startup Procedure Acquire Downstream Channel: 429 MHz Locked Connectivity State: OK Operational Boot State: OK Operational Security: Enabled BPI+ Downstream Bonded Channels Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables 1 Locked 256 QAM 45 429000000 Hz 9.7 dBmV 44.9 dB 1151 3979 2 Locked 256 QAM 1 783000000 Hz 6.1 dBmV 42.5 dB 1192 3549 3 Locked 256 QAM 2 789000000 Hz 5.9 dBmV 42.3 dB 1158 3730 4 Locked 256 QAM 3 795000000 Hz 5.5 dBmV 42 dB 1215 3739 5 Locked 256 QAM 4 801000000 Hz 5.8 dBmV 42.1 dB 1244 3693 6 Locked 256 QAM 5 807000000 Hz 5.9 dBmV 42.3 dB 1201 3718 7 Locked 256 QAM 6 813000000 Hz 5.9 dBmV 42.2 dB 1321 3462 8 Locked 256 QAM 7 819000000 Hz 5.5 dBmV 41.9 dB 1360 3357 9 Locked 256 QAM 8 825000000 Hz 5.5 dBmV 41.9 dB 1384 3202 10 Locked 256 QAM 9 831000000 Hz 5.9 dBmV 42.2 dB 1361 3178 11 Locked 256 QAM 10 837000000 Hz 6 dBmV 42.2 dB 1395 3238 12 Locked 256 QAM 11 843000000 Hz 6 dBmV 42.3 dB 1321 3348 13 Locked 256 QAM 12 849000000 Hz 5.6 dBmV 41.9 dB 1316 3437 14 Locked 256 QAM 13 855000000 Hz 5.5 dBmV 41.9 dB 1248 3627 15 Locked 256 QAM 14 861000000 Hz 5.7 dBmV 42 dB 1272 3645 16 Locked 256 QAM 15 867000000 Hz 5.8 dBmV 42.1 dB 1301 3489 17 Locked 256 QAM 16 873000000 Hz 5.5 dBmV 41.8 dB 1320 3357 18 Locked 256 QAM 33 357000000 Hz 9.7 dBmV 44.5 dB 1128 4159 19 Locked 256 QAM 34 363000000 Hz 9.5 dBmV 44.7 dB 1141 4117 20 Locked 256 QAM 35 369000000 Hz 9.4 dBmV 44.7 dB 1157 4025 21 Locked 256 QAM 36 375000000 Hz 9.6 dBmV 44.9 dB 1069 4006 22 Locked 256 QAM 37 381000000 Hz 9.7 dBmV 44.9 dB 1078 3991 23 Locked 256 QAM 38 387000000 Hz 9.8 dBmV 44.9 dB 1027 4011 24 Locked 256 QAM 39 393000000 Hz 9.7 dBmV 44.9 dB 1109 4001 25 Locked 256 QAM 40 399000000 Hz 9.7 dBmV 45 dB 1100 4035 26 Locked 256 QAM 41 405000000 Hz 9.8 dBmV 45 dB 1207 4009 27 Locked 256 QAM 42 411000000 Hz 9.9 dBmV 45 dB 1106 4073 28 Locked 256 QAM 43 417000000 Hz 9.9 dBmV 45.1 dB 140 122 29 Locked 256 QAM 44 423000000 Hz 9.8 dBmV 45.1 dB 1063 4072 30 Locked 256 QAM 46 435000000 Hz 9.8 dBmV 45 dB 1055 4034 31 Locked 256 QAM 47 441000000 Hz 9.7 dBmV 44.9 dB 1112 3963 32 Locked 256 QAM 48 447000000 Hz 9.5 dBmV 44.9 dB 1139 4033 Upstream Bonded Channels Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power 1 Locked ATDMA 2 5120 Ksym/sec 23500000 Hz 41.0 dBmV 2 Locked ATDMA 1 5120 Ksym/sec 16900000 Hz 40.3 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 29900000 Hz 41.8 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 36300000 Hz 42.3 dBmV 5 Locked ATDMA 5 5120 Ksym/sec 60000000 Hz 40.8 dBmV 6 Locked ATDMA 6 5120 Ksym/sec 67000000 Hz 41.5 dBmV 7 Locked ATDMA 7 5120 Ksym/sec 74000000 Hz 43.8 dBmV 8 Locked ATDMA 8 5120 Ksym/sec 81000000 Hz 45.3 dBmV Downstream OFDM Channels Channel LockedStatus ProfileID ChannelID Frequency Power SNR/MER ActiveSubcarrier Unerror Correctable Uncorrectable 1 Locked 0 ,1 ,2 ,3 159 300000000 Hz 10.28 dBmV 44.1 dB 1108 ~ 2987 38291400037 4292224875 10705 2 Not Locked 0 0 0 Hz 0 dBmV 0 dB 0 ~ 4095 0 0 0 Upstream OFDMA Channels Channel LockedStatus ProfileID ChannelID Frequency Power 1 Not Locked 0 0 0 Hz 0 dBmV 2 Not Locked 0 0 0 Hz 0 dBmV Event Log Time Priority Description Fri Jun 10 18:52:48 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:52:48 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:52:37 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:52:35 2022 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:52:25 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:52:23 2022 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:52:05 2022 Critical Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:52:05 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:51:53 2022 Critical Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:49:05 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:48:48 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:47:45 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:47:43 2022 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:47:32 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:47:13 2022 Critical Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:46:43 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:46:28 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:46:14 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:45:48 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:45:02 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:44:59 2022 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:44:29 2022 Critical Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:43:28 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:43:27 2022 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:43:17 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:42:57 2022 Critical Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:42:24 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:42:22 2022 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:42:16 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:41:52 2022 Critical Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:39:54 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:39:09 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:38:06 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:37:49 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:36:21 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:36:19 2022 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:36:10 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:35:49 2022 Critical Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:34:16 2022 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Fri Jun 10 18:34:12 2022 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Intermittent Problems So, Ever since a scheduled repair in my area my internet has been dropping randomly. Before the upgrade I had the Cox Gigablast Modem they told me it was bad I was like cool let me go buy my own now as a justification to upgrade to a better Wi-Fi 6 Modem...Well now everyday at a random time I get T3 Timeouts Talked to 3....Which two have stated "There is an outage in your area" which I followed up with if there is an outage why isn't it reporting through the app to avoid this conversation which got me the prompt let me diagnose your line to see if I need to schedule a technician...It seems as though Cox support wants to squeeze money out of people instead of addressing problems. The 3rd one stated that my modem was bad which is roughly 1 month old...and then I entertained the idea of plugging in the one Cox gave me and it also ...didn't work.... shocker So, now with this wonderful guy telling me there is an outage in my area that isn't being reported and his response is "its not common but it happens" I seriously wish I could cancel this service but sadly it's the ONLY option i have for my address. I pay nearly $200 a month for it and I can't even trust it to be available during work hours since I work from home. Does any body have any thoughts on the cause? CAX80 is fully updated. Already did a factory reset on the modem. Tried the original cox modem same issues. Sat Oct 9 09:00:24 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 09:00:22 2021 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 09:00:22 2021 Critical (3) Ranging Request Retries exhausted;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:59:46 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:59:45 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:59:44 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:59:40 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:59:39 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:59:38 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:59:37 2021 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 5;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:59:37 2021 Critical (3) Ranging Request Retries exhausted;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:59:37 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:59:03 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:53:27 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:53:25 2021 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 6;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:53:25 2021 Critical (3) Ranging Request Retries exhausted;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:46:11 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:46:10 2021 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 7;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:46:10 2021 Critical (3) Ranging Request Retries exhausted;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:43:46 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:43:43 2021 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:43:43 2021 Critical (3) Ranging Request Retries exhausted;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:39:55 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:39:51 2021 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 5;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:39:51 2021 Critical (3) Ranging Request Retries exhausted;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:32:13 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:32:10 2021 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 6;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:32:10 2021 Critical (3) Ranging Request Retries exhausted;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:29:44 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:29:42 2021 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 7;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:29:42 2021 Critical (3) Ranging Request Retries exhausted;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Sat Oct 9 08:28:21 2021 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:6e:5b:d0;CMTS-MAC=c8:84:a1:18:8f:94;CM-QOS=1.1;CM-VER=3.1; Re: Brand new modem That's was my point stating jts linked and working fine but they're stating it wasn't working Brand new modem So long story short. Cox Gigablast was having connection issues so I was like cool modems going bad after like 2 years of usage which is good. So instead of contacting cox to fight to get a new modem again I just went and bought a Netgear Nighthawk CAX80(which is on their approved listing) My speeds went from decent to trash....as in one speed test showed 228 Kbps download and 0.07mbps upload.. Contacted support they said the modem is bad...meanwhile this has happened last time I replaced the modem with a non cox provided one. They tried to reset it and it didn't work so they told me to manually reset it...so me being the smart **** I am knowing *** well my modem is communicating properly with cox signal wise I reset it via the app on my phone that is NOT connected to wifi and it reset instantly... Has anybody had the same issue with what seems to be Cox throttling the connection on modems they don't provide? I've seen one post from a few years back where they stated an agent admitted to it...but the agent I just talked to was like pulling teeth and very poor skills in my opinion Solved