7 Messages
Intermittent Internet Drop Outs
I have been having intermittent drop outs of my internet. It seems random and will be fine for a couple days and then may go out 3 or 4 times the next day. It will go out for anywhere between 10-45 minutes. Over the last week it has gone out 10 times with only 3 of the 7 days free of drop outs. I have tried two different modems (Netgear CM1000 and CM3000). It has been going on for at least a couple months now. But I was out of the house and unable to troubleshoot for a while. I knew it was going out though as my smartthings hub would notify me when it lost connection.
I have been reading up and learning what I can about cable modems and how it works, but admit that much of it is over my head. However, based on what I have been reading, I think the issue may be that the Upstream power levels are spiking and causing the modem to freeze up. When it goes out, I am unable to access the modem web interface unless I reset the modem. When it is working properly, the upstream power levels are already high at around 47 - 51 (should be between 38-48). I am usually not home when it goes out and even when I am, I am not looking at the modem status page to see what the power levels are right as it goes out. This morning I was home when it went out and tried to grab the info from the modem status page a bunch of times after I reset the modem and it was trying to reconnect. It would lock onto one upstream channel and then drop it repeatedly. But when it was locked on, the power level was at 59.
The modem is on an xfinity supplied 3-way splitter (3.5 dB). Unfortunately due to the layout and wiring of my house, I need the splitter. However, I have resigned to only using two of the ports. On a day when it was doing well the levels were at 46.8, 46.3, 46.3, 46.0 & 46.3 (downstream mainly between 2.2 - 3, but with a couple at 4.2 & 4.6). I tried removing the splitter to test and it dropped the levels that day to 44.5, 44.8, 44.5, 44.3, 44.5. (It put most of my my downstream levels to around 4.5 - 5.)
I was able to grab one status reading about a month ago where it was bad and it was locked onto 5 upstream channels. Their power levels were 58.5, 58.5, 58.0, 57.3 & 52.5 at the time (downstream between -3 to -1.5). 15 minutes later, the power levels were 51.8, 51.8, 51.0, 50.8 & 51.5 (downstream still between -3 to -1.5). (I can't remember for sure, but I believe the modem was on a 7 dB splitter port at the time.)
The line that feeds the splitter was replaced and rerun through the house a couple months ago. We were having signal loss on our xfinity 4k dvr and some channels would intermittently have issues with going out or being pixelated. The xfinity tech came out and replaced all the fittings and everything he could and said that he was still seeing signal loss for the frequency for those channels. He said the cable in the wall needed to be replaced. We had their recommended contractor (HelloTech) come out and run a new line within the house from the master closet where the cable enters the house and splits out. When the contractor pulled the old line out, he said it was run with a bunch of short lines connected by female-to-female connectors. He ran one continuous line to replace it.
I can't be certain, but I feel like our internet connectivity issues started after we got the line replaced. Is it possible that the connectors could have been damping the power levels down to acceptable levels and after getting a new line the power spikes are too high for the modem? I have also read that power spikes can be caused by a damaged wire outside the home, maybe with frayed wires. Also, in case it can affect things, I am in Florida and it is the hot part of the year. What can I do to try to fix these issues? @Xfinity Support is there anything that can be done?
Here is the error log from my CM1000 modem from this morning when I had an outage. I admit I don't understand it. Hopefully someone here can help me make sense of it. I appreciate any insight you can provide. (I replaced my MAC addresses with question marks.)
docsDevEvFirstTime | docsDevEvLastTime | docsDevEvCounts | docsDevEvLevel | docsDevEvId | docsDevEvText |
8/18/24 9:41:53 AM | 8/18/24 9:41:53 AM | 1 | Notice (6) | 67061600 | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Notice (6) | -1858273230 | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Time Not Established | 9 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 82000400 | 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.1; |
Time Not Established | Time Not Established | 16 | Critical (3) | 82000500 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 8 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 82000400 | 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.1; |
Time Not Established | Time Not Established | 4 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 82000400 | 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.1; |
Time Not Established | Time Not Established | 16 | Critical (3) | 82000500 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 16 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 82000400 | 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.1; |
Time Not Established | Time Not Established | 4 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 82000400 | 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.1; |
Time Not Established | Time Not Established | 4 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 82000400 | 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.1; |
Time Not Established | Time Not Established | 3 | Critical (3) | 82000500 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 4 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 84000100 | 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 | Time Not Established | 8 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 82000400 | 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.1; |
Time Not Established | Time Not Established | 16 | Critical (3) | 82000500 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 8 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 82000400 | 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.1; |
Time Not Established | Time Not Established | 16 | Critical (3) | 82000500 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 8 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 82000400 | 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.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 82000500 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 4 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 1 | Critical (3) | 84000100 | 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; |
8/18/24 9:13:07 AM | 8/18/24 9:13:07 AM | 1 | Critical (3) | 82000400 | 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.1; |
8/18/24 9:11:30 AM | 8/18/24 9:13:04 AM | 12 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:10:54 AM | 8/18/24 9:11:03 AM | 3 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:10:15 AM | 8/18/24 9:10:23 AM | 4 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:09:45 AM | 8/18/24 9:09:45 AM | 1 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:09:18 AM | 8/18/24 9:09:41 AM | 5 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:09:07 AM | 8/18/24 9:09:07 AM | 1 | Critical (3) | 82000500 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:08:56 AM | 8/18/24 9:09:05 AM | 5 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:08:54 AM | 8/18/24 9:08:54 AM | 1 | Critical (3) | 82000800 | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:08:54 AM | 8/18/24 9:08:54 AM | 1 | Critical (3) | 82000600 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:08:41 AM | 8/18/24 9:08:54 AM | 3 | Critical (3) | 82000500 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:08:40 AM | 8/18/24 9:08:40 AM | 1 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:08:38 AM | 8/18/24 9:08:39 AM | 2 | Critical (3) | 82000500 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:08:33 AM | 8/18/24 9:08:37 AM | 4 | Critical (3) | 82000500 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:08:32 AM | 8/18/24 9:08:32 AM | 1 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:08:32 AM | 8/18/24 9:08:32 AM | 1 | Critical (3) | 82000500 | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
8/18/24 9:08:32 AM | 8/18/24 9:08:32 AM | 1 | Critical (3) | 82000200 | No Ranging Response received - T3 time-out;CM-MAC=??:??:??:??:??:??;CMTS-MAC=??:??:??:??:??:??;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Time Not Established | 57 | Critical (3) | 84000100 | 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 | Time Not Established | 1 | Critical (3) | 84000100 | 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; |
Accepted Solution
dustinf
7 Messages
1 month ago
Just wanted to follow up for future readers who may have this problem. After the tech came out and tested everything, there wasn't anything he could do in the house. Everything was reading fine as there was no outage while he was there. I let him know the readings I was getting. He put in a maintenance request for someone to look at the line in the neighborhood. Later that day I got a text saying the maintenance work had been completed. I don't know what they did, but I haven't had a single outage in the month since. So, the problem was something outside of my house.
1
0
EG
Expert
•
106.9K Messages
3 months ago
You are going to need to get the Comcast techs reinvolved until things get fixed properly. Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it up to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.
Good luck !
0
0
XfinityAngie
Official Employee
•
1.4K Messages
3 months ago
Please send us a direct chat message with your full name and complete service address to “Xfinity Support”. To do so, click on the chat icon located at the top right of this forum's page.
Here's the detailed steps to direct message us:
• Click "Sign In" if necessary
• Click the "Direct Message” icon (upper right corner of this page)
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list
• Type your message in the text area near the bottom of the window
• Press Enter to send your message
1
0
EG
Expert
•
106.9K Messages
3 months ago
@XfinityAngie
The problem has already been established..... It's all in black and white.
(edited)
0
0
dustinf
7 Messages
3 months ago
I started a direct message with xfinity support as you suggested.
I removed the splitter this evening to test (meaning no cable viewing on my main living room TV). I'll see if the internet still goes out over the next few days with no splitter. However, long term, I can't do without cable on my main viewing TV. That is also where the ethernet runs originate for my other rooms. So, my router and ethernet switch are located there. Hence why I was splitting the cable between modem and cable box.
The power levels right now without the splitter put my downstream levels at their upper limit (5.9 to 7dBmV) and my upstream all around 46dBmV.
1
0