Cox ruining Fortnite and Live Streaming experience with PACKET LOSS
Okay I started getting packet losses two months ago, which is like a freaking cancer. I did everything from switching coax, hard wiring modem to pc, new ethernet cords, even buying a new modem and sending cox the one they rented me out (new modem is cox compatible Netgear Nighthawk c7000). spoke to probably more than 20 techs online who by the way all did the same thing, reset my modem and cleared the cache. I had two techs come out to look at my house and one changed the lines, which did absolutely nothing, probably made it worst. The next one came and connected my modem into his little device and he said that everything was good, and he left. Now i look like the boy who cried wolf, but i know for *** sure i'm not the only one having this stupid problem. It seems to always happen more at night than in the morning, network congestion or what? Why is there no cure to this cancer yet, seriously... what do we have to do, EVEN if i get another tech sent out to my house what will they do? look at the modem and say its good? they have no idea how to approach this situation. I have the ultimate package w/ the unlimited data plan bringing me the max amount of $ i could pay for internet with cox, I for *** sure know i'm getting ripped off, I'm probably better plugging my computer directly into a potato. Packet losses ranging from 10%-60% all night long, jittery gameplay, unable to live stream AT ALL download speeds are reading as it should, normally 200-300 mpbs... but upload, oh yes upload speeds are a whopping Less than 1mpbs...(paying for 30mbps btw) every night, tried every speed test site i could find, the meter stick doesn't even move, looks like its trying to go backwards if anything. I hate this city for only having cox as the main isp that offer high speeds lol. god this ** so bad, vent over. solution you wont find, i just wanted to complain and get this off my chest since cox doesn't do anything with reimbursing me from all this stress and frustration. Unplugging modem for 10 seconds and plugging it back in now for the 42,371,284th time...Solved56KViews2likes53Comments
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!13KViews0likes21Comments
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 Mbps10KViews0likes39CommentsPoor DNS Intermittent service unavailable
I am running a new Arris (Motorola) Surfboard SBG6580 on a Windows 7 machine. This started in mid December and I had my network engineer son-in-law look at it. I have had Cox out once (his suggestion: change from Firefox to Chrome). When that did not work, I called Cox again. They wanted $60 to clean the malware. I ran four anti-malware apps, none of which found anything. The problem continues. When I call in, they want me to run Speedtest, which always tests excellent when they are on the line. It timed out on the ping while I was waiting on hold. As soon as they are on, it works fine. Same problem with a Win 8 Wi-Fi connected machine. I have replaced the modem. I can't find if this modem/router is caching the DNS, but I have the DNS pointing at Cox as a static DNS. Speedtest told me it was the fastest DNS for me. Cox tells me the modem has the latest software release. If I turn it off and back on, it will work great for about an hour, then goes south again. Don't think I should be resetting the modem each hour. Gateway diagnostics shows: Startup Procedure Procedure Status Comment Acquire Downstream Channel Locked Connectivity State OK Operational Boot State OK Operational Configuration File Security Enabled BPI+ Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 104 855000000 Hz -7.7 dBmV 39.0 dB 334 0 2 Locked QAM256 101 837000000 Hz -7.7 dBmV 39.0 dB 707 694 3 Locked QAM256 102 843000000 Hz -7.2 dBmV 39.1 dB 247 0 4 Locked QAM256 103 849000000 Hz -7.5 dBmV 38.6 dB 431 0 5 Locked QAM256 105 861000000 Hz -6.3 dBmV 39.6 dB 195 0 6 Locked QAM256 106 867000000 Hz -6.7 dBmV 38.6 dB 182 0 7 Locked QAM256 107 873000000 Hz -6.7 dBmV 38.5 dB 298 0 8 Locked QAM256 108 879000000 Hz -5.8 dBmV 39.1 dB 101 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 2 5120 Ksym/sec 26500000 Hz 42.2 dBmV 2 Locked TDMA and ATDMA 1 2560 Ksym/sec 21600000 Hz 42.2 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 33000000 Hz 42.2 dBmV 4 Locked TDMA and ATDMA 4 2560 Ksym/sec 37900000 Hz 42.2 dBmV Any assistance/ideas would be helpful.8.8KViews0likes18Comments
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.Solved7KViews0likes13Comments
Intermittent/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.1KViews0likes3CommentsInternet quality intermittently bad causing drops of service over the past few weeks
When it works, it works great. Then it doesn't and it keeps dropping for hours. I'm having frequent packet loss and connectivity issues over the past few weeks after several months of low to no issues on 4 different WIRED computers. This happens daily in waves. Sometimes the quality is good for a few hours, but usually it drops every few minutes for hours on end. I've been running ping plotter to monitor for connectivity. https://imgur.com/a/9cRQv7k Usually when it goes out: Actively running Netflix, YouTube, and general web browsing seems uninterrupted unless it's trying to start up a new one. I can still view and hear others on currently joined video calls or streams. The quality of myvoice and video degrades to the point that others on the call can't see or hear and eventually I get dropped Just this bit makes me think it's a problem with the upstream channels possibly having noise or an issue in the network in that direction. I've wasted days working with the online support chat and I've calling support. it doesn't seem like they have the tools or know-how to get to the bottom of the issue. Often it seems they jump to conclusions I without evidence and few of the things they have determined: My modem needs a reboot. This is the first thing every time and I've already done it. Everything is fine. This is usually the final conclusion every time I call. A fine Jedi mind trick, but they're not Jedi. There's probably a virus on all my computers and I need Cox Complete Care. I don't have enough bandwidth and I need to upgrade to the Gigablast plan. I feel stupid for even giving this one a try and am not happy about the zero results. It's my modem. I've replaced my modem a number of times duesupport suggesting the modem is faulty over the years. Never once has it remedied the issue. My current (newest best) modem has been working fine for months before these issues cropped up. Cox says it's the modem. Arris says it's Cox. :-| I need Panoramic WiFi and that will fix it. Nice try on the upsell. Xbox consoles are eating all the bandwidth because they have a lot of graphics. This is laughable and nonsense. Even if it made sense I don't even have an Xbox. They need to send a tech out to look at the cable lines and modem I've had a tech out to look at the lines and they reported the signals and modem look good. All the channels look to be in range and there's no ingress. It feels more like the support channels are really just sales channels. There doesn't appear to be a next step beyond sending out a tech. I'd switch providers, but there's nothing else available. I'm not sure where to go from here.Solved5.6KViews0likes7Comments
Help! Connection Keeps Dropping. (Router Logs)
Help me figure out what is going on. I am a strong gamer and have the xbox one i am having issues with my connection dropping in the middle of games. Also have strict NAT. Modem i am using is DOCSIS 3.0 N450 This is very irritating and has me thinking i chose the wrong service. Here are my logs from my router... Sat Sep 05 01:37:17 2015 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=64:00:f1:3f:fc:a0;CM-QOS=1.1;CM-VER=3.0; Sat Sep 05 01:37:17 2015 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=64:00:f1:3f:fc:a0;CM-QOS=1.1;CM-VER=3.0; Sat Sep 05 01:37:17 2015 Notice (6) TLV-11 - unrecognized OID;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=64:00:f1:3f:fc:a0;CM-QOS=1.1;CM-VER=3.0; Fri Sep 04 12:16:58 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=64:00:f1:3f:fc:a0;CM-QOS=1.1;CM-VER=3.0; Fri Sep 04 01:35:31 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=64:00:f1:3f:fc:a0;CM-QOS=1.1;CM-VER=3.0; Mon Aug 24 10:42:04 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=64:00:f1:3f:fc:a0;CM-QOS=1.1;CM-VER=3.0; Sun Aug 23 16:50:24 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=64:00:f1:3f:fc:a0;CM-QOS=1.1;CM-VER=3.0; Sun Aug 23 16:48:37 2015 Critical (3) Resetting the cable modem due to docsDevResetNow Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=64:00:f1:3f:fc:a0;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=64:00:f1:3f:fc:a0;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=64:00:f1:3f:fc:a0;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:2b:8c:d7:8c:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INIT5.1KViews0likes10CommentsDropping packets and unreliable internet connection
I have had this issue several times. Just called in again to get it resolved. I have been in IT for over 10 years and this is ridiculous. I work from home primarily and cannot have an unreliable internet connection. At least once a week lately I get issues and see consistently over 25% packet loss. I see this pinging 8.8.8.8 (google open DNS server) or cox.net or any website. Sometimes simply disconnecting power and reseating the cable modem will resolve, others I have to call in or have a tech come out. I have had more issues since moving to my current address and they continue to go unresolved. Yet I pay my bill and have never even been offered a credit or any form of compensation for continuing issues with my services. I've been with Cox over 8 years. I've even previously had support tell me my router was the issue - ludicrous considering I have had a field tech come out and connect his equipment and also see the same loss testing the lines. But to appease support I bought a new $150 router. What does it take to get Cox to resolve this issue once and for all? I'm at the point of cutting services way down (dropping my bundle) and adding AT&T as a secondary connection to my router so I can have consistent internet and simply streaming all of my TV. Is this what I need to do? Or is Cox going to be able to finally resolve my issues permanently and do something for customer retention? Current signals from cable router after finally getting back online Downstream Channels Power Level: Signal to Noise Ratio: Channel 1: 15.5dBmV 39.5dB Channel 2: 15.4dBmV 39.9dB Channel 3: 15.4dBmV 39.3dB Channel 4: 15.0dBmV 39.6dB Channel 5: 13.9dBmV 39.5dB Channel 6: 13.8dBmV 39.5dB Channel 7: 13.6dBmV 39.1dB Channel 8: 13.4dBmV 39.4dB Upstream Channels Power Level: Channel 1: 46.5dBmV Channel 2: 45.7dBmV Channel 3: 46.2dBmV Channel 4: 45.2dBmV4.9KViews0likes5Comments
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
