Intermittent internet connection loss, Airport Extreme (newest version) router and SB6141 modem
For several weeks I have experienced intermittent loss of connection to internet, sometimes resolving spontaneously but other times requiring reboot (power off/power on) of cable modem (Arris SB6141). Cox support by (phone and by local technician visits to home) show proper signal levels to modem. Arris/Motorola support also says modem checks out OK, according to signal levels, etc., in the modem status pages. Internet speed test for my level of service (Preferred) has been normal when the internet connection is present. The connection loss in recent weeks is typically in the 12 midnight to 2:00 am time period. On the two most recent occasions Cox reps denied a known maintenance outage, stated my problem was unique. Local in-home wifi network works fine; only internet connection is lost. On my latest call to cox tech support, the tech ran tests and suspected a problem with the cable modem (Arris SB6141) and arranged for a new modem to be shipped to me (Cisco DPC3010). This arrived but I have not connected it yet, pending further research. Researching the issue, I found reports of alleged incompatibility between Cox and the Airport Extreme router, possibly related to Cox’s IPv6 implementation of IPv6 and the AE router IPv6 settings. There are also reports of incompatibility between the Arris Sb6141 modem and the AE router. Question: Are there any setup parameters in the Airport Extreme router that I should try before changing out to the new modem? Something perhaps related to interaction between the AE router and SB6141 modem, or between the AE router settings and Cox’s IPv6 requirements? My current router settings are Configure IPv6 “Automatically” (other choices are “link-local only” and “manually”) and IPv6 Mode “Native” (other choice is “tunnel”).56KViews0likes31Comments
Internet Loses Connection Constantly
I keep losing internet connection about every 5 minutes during the evening. It's almost like it resets itself and then comes right back for another 5 minutes. Gets very annoying after a while. I have the following modem: Make and Model:DCI382R It's something wrong with the internet or the modem as it happens with all of my devices (laptop, phone, iPad, etc.). Is there something I can try or do I need a new modem/router? Thanks!13KViews0likes21CommentsHigh saturation node, slow internet speeds, intermittent drops and nothing they can do?
I'm hoping to get some additional assistance for our internet woes. We contacted Cox on April 15th because we experienced an outage with our internet service. This outage was longer than we had been experience for the last month or so so it was time to call. We were greeted with a recording indicating Cox was working on some upgrades in our area and that users might experience intermittent outages between midnight and 6am.We chalked it up to their maintenance window and let it go for the evening. The next day wenoticed we were experiencing slower than normal internet speeds, in our case, less than half of our potential 150Mbps download speed. We did some internal troubleshooting, resettingour router, re-provisioning our cable modem through the automated system, factory resettingour cable modem and eliminated the router altogether, going straight from computer to cable modem for testing. All tests are done using hardwire, either through a router or directly from the cable modem. WIFI was not used during any of this testing. A majority of the responses were the same, download speeds generally ranged between 70-90Mbps fromearly afternoon into late evenings. There were sporadic results that showed closer to "normal download levels around 110-130Mbps but those were not consistent; we saw many more of the abnormal download speed results than "normal" ones. An appointment was eventually made for a technician to come out and take a look at everything on the outside of the home on 4/20. We received a call from a technician the morning of 4/18 about our service call. The technician indicated he was looking at the node we're attached to and said it was over 80% saturated and that slows speeds and drop outs were somewhat expected given the high level of saturation. The technician indicated he looked at everything and everything looked good, levels were good and there was really nothing he would be able to do about the situation and cancelled our service call for 4/20. A number of days later, our connection appears to be getting worse, with speeds generally ranging in the 60-80Mbps range in the early afternoon through late evening. Again, we still have some results in the 100-120Mbps range but those are far fewer than the 60-80Mbps range. We're also experiencing more drop outs (loss of connection lasting 5-15 seconds) and increased frustration. We understand download speeds are an "up to" but we're generally not getting anything close during the waking hours. Is there anything else we can do to address these issues in the short term? We have been forced, like many others, to work remote andour ability to provide support has been impacted with these connectivity related issues. Here are some recent examples of speed tests using Cox's speed test portal: PING:11ms JITTER:5ms DOWNLOAD:65.8 Mbps UPLOAD:10.0 Mbps PING:20ms JITTER:96ms DOWNLOAD:66.8 Mbps UPLOAD:9.9 Mbps PING:11ms JITTER:2ms DOWNLOAD:62.3 Mbps UPLOAD:10.1 Mbps PING:10ms JITTER:4ms DOWNLOAD:73.2 Mbps UPLOAD:10.2 Mbps10KViews0likes39Comments
Now....Bad wi fi connection
Hi, within the last 3 months or so, My laptop and iphone have been not receiving a good solid signal. I lose internet on both and it's increasingly frustrating as the problem is getting worse. Our router has always been sufficient. What's going on and why am I having these problems now? What is different or changed on your end? Thanks.Solved7KViews0likes13CommentsIntermittent 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.8KViews0likes20Comments
Random high latency spikes
I am in CT and since Tuesday morning I receive high latency spikes from most websites and servers I go to - from Facebook and Google to gaming servers and even VPN for work (which my office also has Cox). I had a tech come out yesterday and inspect my lines - he said they were perfect (my house is only 6 years old and the drop from the box to my house was installed just a few months ago). When I called Tier 2 again I had to give them 3 sets of pings and traceroutes; I provided Google, Facebook, and io9.com. The person I talked to sent them somewhere (network engineers, maybe?) and called back 10 minutes later saying it wasn't anything happening in the Cox network, that my ping and traceroute packets are being deprioritized after the Cox network. I'd agree with this if it was just the three sites that I provided the data for, but when it's every single site I visit - again, websites, gaming servers, servers at work through a VPN tunnel, I highly question whether all of those servers will be deprioritizing my network traffic (and why would they deprioritize non ping/traceroute packets?). I'm extremely frustrated since this makes working extremely difficult. Of course Cox engineers are going to say it's not them. When I VPN into a machine at my office and perform the same traceroutes/pings I don't get the high latency spikes that I'm experiencing from home. What are my options? Should I continue to call Tier 2 and demand a better explanation as to why all of my traffic is "being deprioritized"?6.7KViews0likes15CommentsIntermittent/random drops of internet connection: SURFboard SBG6782-AC
Since upgrading to a SURFboard®SBG6782-AC all in one Modem/Wifi/Router combo (I know, bad idea), all the devices on our network are experiencing short and intermittent drops from internet access randomly. The devices remain on the wifi network, but lose their internet connections for a few minutes at a time. This happens multiple times a day. The modem/router stays on and does not power cycle when this happens. On a weird and maybe related side note: the majority of the time when trying to load google.com, do searches on google and opening youtube links all seem to take longer than other web pages, sometimes by several minutes. This happens when using different browsers. I've tried to diagnose the problem and there's just too much information out there for me to zero in on the cause. Here are logs and other info to help: Startup Procedure Procedure Status Comment Acquire Downstream Channel Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked QAM256 121 813000000 Hz 2.7 dBmV 40.8 dB 11 0 2 Locked QAM256 122 819000000 Hz 2.8 dBmV 40.3 dB 26 0 3 Locked QAM256 123 825000000 Hz 2.6 dBmV 40.3 dB 19 0 4 Locked QAM256 124 831000000 Hz 2.7 dBmV 40.4 dB 34 0 5 Locked QAM256 129 861000000 Hz 2.0 dBmV 39.9 dB 22 0 6 Locked QAM256 130 867000000 Hz 1.9 dBmV 39.4 dB 40 0 7 Locked QAM256 131 873000000 Hz 2.2 dBmV 39.4 dB 45 0 8 Locked QAM256 132 879000000 Hz 2.0 dBmV 39.4 dB 34 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked TDMA and ATDMA 4 2560 Ksym/sec 18896000 Hz 44.0 dBmV 2 Locked ATDMA 1 2560 Ksym/sec 37104000 Hz 45.5 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 30704000 Hz 45.5 dBmV 4 Locked ATDMA 3 5120 Ksym/sec 23696000 Hz 44.0 dBmV Time Priority Description Mon Apr 20 16:47:44 2015 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Fri Apr 17 13:07:54 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Fri Apr 17 12:52:50 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Fri Apr 17 11:00:04 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Fri Apr 17 10:45:00 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Fri Apr 17 08:44:28 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Fri Apr 17 08:29:24 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Fri Apr 17 05:28:36 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Fri Apr 17 05:13:32 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Fri Apr 17 04:47:44 2015 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Fri Apr 17 04:28:20 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Fri Apr 17 04:13:16 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Fri Apr 17 03:28:04 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Fri Apr 17 02:57:56 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Thu Apr 16 20:39:34 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Thu Apr 16 20:24:30 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Thu Apr 16 16:47:44 2015 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Wed Apr 15 19:59:27 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Wed Apr 15 19:44:23 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Wed Apr 15 17:58:55 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Wed Apr 15 17:43:51 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Wed Apr 15 16:47:44 2015 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Wed Apr 15 04:48:37 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Wed Apr 15 04:47:45 2015 Notice (6) TLV-11 - unrecognized OID;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Wed Apr 15 04:47:45 2015 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Wed Apr 15 04:47:33 2015 Notice (6) Honoring MDD; IP provisioning mode = IPv4 Wed Apr 15 04:47:22 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:46:53 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:46:53 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:46:46 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:46:45 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:46:28 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:46:28 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:45:24 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:45:24 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:45:21 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:45:20 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:45:16 2015 Notice (6) Ds Pulse Failed - Reinitialize MAC... Wed Apr 15 04:45:04 2015 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:44:05 2015 Notice (6) Honoring MDD; IP provisioning mode = IPv4 Wed Apr 15 04:43:55 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:43:41 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:43:41 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:42:28 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:42:28 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:42:17 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:42:17 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:42:16 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:42:15 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:40:25 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:40:24 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:39:33 2015 Notice (6) Ds Pulse Failed - Reinitialize MAC... Wed Apr 15 04:39:32 2015 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:39:05 2015 Notice (6) Honoring MDD; IP provisioning mode = IPv4 Wed Apr 15 04:38:55 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:38:51 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:38:50 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:38:40 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:38:39 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:35:12 2015 Notice (6) Ds Pulse Failed - Reinitialize MAC... Wed Apr 15 04:35:10 2015 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.0;CM-VER=3.0; Wed Apr 15 04:34:43 2015 Notice (6) Honoring MDD; IP provisioning mode = IPv4 Wed Apr 15 04:34:30 2015 Notice (6) T4 No Station Maint Timeout - Reinitialize MAC... Wed Apr 15 04:34:30 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Wed Apr 15 04:32:30 2015 Warning (5) MDD message timeout;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Wed Apr 15 04:32:26 2015 Critical (3) SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Tue Apr 14 22:08:38 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Tue Apr 14 21:53:34 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Tue Apr 14 17:52:30 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Tue Apr 14 17:37:26 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Tue Apr 14 17:07:18 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Tue Apr 14 17:04:31 2015 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Tue Apr 14 16:52:14 2015 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE Tue Apr 14 16:37:10 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Tue Apr 14 11:50:54 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Tue Apr 14 11:35:51 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Tue Apr 14 10:35:34 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Tue Apr 14 10:20:30 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Tue Apr 14 05:04:32 2015 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Mon Apr 13 22:02:14 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Mon Apr 13 21:47:11 2015 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE Mon Apr 13 17:04:31 2015 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Mon Apr 13 15:30:30 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Mon Apr 13 15:15:26 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Mon Apr 13 14:00:06 2015 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE Mon Apr 13 13:45:02 2015 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE Mon Apr 13 05:04:31 2015 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Sat Apr 11 05:05:18 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Sat Apr 11 05:04:33 2015 Notice (6) TLV-11 - unrecognized OID;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Sat Apr 11 05:04:33 2015 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:1e:be:ff:45:c6;CM-QOS=1.1;CM-VER=3.0; Sat Apr 11 05:04:27 2015 Notice (6) Honoring MDD; IP provisioning mode = IPv4 Sat Apr 11 05:04:17 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Sat Apr 11 05:01:28 2015 Notice (6) Ds Pulse Failed - Reinitialize MAC... Sat Apr 11 05:01:17 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Sat Apr 11 05:00:49 2015 Notice (6) Ds Lock Failed - Reinitialize MAC... Sat Apr 11 05:00:49 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Sat Apr 11 05:00:48 2015 Warning (5) Lost MDD Timeout;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Sat Apr 11 05:00:40 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Sat Apr 11 04:58:30 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Sat Apr 11 04:58:29 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:5f:0c:e5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;6.1KViews0likes3Comments
Intermittent Disconnects from Cox....FRUSTRATING
We have been experiencing an increasing number of "disconnects" (T3/T4) from the Internet with our Cox Preferred service. I have recently installed a NEW modem (SurfBoard6183) and use Apple's newest wireless router. We have had a Cox contractor service representative at our home and he says the levels are fine. He is the latest dropout log from my modem: Time Priority Description Tue Nov 24 21:48:14 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; Tue Nov 24 21:47:31 2015 Notice (6) TLV-11 - unrecognized OID;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Tue Nov 24 21:46:51 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; Tue Nov 24 21:44:41 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; Tue Nov 24 21:43:58 2015 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; Tue Nov 24 21:43:56 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; Tue Nov 24 21:43:51 2015 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; Tue Nov 24 10:53:08 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; Tue Nov 24 10:52:09 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; Tue Nov 24 10:51:32 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Tue Nov 24 10:50:39 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; Tue Nov 24 10:48:29 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9d:90:0d;CMTS-MAC=bc:16:65:27:6e:b3;CM-QOS=1.1;CM-VER=3.0; I am looking for help from COX... My research indicates the problem may be at their end, i.e. the wire from the pole, any trap on my line etc etc.5.3KViews0likes10CommentsModem Resets itself all the time
Hello, Our internet is dodgy at best. If we have 4 home devices on it, one or multiple start to lag tremendously. Also, the modem goes through spurts where it just resets itself over and over again. I erased all of our MAC Addresses, but I posted the log below. With my educational and professional background, it looks like the signal is not coming from Cox like it should. The signal is being lost somewhere. Any thought on what to do or look for? And, no, there are no splitters. There is a cable from the wall to the modem. We have 2 ethernet cables coming from the back of the modem going to 2 computers. Everything else is on WIFI. Time Priority Description Thu Jun 09 20:05:01 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0; Thu Jun 09 20:04:18 2016 Notice (6) TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; Tue Jun 07 12:25:16 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=:d0;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; Tue Jun 07 12:24:16 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=8;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:24:02 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:22:09 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:22:08 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:19:11 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:19:10 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:18:54 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:18:53 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:18:07 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:18:06 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:17:43 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:17:41 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:17:37 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:17:36 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:16:50 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:16:49 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:15:47 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:15:45 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:15:18 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:15:17 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:14:45 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:14:44 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:14:35 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:14:33 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:14:29 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Tue Jun 07 12:14:28 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1 Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INITSolved5KViews0likes1Comment
High saturation node, slow internet speeds, intermittent drops and nothing they can do?
I'm hoping to get some additional assistance for our internet woes. We contacted Cox on April 15th because we experienced an outage with our internet service. This outage was longer than we had been experience for the last month or so so it was time to call. We were greeted with a recording indicating Cox was working on some upgrades in our area and that users might experience intermittent outages between midnight and 6am.We chalked it up to their maintenance window and let it go for the evening. The next day wenoticed we were experiencing slower than normal internet speeds, in our case, less than half of our potential 150Mbps download speed. We did some internal troubleshooting, resettingour router, re-provisioning our cable modem through the automated system, factory resettingour cable modem and eliminated the router altogether, going straight from computer to cable modem for testing. All tests are done using hardwire, either through a router or directly from the cable modem. WIFI was not used during any of this testing. A majority of the responses were the same, download speeds generally ranged between 70-90Mbps fromearly afternoon into late evenings. There were sporadic results that showed closer to "normal download levels around 110-130Mbps but those were not consistent; we saw many more of the abnormal download speed results than "normal" ones. An appointment was eventually made for a technician to come out and take a look at everything on the outside of the home on 4/20. We received a call from a technician the morning of 4/18 about our service call. The technician indicated he was looking at the node we're attached to and said it was over 80% saturated and that slows speeds and drop outs were somewhat expected given the high level of saturation. The technician indicated he looked at everything and everything looked good, levels were good and there was really nothing he would be able to do about the situation and cancelled our service call for 4/20. A number of days later, our connection appears to be getting worse, with speeds generally ranging in the 60-80Mbps range in the early afternoon through late evening. Again, we still have some results in the 100-120Mbps range but those are far fewer than the 60-80Mbps range. We're also experiencing more drop outs (loss of connection lasting 5-15 seconds) and increased frustration. We understand download speeds are an "up to" but we're generally not getting anything close during the waking hours. Is there anything else we can do to address these issues in the short term? We have been forced, like many others, to work remote andour ability to provide support has been impacted with these connectivity related issues. Here are some recent examples of speed tests using Cox's speed test portal: PING:11ms JITTER:5ms DOWNLOAD:65.8 Mbps UPLOAD:10.0 Mbps PING:20ms JITTER:96ms DOWNLOAD:66.8 Mbps UPLOAD:9.9 Mbps PING:11ms JITTER:2ms DOWNLOAD:62.3 Mbps UPLOAD:10.1 Mbps PING:10ms JITTER:4ms DOWNLOAD:73.2 Mbps UPLOAD:10.2 Mbps
