WiFi keeps being disabled. Logs showing weird stuff. Any one else having this problem?

I'm posting this on behalf of a customer of our MSP.

They got a new business class router/AP this fall.

Since then they've repeatedly seen their WiFi end up "disabled" without any manual intervention. In going thru the logs for the past 90 days I've found some entries that don't seem to make sense in the day or so running up to losing the WiFi.

The system entires look like this:

2019/1/24 04:20:14 Notice [Firewall][4987]: tsip_pm_enabled: 0
2019/1/24 04:19:50 Notice [Firewall][4638]: tsip_pm_enabled: 0
2019/1/24 04:14:10 Notice [PortManagement][757]: tsip_pm_enable: 0
2019/1/24 04:10:19 Notice [PortManagement][755]: tsip_pm_enable: 0
2019/1/24 03:13:19 Notice [Firewall][4920]: tsip_pm_enabled: 0
2019/1/24 03:06:27 Notice [Firewall][2325]: tsip_pm_enabled: 0
2019/1/24 03:04:47 Notice [PortManagement][758]: tsip_pm_enable: 0

The event logs for the same time period:

2019/1/24 04:32:34 Notice [Docsis][571]: DBC Complete - notifying DMG
2019/1/24 04:32:33 Notice [Docsis][571]: DBC act request received, len: 36
2019/1/24 04:19:25 Notice [Dhcpc][4269]: erouter0 got new IP 71.194.21.200
2019/1/24 04:14:59 Critical [Docsis][570]: Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
2019/1/24 04:11:42 Critical [Docsis][567]: No Ranging Response received - T3 time-out
2019/1/24 04:11:33 Critical [Docsis][567]: Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
2019/1/24 04:11:33 Critical [Docsis][567]: Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
2019/1/24 04:11:33 Critical [Docsis][567]: Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
2019/1/24 04:11:33 Critical [Docsis][567]: Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
2019/1/24 04:11:10 Critical [Docsis][567]: No Ranging Response received - T3 time-out
2019/1/24 04:11:03 Critical [Docsis][567]: No Ranging Response received - T3 time-out
2019/1/24 04:11:03 Critical [Docsis][567]: No Ranging Response received - T3 time-out
2019/1/24 03:54:39 Critical [Docsis][566]: No Ranging Response received - T3 time-out
2019/1/24 03:30:24 Critical [Docsis][566]: No Ranging Response received - T3 time-out
2019/1/24 03:10:06 Critical [Docsis][566]: No Ranging Response received - T3 time-out
2019/1/24 03:05:59 Notice [Dhcpc][1822]: erouter0 got new IP 71.194.21.200
2019/1/24 02:47:12 Critical [Docsis][567]: No Ranging Response received - T3 time-out
2019/1/24 02:45:33 Critical [Docsis][567]: No Ranging Response received - T3 time-out
2019/1/24 02:45:14 Critical [Docsis][567]: No Ranging Response received - T3 time-out
2019/1/24 02:41:24 Critical [Docsis][567]: No Ranging Response received - T3 time-out
2019/1/24 02:40:43 Critical [Docsis][567]: No Ranging Response received - T3 time-out
2019/1/23 23:12:18 Notice [Dhcpc][2284]: erouter0 T1 Expired, Enter Renew State

The client is blameing us since we set up the network but we believe this is a comcast issue especaily considering these entries. Please advise on next steps.