VERY SLOW UPLOAD SPEEDS, download is fine.
I have been dealing with extremely slow upload speeds for a very long time, at least a year. Maybe two? I have gigablast. Download is consistently fine. Always around 900 mbps and above. Upload is sporadic. Very seldom I get the 35mbps. But its very short lasting. Maybe a couple hours, then it goes back down to well under 10mbps. Most of the time it stays under 5mbps. Just ran a speed test, its at 3mbps. Anyways, numerous tech visits. Most of them didn't find anything. Changed all cables from the pole outside, all the way into my house and up to my modem. Its a straight cable from the pole to modem, no splitters. Replaced my modem. Replaced all ethernet cords. Literally replaced EVERYTHING. Still having the same issues. One of the techs said I was getting slow speeds at the pole. Scheduled out a linemen to come check the lines down my street. Linemen said that he found something and that it should be repaired. My upload came up for a few days and stayed consistent, which never happened before, but now its back down again. Dealing with these issues for so long is very, very frustrating and the fact that I pay $160 a month for gigablast and the extra 500gb data and I don't even get a fraction of the speed I am paying for just tops it off. I don't know what else to do. I've just about given up. There's nothing else to replace. If anyone can help it would be greatly appreciated. Because I do not know what else to do. I've browsed many forums and other things on the internet and this seems to be an issues for many people, but i'm hoping someone has a miracle for me. And before anyone asks: YES, i'm directly connected to the modem WIRED and its on multiple devices. Yes I have rebooted it too many times to count.37KViews0likes20Comments
Required Internet Package for Netflix Viewing
I've been with Cox for a few years now and have always had the Preferred Internet Package. I did some research, I found that Netflix only requires 5 Mbps to display HD. Why does Cox warn people that you NEED the Preferred 50Mbps internet package? My internet works just fine now that I switched over to the Starter Internet. Does anybody else have any issues with the 5Mbps internet?9.7KViews0likes4Comments
Preferred Service getting 10Mbps w/3.0 DOCSIS
Good evening, I upgraded a few months back to preferred service with the expectation of an increase of ~45Mbps from what I had prior. What I have now verified with the Cox speed test and the Speedtest.net test are between 10Mbps and 16Mbps down and 5-7Mbps up. I bought a 3.0 DOCSIS to try and mitigate the slow speeds, but I am still not even getting ~25% of the advertised speed. I called a technician and this is what he accomplished/said. He replaced the entire line from the junction box to my house. Once inside he took wireless readings and mentioned that my "tx/rx" were well out of limits. What he did was add another connector from the junction line to the modem as a "band-aid" to at least get my "tx" within limits. After all the work, we were still getting the same internet speed. I have ruled out my computer as the issue as it was able to receive much higher speeds from a buddies house. Additionally my internet speed test is similar on multiple internet capable devices. In the end, the tech said that he was unable to guarantee speeds because 1) it falls in the realm of the contractors for connections outside the realm of the junction box-house connection and 2) he didn't even have a meter to be able to test as all the techs in the region have to share 1 metering device. Thoughts?Solved8.3KViews0likes18Comments
Intermittent Internet - Started Today 10/25/2015
Starting this morning, Sunday 10/25/15 I have been troubleshooting an intermittent internet problem. As always, I reset the cable modem and routers and it would work on the reboot, but then the become intermittent again. I checked the modem (an Arris SURFboard SBG6782-AC)diagnostics and found that due to T3 and T 4 errors, the modem was resetting. On searching for an explanation it appears that low signal levels or noise could be the problem. T3 ( Ranging Request Retries Exhausted ) Explanation: The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem’s power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process. This error message is DOCSIS event message is R03.0, Ranging Request. T4 ( Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received ) Explanation: The cable modem did not received a station maintenance opportunity in which to transmit a Ranging Request (RNG-REQ) message within the T4 timeout period (30 to 35 seconds). The cable modem is resetting its cable interface and restarting the registration process. Typically, this indicates an occasional, temporary loss of service, but if the problem persists, check for possible service outages or maintenance activity on this particular headend system. This error message is DOCSIS event message is R04.0, Ranging Request. This is a cut and paste of the report Time Priority Description Sun Oct 25 18:03:36 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:03:04 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:02:36 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:02:04 2015 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:02:04 2015 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:02:04 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:01:37 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:01:04 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:00:37 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:00:04 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:59:38 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:59:05 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:58:38 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:58:05 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:57:38 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:57:05 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:56:38 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:56:05 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:55:38 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:55:05 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:54:39 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:54:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:53:39 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:53:06 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:52:39 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:52:06 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:51:39 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:51:06 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:50:39 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:50:06 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:49:40 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:49:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:48:40 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:48:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:47:40 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:47:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:46:40 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:46:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:45:40 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:45:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:44:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:44:08 2015 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:44:08 2015 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:44:08 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:43:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:43:08 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:42:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:42:08 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:41:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:41:08 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:40:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:40:08 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:39:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:39:09 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:38:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:38:09 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:37:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:37:09 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:36:42 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:36:09 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:35:42 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:35:09 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:34:43 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:34:10 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:33:43 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:33:10 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:32:43 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:32:10 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:31:43 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:31:10 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:30:43 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:30:10 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:29:44 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:29:11 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:28:44 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:28:11 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:27:44 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:27:11 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:26:44 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:26:11 2015 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:26:11 2015 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:26:11 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:25:44 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:25:11 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:24:45 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:24:12 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:23:45 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:23:12 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:22:45 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:22:12 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:21:45 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:21:12 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:20:45 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:20:12 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:19:46 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:19:13 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:18:46 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:18:13 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:17:46 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:17:13 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0;6.8KViews0likes20CommentsWhy doesn't Cox support 16x4 DOCSIS 3.0 modems?
It is strange to me that the MSO competition (although not in this market) has significantly faster HSI options than Cox, and currently support the newer 16x4 DOCSIS 3.0 modems. If Cox was serious about this whole "Gigablast" rollout by the end of 2016, then one would assume that this would be something of a priority for them. As a long time customer of Cox, I was disappointed to hear that the Netgear CM500 modem (16x4) was not on the approved list, but the Netgear CM400 (8x4) is. I planned to fork over whatever it cost to retrofit for this gigabit internet option, but after seeing that I would need to spend even more money in a year to probably not get a fraction of the advertised speed was disheartening. I wish we had TWC or Comcast as options here in the valley as I would change providers right now. This may sound like a rant and quite possibly is, but the only difference in hardware between the two modems is the amount of downstream channels they have. This is ultimately irrelevant since the ISP determines your internet speeds. The most frustrating part is that the approved modem which can handle half the speed of the non-approved one; is only $20 less than the better one. Thank you Cox for still finding a way to cost me more money....I hope Google Fiber or CenturyLink rollout before Cox does, because that is where my money will go.5.8KViews0likes3Comments
Internet connection slow
Having issues where my internet connection slows to a crawl. My upload speed test will return 0.01mbps. Having a hard time staying connected in online games and even browsing the internet. This happens randomly. Router is a Netgear nighthawk r7000. Modem Netgear CM500 Both are new. Issues were happening before they were replaced.4.8KViews0likes13CommentsStop blaming Cox, you whiners!
Since I first discovered this forum I've read many dozens of questions in which users blame Cox for their email or internet problems. Many others chime in with posts like "Yeah, I have the same problem" or something like "Me too. I'm sick of it. Cox **" But have these whiners called Cox technical support, describing their problem in an intelligible and thoroughly descriptive manner? I can surmise from the posts and replies that the answer is mostly "No". My experience with Cox has been more then satisfactory. I did have to call Cox technical support once for a modem issue that only they could resolve.. And they did, in a heartbeat. If you have internet problems and your device is a PC then I can tell you the primary source of such problems are: - Registry cleaners like Ccleaner et al. If you let programs such as this modify your registry you might as well reinstall Wndows to get it working properly again. - Installing device drivers from "who knows where". - 3rd-party ant-malware software. You don't need that **. Rely on Windows Defender. - Editing your registry or configuration based on info from non-Microsoft websites or upon the advice of your neighbor's cousin's 14 year old "PC guru" son. And the list goes on. I'm an EE and certified IT specialist. Let Windows take care of itself. Uninstall 3rd party anti-malware software. Don't install drivers from ANY of the many "device driver" sites. Don't open emails from sources you don't recognize and don't go browsing where you shouldn't be browsing. Or you could install one of the many Linux distros. But if you're not an expert coder you'll find yourself up the creak without a paddle. At this point all I can say is that I'm running Window 10 with all current updates installed and my device drivers are maintained by appropriate sources. Windows runs great and my Cox internet connectivity is impeccable. If you have a problem, call Cox. Most of the recommendations you may receive here are 3rd party misinformation, even from the moderator (sorry, whoever you are but dems da facts).4.3KViews0likes11CommentsPaying for Premium 100mbps but only getting about 10-20mbps
Just recently had cox internet set up at my place and I tested the internet the other day multiple times and the fastest I have seen it at is around 20mbps download. Sometimes it dips to just 10mbps. I am paying for the premier service 100mbps, so I am wondering where I am losing speed? I have a brand new Motorola SB6141 Modem and new AC1200 Linksys router, both rated for well above the 100mbps, so they can't be the culprit. I am wondering is there specific settings I need to configure on my router to improve the speed or is this something I just need to call Cox about?3.7KViews0likes5Comments
New Motorola Arris sb6183 only bonding 8 channels and slower than old Zoom on 300 ultimate HELP!
My area was recently updated to Ultimate 300 and when the change happened I didn't notice my speed jump at all. I chatted with tech and they told me i needed a 16x4 modem vs my old 8x4. I was bonding 8 channels on the old and when initial plugging in the new modem it was only bonding 4 channels. A few hours after install it jumped to 8 but my speeds are horrible! They are ranging from 20mpbs to 140mbps. No where near 300 or even 200mpbs. I have chatted with tech support again and they said something wasn't set right and changed some things but it did nothing. Speeds actually got slower. They don't know how to get the modem to bond to 12 or 16 channels to get the rest of my speed. Any help?!?3.6KViews0likes6Comments
Cox Gigablast - Video buffering issues
I have been with Cox Gigablast for 3-4 months now. I am getting poor video streaming quality compared to what I used to receive when I was on their Preferred plan (30mbps). I have tried this on several websites that we have been using for 8+ years and all the buffering issues have cropped up since we installed GigaBlast :( I have tried this on connected-mode and in wireless. I just had a better experience with CoxInternet when I was on CoAx .. The speeds are in excess of 700Mbps upload and download when I do the Internet speedtest with Fiber. But the constant "bufferring" during video playback is very annoying. It defies common sense. Anyone facing this issue and have any suggestions?3.6KViews0likes1Comment
Stop blaming Cox, you whiners!
Since I first discovered this forum I've read many dozens of questions in which users blame Cox for their email or internet problems. Many others chime in with posts like "Yeah, I have the same problem" or something like "Me too. I'm sick of it. Cox **" But have these whiners called Cox technical support, describing their problem in an intelligible and thoroughly descriptive manner? I can surmise from the posts and replies that the answer is mostly "No". My experience with Cox has been more then satisfactory. I did have to call Cox technical support once for a modem issue that only they could resolve.. And they did, in a heartbeat. If you have internet problems and your device is a PC then I can tell you the primary source of such problems are: - Registry cleaners like Ccleaner et al. If you let programs such as this modify your registry you might as well reinstall Wndows to get it working properly again. - Installing device drivers from "who knows where". - 3rd-party ant-malware software. You don't need that **. Rely on Windows Defender. - Editing your registry or configuration based on info from non-Microsoft websites or upon the advice of your neighbor's cousin's 14 year old "PC guru" son. And the list goes on. I'm an EE and certified IT specialist. Let Windows take care of itself. Uninstall 3rd party anti-malware software. Don't install drivers from ANY of the many "device driver" sites. Don't open emails from sources you don't recognize and don't go browsing where you shouldn't be browsing. Or you could install one of the many Linux distros. But if you're not an expert coder you'll find yourself up the creak without a paddle. At this point all I can say is that I'm running Window 10 with all current updates installed and my device drivers are maintained by appropriate sources. Windows runs great and my Cox internet connectivity is impeccable. If you have a problem, call Cox. Most of the recommendations you may receive here are 3rd party misinformation, even from the moderator (sorry, whoever you are but dems da facts).