Cox service is making me lose my hair!!!
UPDATE 2/7: today the internet went out andas usual it happened in the same time like before. UPDATE 2/6: so I had a tech come in on Thursday [2/4] to look at the "issue" and they said that it was the POE filter and the splitter that was installed on the main line that's causing the disconnections. They said it was not up to spec with their network. Okay so they replaced it with their own as well as replaced the coax cables that's connected from the outlet to my modem. Today [2/6] I've now experienced a disconnection for 10 mins instead of a mere 1-2 mins prior to this "fix". So I pretty much spent $100 of my money just to get a worse network experience. I, and others in my household, rely on your network 24/7 not just for leisure but also for workand cannot have interruptions this severe. I am now contemplating on reporting this to the FCC the more issues I experience. I've been having issues everyday at the same timeframe with my gigablast. I've never had an issue before but so far it has started on the 2nd week of January to now and it had only worked without issue for two days straight last week.. My network connection would cut off multiple times around 11am-2pm everyday and whenever I ask assistance they would always tell me that they'll send out a tech to check my connection. I've factory reset my modem and router a million times, switched over to another coax port in the house, have tried having a direct connection from the main line to one coax port (no splitter), I've done having direct connection to the modem and all these steps have not resolved the issue. The website says that there are no outages, maintenance, service interruptions whatsoever but there clearly is. It seems Cox isn't as responsive unless it about bill pay. Customer Support would always pull a "let's have a tech come in to check your connection", no my connection isn't the issue, the residents in the vicinity is having the issue andCox doesn't seem to understand that. I've asked multiple times to check the main line that goes in our area but no one is sent to check it. There are multiple reports even on Downdetector of the same issue I'm experiencing.You're Not Crazy It's Happening To Everyone
I can't read one more. I can't read one more post that says, "my modem drops dozens of times a day, and comes back up minutes later, sometimes it's unusable for HOURS, I've rebooted, and reset, and refreshed, and I've replaced ALL of my equipment, I've called Cox dozens of times, techs have visited my house over and over, and it's STILL HAPPENING, EVERY DAY." It's not a user-end issue, and I can't believe that with ALL OF THESE IDENTICAL REPORTS (and you can add mine - identical), that Cox is just plum mystified (and always, EXTREMELY RETICENT TO ISSUE ANY KIND OF CREDIT FOR THEIR BREACH OF CONTRACT). It's too much. That's enough. The Federal Communications Commission is there to protect consumers from this fraud and abuse, and by God, I'll be calling on them to do so. Investigative journalists live to expose greed and corruption, and the lack of antitrust measures governing utilities like Cox is fertilizer for the kind of stink Cox gives you for hundreds of dollars a month. So anyway, does anyone have any suggestions, he asked rhetorically. (incidentally, the sheer VOLUME of tags, crowd-sourced, shows where the stakeholders are:)
Slow internet AGAIN 0.1 upload on gigablast
I have gigablast. Every night my internet slows down to 0.1 upload and 200 download. I call in and they state there aren't outages. I have had a tech out to repair something at the street. I have replaced my router with a new cox issued one. No one can figure this out. Is anyone else having these issues. I have read on the forums that several other people have this issue , but not anywhere near my location. Can anyone help please?
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 MbpsSpiky inconsistent internet
for a few weeks i've been having terrible internet (even worse at night) i tried running a tracert to google.comto see if i could identify the issue and it would seem the first node has mostly been the worse. also rand a ping -t to the first node. nd a ping -t to the first node. Reply from 10.132.120.1: bytes=32 time=27ms TTL=254 Reply from 10.132.120.1: bytes=32 time=10ms TTL=254 Reply from 10.132.120.1: bytes=32 time=24ms TTL=254 Reply from 10.132.120.1: bytes=32 time=61ms TTL=254 Reply from 10.132.120.1: bytes=32 time=40ms TTL=254 Request timed out. Reply from 10.132.120.1: bytes=32 time=32ms TTL=254 Reply from 10.132.120.1: bytes=32 time=18ms TTL=254 Reply from 10.132.120.1: bytes=32 time=95ms TTL=254 Reply from 10.132.120.1: bytes=32 time=120ms TTL=254 Reply from 10.132.120.1: bytes=32 time=249ms TTL=254 Reply from 10.132.120.1: bytes=32 time=102ms TTL=254 Reply from 10.132.120.1: bytes=32 time=143ms TTL=254 Reply from 10.132.120.1: bytes=32 time=112ms TTL=254 Reply from 10.132.120.1: bytes=32 time=29ms TTL=254 Reply from 10.132.120.1: bytes=32 time=231ms TTL=254 Reply from 10.132.120.1: bytes=32 time=23ms TTL=254 Reply from 10.132.120.1: bytes=32 time=50ms TTL=254 Reply from 10.132.120.1: bytes=32 time=74ms TTL=254 Reply from 10.132.120.1: bytes=32 time=27ms TTL=254 Reply from 10.132.120.1: bytes=32 time=243ms TTL=254 Reply from 10.132.120.1: bytes=32 time=31ms TTL=254 Reply from 10.132.120.1: bytes=32 time=12ms TTL=254 Reply from 10.132.120.1: bytes=32 time=22ms TTL=254 Reply from 10.132.120.1: bytes=32 time=61ms TTL=254 Reply from 10.132.120.1: bytes=32 time=223ms TTL=254 Reply from 10.132.120.1: bytes=32 time=65ms TTL=254 Reply from 10.132.120.1: bytes=32 time=48ms TTL=254 Reply from 10.132.120.1: bytes=32 time=50ms TTL=254 Reply from 10.132.120.1: bytes=32 time=9ms TTL=254 Reply from 10.132.120.1: bytes=32 time=148ms TTL=254 Reply from 10.132.120.1: bytes=32 time=149ms TTL=254 Reply from 10.132.120.1: bytes=32 time=46ms TTL=254 Reply from 10.132.120.1: bytes=32 time=20ms TTL=254 Reply from 10.132.120.1: bytes=32 time=23ms TTL=254 Reply from 10.132.120.1: bytes=32 time=17ms TTL=254 Reply from 10.132.120.1: bytes=32 time=73ms TTL=254 Reply from 10.132.120.1: bytes=32 time=120ms TTL=254 Reply from 10.132.120.1: bytes=32 time=67ms TTL=254 Reply from 10.132.120.1: bytes=32 time=36ms TTL=254 Reply from 10.132.120.1: bytes=32 time=28ms TTL=254 Reply from 10.132.120.1: bytes=32 time=26ms TTL=254 Reply from 10.132.120.1: bytes=32 time=134ms TTL=254 Reply from 10.132.120.1: bytes=32 time=26ms TTL=254 Reply from 10.132.120.1: bytes=32 time=11ms TTL=254 Reply from 10.132.120.1: bytes=32 time=74ms TTL=254 Reply from 10.132.120.1: bytes=32 time=168ms TTL=254 Reply from 10.132.120.1: bytes=32 time=45ms TTL=254 Reply from 10.132.120.1: bytes=32 time=153ms TTL=254 Reply from 10.132.120.1: bytes=32 time=22ms TTL=254 Reply from 10.132.120.1: bytes=32 time=111ms TTL=254 Reply from 10.132.120.1: bytes=32 time=95ms TTL=254 Reply from 10.132.120.1: bytes=32 time=46ms TTL=254 Reply from 10.132.120.1: bytes=32 time=36ms TTL=254 Reply from 10.132.120.1: bytes=32 time=38ms TTL=254 Reply from 10.132.120.1: bytes=32 time=48ms TTL=254 Reply from 10.132.120.1: bytes=32 time=14ms TTL=254 Reply from 10.132.120.1: bytes=32 time=261ms TTL=254 Request timed out. Reply from 10.132.120.1: bytes=32 time=322ms TTL=254 Reply from 10.132.120.1: bytes=32 time=164ms TTL=254 Reply from 10.132.120.1: bytes=32 time=127ms TTL=254 Reply from 10.132.120.1: bytes=32 time=106ms TTL=254 Reply from 10.132.120.1: bytes=32 time=34ms TTL=254 Request timed out. Reply from 10.132.120.1: bytes=32 time=33ms TTL=254 Reply from 10.132.120.1: bytes=32 time=27ms TTL=254 Reply from 10.132.120.1: bytes=32 time=75ms TTL=254 Reply from 10.132.120.1: bytes=32 time=94ms TTL=254 Reply from 10.132.120.1: bytes=32 time=60ms TTL=254 Reply from 10.132.120.1: bytes=32 time=86ms TTL=254 any help would be appreciated also i'm wired
2 weeks ago tech came out ,sub contractor, found all sorts of issues; continued in description
Sub contractor tech came out about 2 weeks ago after going thru several level 1 techs that had very varied levels of knowledge. He found several issues and ran a new drop line, new line from the box to the modem and fixed the issue of a vary unstable connection that would just basically give up. Now a tech is scheduled for today for the same issues. Been with COX for quite a while having phone and cable with internet over 18 years so I guess I am patient or stupid. Dropped all my service except internet because of signal issues and cost.I have a i7 9700 K on a Z390 Taichi MB running Win10 64bit 32GB DDR4 with 3 SSDs and 2080 GTX 11GB ti with Netgear COX approved modem and Router CM-1000 and RAX-80. Paying for GigaBlast and getting on average 500 to 650 Mbps so speed is not a huge issues. Any ideas? 2020-01-20, 00:24:07 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-20, 00:13:44 Warning (5) Dynamic Range Window violation 2020-01-20, 00:13:44 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-20, 00:11:52 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 3.;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-20, 00:11:47 Notice (6) TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-20, 00:11:47 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established 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.1;CM-VER=3.1; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; Time Not Established 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.1;CM-VER=3.1; 2020-01-18, 13:16:11 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; Time Not Established 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.1;CM-VER=3.1; 2020-01-08, 04:11:35 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 11:00:18 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:47:23 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.1;CM-VER=3.1; 2020-01-07, 09:47:19 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:59 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:59 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:40 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:40 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:19 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:45:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:45:26 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:45:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:25:49 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.1;CM-VER=3.1; 2020-01-07, 09:23:12 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.1;CM-VER=3.1; 2020-01-07, 09:23:08 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:22:48 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:22:48 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:22:29 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:22:29 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:22:09 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:22:08 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:21:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:21:17 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:00:28 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.1;CM-VER=3.1; 2020-01-07, 09:00:24 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:00:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:00:23 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; Been with COX for quite a while having phone and cable with internet over 18 years so I guess I am patient or stupid. Dropped all my service except internet because of signal issues and cost.I have a i7 9700 K on a Z390 Taichi MB running Win10 64bit 32GB DDR4 with 3 SSDs and 2080 GTX 11GB ti with Netgear COX approved modem and Router CM-1000 and RAX-80 2020-01-20, 12:45:03 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-20, 12:33:06 Notice (6) CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: �; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-20, 12:33:06 Warning (5) Unicast DSID PSN startup error 2020-01-20, 12:32:55 Warning (5) Dynamic Range Window violation 2020-01-20, 12:32:55 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-20, 12:32:49 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 3.;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-20, 12:32:44 Notice (6) TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-20, 12:32:44 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 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=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; Time Not Established 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.1;CM-VER=3.1; 2020-01-20, 12:31:50 Critical (3) Resetting the cable modem due to docsDevResetNow 2020-01-20, 00:24:07 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; Time Not Established 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.1;CM-VER=3.1; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; Time Not Established 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.1;CM-VER=3.1; 2020-01-18, 13:16:11 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; Time Not Established 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.1;CM-VER=3.1; 2020-01-08, 04:11:35 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 11:00:18 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:47:23 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.1;CM-VER=3.1; 2020-01-07, 09:47:19 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:59 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:59 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:40 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:40 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:46:19 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:45:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:45:26 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:45:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:25:49 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.1;CM-VER=3.1; 2020-01-07, 09:23:12 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.1;CM-VER=3.1; 2020-01-07, 09:23:08 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:22:48 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1; 2020-01-07, 09:22:48 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:38:df:08:fe:af;CM-QOS=1.1;CM-VER=3.1;
Modem resets every morning at 5:21
I have an Arris SBG7600AC2 modem that is hard resetting every morning from a signal Cox is sending. I am including the event log. Is there a setting I need to change on my modem? 12/14/2019 5:21 73040100 6 TLV-11 - unrecognized OID;CM-MAC=14:c0:3e:a3:36:c9;CMTS-MAC=2c:86:d2:88:58:eb;CM-QOS=1.1;CM-VER=3.0; 12/14/2019 5:21 84000700 5 RCS Partial Service;CM-MAC=14:c0:3e:a3:36:c9;CMTS-MAC=2c:86:d2:88:58:eb;CM-QOS=1.1;CM-VER=3.0; 12/15/2019 5:22 73040100 6 TLV-11 - unrecognized OID;CM-MAC=14:c0:3e:a3:36:c9;CMTS-MAC=2c:86:d2:88:58:eb;CM-QOS=1.1;CM-VER=3.0; 12/15/2019 5:22 84000700 5 RCS Partial Service;CM-MAC=14:c0:3e:a3:36:c9;CMTS-MAC=2c:86:d2:88:58:eb;CM-QOS=1.1;CM-VER=3.0;
