Intermittent daily Connectivity issues SB8200

RESOLVED.

I bought a refurbed Netgear CM1100 and it works.

TAKEAWAYS:

Arris customer support did not reply within three days and counting.
Xfinity will send techs out to your house repeatedly before they will open a support ticket and evaluate an event log.

I don't know how Arris SB8200 gained a place on Xfinity's 'approved' (but not 'supported') list of cable modems but I would strongly recommend avoiding that product.  A needless nightmare in getting this issue resolved.

Thanks!..Yeah what gets me is that it has specific times every day that it happens for me ...and gets better then worse again , but never goes away .

New errors in todays log that have not seen or noticed before.. Outage this time inclueded a Solid 15 min at about 5pm.. but taht didn't show here onr on Outage map... Comcast Please Help!

07/08/2020 16:25 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;C....
07/08/2020 16:24 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;C....
07/08/2020 16:23 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C....
07/08/2020 16:16 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;C....
07/08/2020 16:16 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;C....
07/08/2020 16:15 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;C....
07/08/2020 16:15 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2.;C....
07/08/2020 16:14 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;C....
07/08/2020 16:14 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C....
07/08/2020 16:14 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;C....
07/08/2020 16:10 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C....
07/08/2020 16:10 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;C....
07/08/2020 16:09 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;C....
07/08/2020 16:08 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;C....
07/08/2020 16:08 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C....
07/08/2020 16:07 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;C....
07/08/2020 16:06 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C....
07/08/2020 16:04 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;C....
07/08/2020 16:02 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C....
07/08/2020 16:02 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;C....
07/08/2020 16:02 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C....
07/08/2020 15:08 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;C....
07/08/2020 15:07 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;C....
07/08/2020 15:07 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C....
07/08/2020 10:37 2436694061 5 "Dynamic Range Window violation"
07/08/2020 10:37 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;C....
07/08/2020 10:37 2436694061 5 "Dynamic Range Window violation"
07/08/2020 10:37 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;C....
07/08/2020 10:35 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C....
07/08/2020 09:51 2436694061 5 "Dynamic Range Window violation"
07/08/2020 09:51 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;C....
07/08/2020 09:49 2436694061 5 "Dynamic Range Window violation"
07/08/2020 09:49 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;C....
07/08/2020 09:49 2436694061 5 "Dynamic Range Window violation"
07/08/2020 09:49 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;C....
07/08/2020 09:49 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C....
07/08/2020 09:49 2436694061 5 "Dynamic Range Window violation"
07/08/2020 09:49 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;C....
07/08/2020 09:47 2436694061 5 "Dynamic Range Window violation"
07/08/2020 09:47 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;C....
07/08/2020 09:45 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;C....
07/08/2020 09:32 2436694061 5 "Dynamic Range Window violation"
07/08/2020 09:32 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;C....
07/08/2020 09:32 2436694061 5 "Dynamic Range Window violation"
07/08/2020 09:32 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;C....
07/08/2020 09:32 2436694061 5 "Dynamic Range Window violation"
07/08/2020 09:32 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;C....
07/08/2020 09:32 2436694061 5 "Dynamic Range Window violation"
07/08/2020 09:32 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;C....
07/08/2020 09:31 2436694061 5 "Dynamic Range Window violation"

Does comcast review these forums at all ...Can anyone help? I Attached a ping log I ran for 24hours ... (deleted some rows to reduce size to fit here .. Pinging comcast.net 

Don't know if Comcast checks / cares. I've been having the same issue for 2 months now. Working from home at this point is becoming impossible. I have an approved Modem (SB8200), an Orbi RBR40 mesh system, and am really only using two computers in the home at any give time.

I've troubleshooted every way to Sunday (former Network Engineer by trade) and not a single thing has fixed it. I get 2 seconds of packet loss / connectivity drops every 2 minutes or so when using the system. This happens over and over until eventually the modem reboots itself after receiving the reboot signal from an upstream device I assume. Then, problems go away for a little while. But sure enough, they come back the same day.

Today though, I was able to shut off internet to a few of my WiFi devices that weren't actively being used for anything and that seemed to help. Which made me start thinking that maybe the Comcast device that's upstream from my Modem is limiting the amount of MAC addresses in it's table? Maybe they're doing some form of QoS to limit how many devices a single home can have technically online at the same time? Either way, the problem is incredibly annoying and sounds a lot like the problem you're having.

Of course, Comcast has been ZERO help in actually solving the issue. They seem to actively discourage people from getting support on their Internet connection outside of "Did you restart the modem??". 

Thankfully, I have 2 other 1gbps ISP's in my neighborhood, one of whom will be installing new service today. So hopefully I don't have to deal with Comcast anymore.

If you make any progress on this issue, please let me know. I'll do the same.

The same thing is happening to me!! At the same times it is happnening to you... from around 9 am to noon and then again after 1 pm til 5 ish, often around 830 at night too. Working from home is nearly impossible when the wifi keeps going out!!! (I even use an ethernet cable to my modem and no luck -- still goes out)

happens with me too at 9am. also with the sb8200. Why am I paying so much for gigabit...

Thank  you all for your replys .. makes me think I'm not crazy.  There must be a reason Its only at certain times!!

It has occurred even when I directly connect my PC  to the router , and bypass any Wifi or direct wire connections from my house so it's not any load I produce..  Going to call comcast today  see if I can get a service guy to come over durring one of these times , (take a vacation day on that day from my job I guess) .  

Of course just as I hip post on the above this happened 😡

7/24/2020 10:20:30 AM - Reply from 23.74.253.169: bytes=32 time=173ms TTL=53
7/24/2020 10:20:31 AM - Reply from 23.74.253.169: bytes=32 time=170ms TTL=53
7/24/2020 10:20:32 AM - Reply from 23.74.253.169: bytes=32 time=170ms TTL=53
7/24/2020 10:20:37 AM - Request timed out.
7/24/2020 10:20:42 AM - Request timed out.
7/24/2020 10:20:47 AM - Request timed out.
7/24/2020 10:20:52 AM - Request timed out.
7/24/2020 10:20:53 AM - Reply from 23.74.253.169: bytes=32 time=192ms TTL=53
7/24/2020 10:20:58 AM - Request timed out.
7/24/2020 10:21:03 AM - Request timed out.
7/24/2020 10:21:08 AM - Request timed out.
7/24/2020 10:21:13 AM - Request timed out.
7/24/2020 10:21:14 AM - Reply from 23.74.253.169: bytes=32 time=184ms TTL=53
7/24/2020 10:21:15 AM - Reply from 23.74.253.169: bytes=32 time=179ms TTL=53
7/24/2020 10:21:16 AM - Reply from 23.74.253.169: bytes=32 time=202ms TTL=53
7/24/2020 10:21:21 AM - Request timed out.
7/24/2020 10:21:26 AM - Request timed out.
7/24/2020 10:21:27 AM - Reply from 23.74.253.169: bytes=32 time=174ms TTL=53
7/24/2020 10:21:28 AM - Reply from 23.74.253.169: bytes=32 time=169ms TTL=53
7/24/2020 10:21:29 AM - Reply from 23.74.253.169: bytes=32 time=171ms

I will add that I discovered a Link Aggregation feature under the advanced tab of the SB8200 UI.  I clicked it on and will hope that that helps solve the problem.

Edit:  it did not solve the problem.  It simply allows two cables to bond as one into a switch that also has LAP enabled.

Comcast is zero help == true.

I have the same issue:  SB8200 dropping connection.

Tech came out said everything is good coming into my house and all connections are good inside.

Still dropping connects.

Contacted support pleading from them to look at the SB8200 event log.

Answer was no, but here's $60 and we'll schedule a tech to come out to your home.

Unbelievably stupid support management.

So anyway,,, here's my event log 

Date Time Event ID Event Level Description
07/24/2020 11:48 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
07/24/2020 07:20 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:01 68001101 3 "TFTP Request Retries exceeded, CM unable to register "
01/01/1970 00:01 68000500 3 "TFTP failed - Request sent - No Response;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
07/23/2020 01:37 2436694044 3 "Resetting the cable modem due to docsDevResetNow"
07/22/2020 23:18 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:51 2436694044 3 "Resetting the cable modem due to docsDevResetNow"
01/01/1970 00:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:12 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:12 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:12 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:12 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:11 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:11 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:11 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:11 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:11 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:10 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:05 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:02 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:02 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:01 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:01 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:01 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:01 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"
07/22/2020 09:01 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:0d:ea:3d;CMTS-MAC=00:27:90:fe:ad:5e;CM-QOS=1.1;CM-VER=3.1;"

Similar problems too. Frequent outages several times a day. Motorola SB8600.

After a reboot I have zero uncorrected packets (except for channel 32 suspiciously). When a disconnect happens uncorrected packets spike on all channels. It comes back 1 to 10 minutes later.

Here's a snippet of my log:

11:10:01
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;
11:10:04
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;C
11:10:07
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;
11:10:09
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;
11:10:11
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;
11:10:16
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;
11:10:17
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;
11:10:23
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.
11:10:24
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;
11:10:35
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;
11:11:04
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;
11:11:32
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;
11:11:33
Sat Jul 25 2020 Notice (6) CM-STATUS message sent. Event Type Code: 21; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;
11:11:34
Sat Jul 25 2020 Warning (5) MDD message timeout;CM-MAC=00:40:36:61:5f:f8;CMTS-MAC=00:01:5c:cd:ca:5e;CM-QOS=1.1;CM-VER=3.1;

So after vist where lines were checked made sure tight etc .. Technition noticed an attenuator dongle attached on cable entering modem (something previous Tech must have put on many years ago)  He seemed confident that was the cause however No bueno... Next day issue resumed like clockwork.

I went to comcast store and they suggested updating firm ware , but ARRIS site has none stating that the ISP pushes the firmware (Im on HW version 6 , but not sure if that correlates to Firmware)

I thought about doing the LAG as well , so thank you  @kanick  for ruling that out too..

Update ...literally nothing from Comcast on this ... At wits end  might just  purcase another brand Modem as suggested in earlier post and see if that works..