3 Messages
Constant internet disconnects
I have been struggling with intermittent drops in my internet service for about three weeks now. We are on our second modem and about to have our 4th tech visit. I suspect that there is an issue somewhere up stream of me that is causing the issue, but I need to know the magic words to get a tech to actually go check that and not the cables in my house for the 4th time. Here are the log entries that I am seeing on my modem with the MACs redacted.
If I have to interact with the Xfinity assistant one more time I might loose my mind
03/19/2025 18:39:27 |
Notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:39:08 |
Critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:39:05 |
Warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:39:05 |
Warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:39:05 |
Critical | No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:39:03 |
Notice | CM-STATUS message sent. Event Type Code: 17; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:39:03 |
Critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:38:59 |
Critical | No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:38:58 |
Notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:38:57 |
Critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:38:57 |
Error | TCS Fail on all Upstream Channels;CM-MAC=;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:38:57 |
Critical | No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:38:51 |
Notice | CM-STATUS message sent. Event Type Code: 2; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:38:50 |
Critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:38:50 |
Critical | No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:38:50 |
Error | TCS Fail on all Upstream Channels;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
03/19/2025 18:38:44 |
Notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
And the current power levels at time of posting
Channel ID | Lock Status | Modulation | Frequency | Power | SNR/MER | Corrected | Uncorrectables |
4 | Locked | 256QAM | 435000000 Hz | -0.9 dBmV | 43.4 dB | 3091 | 3132 |
12 | Locked | 256QAM | 483000000 Hz | -0.3 dBmV | 43.4 dB | 3019 | 3089 |
20 | Locked | 256QAM | 531000000 Hz | -0.4 dBmV | 44.6 dB | 9151 | 11331 |
28 | Locked | 256QAM | 579000000 Hz | -0.6 dBmV | 43.4 dB | 9269 | 11751 |
1 | Locked | 256QAM | 417000000 Hz | -0.9 dBmV | 43.4 dB | 18328 | 21249 |
2 | Locked | 256QAM | 423000000 Hz | -0.8 dBmV | 43.4 dB | 18465 | 25749 |
3 | Locked | 256QAM | 429000000 Hz | -1.0 dBmV | 43.4 dB | 18937 | 27898 |
5 | Locked | 256QAM | 441000000 Hz | -0.9 dBmV | 43.4 dB | 16726 | 23852 |
6 | Locked | 256QAM | 447000000 Hz | -0.8 dBmV | 43.4 dB | 14646 | 16932 |
7 | Locked | 256QAM | 453000000 Hz | -0.4 dBmV | 43.4 dB | 14548 | 16424 |
8 | Locked | 256QAM | 459000000 Hz | -0.5 dBmV | 43.4 dB | 14982 | 20440 |
9 | Locked | 256QAM | 465000000 Hz | -0.4 dBmV | 43.4 dB | 14799 | 15771 |
10 | Locked | 256QAM | 471000000 Hz | -0.3 dBmV | 44.6 dB | 13741 | 14086 |
11 | Locked | 256QAM | 477000000 Hz | -0.5 dBmV | 43.4 dB | 14973 | 18024 |
13 | Locked | 256QAM | 489000000 Hz | -0.5 dBmV | 43.4 dB | 12972 | 19743 |
14 | Locked | 256QAM | 495000000 Hz | -0.3 dBmV | 44.6 dB | 11906 | 13599 |
15 | Locked | 256QAM | 501000000 Hz | -0.4 dBmV | 43.4 dB | 12055 | 14547 |
16 | Locked | 256QAM | 507000000 Hz | -0.4 dBmV | 43.4 dB | 11507 | 13104 |
17 | Locked | 256QAM | 513000000 Hz | -0.4 dBmV | 43.4 dB | 10966 | 14787 |
18 | Locked | 256QAM | 519000000 Hz | -0.3 dBmV | 43.4 dB | 10332 | 13794 |
19 | Locked | 256QAM | 525000000 Hz | -0.3 dBmV | 43.4 dB | 10116 | 10608 |
21 | Locked | 256QAM | 537000000 Hz | -0.4 dBmV | 43.4 dB | 9043 | 11369 |
22 | Locked | 256QAM | 543000000 Hz | -0.5 dBmV | 43.4 dB | 9062 | 11808 |
23 | Locked | 256QAM | 549000000 Hz | -0.5 dBmV | 43.4 dB | 9626 | 13675 |
24 | Locked | 256QAM | 555000000 Hz | -0.5 dBmV | 43.4 dB | 9565 | 11874 |
25 | Locked | 256QAM | 561000000 Hz | -0.4 dBmV | 43.4 dB | 8558 | 11391 |
26 | Locked | 256QAM | 567000000 Hz | -0.4 dBmV | 43.4 dB | 9021 | 11952 |
27 | Locked | 256QAM | 573000000 Hz | -0.5 dBmV | 43.4 dB | 9789 | 12925 |
29 | Locked | 256QAM | 585000000 Hz | -0.4 dBmV | 43.4 dB | 8384 | 12799 |
30 | Locked | 256QAM | 591000000 Hz | -0.4 dBmV | 44.6 dB | 9191 | 13119 |
31 | Locked | 256QAM | 597000000 Hz | -0.3 dBmV | 43.4 dB | 8247 | 9815 |
32 | Locked | 256QAM | 603000000 Hz | 0.1 dBmV | 43.4 dB | 8535 | 11777 |
193 | Locked | OFDM PLC | 957000000 Hz | -2.6 dBmV | 44.0 dB | 10882976 | 10558 |
Upstream Bonded Channels | ||||||
---|---|---|---|---|---|---|
Channel ID | Lock Status | US Channel Type | Frequency | Width | Power | |
2 | Locked | SC-QAM | 22800000 Hz | 6400000 | 41.0 dBmV | |
4 | Locked | SC-QAM | 35600000 Hz | 6400000 | 41.3 dBmV | |
3 | Locked | SC-QAM | 29200000 Hz | 6400000 | 41.3 dBmV | |
1 | Locked | SC-QAM | 16400000 Hz | 6400000 | 40.8 dBmV |
EG
Expert
•
109.5K Messages
15 days ago
The signal status values at that snapshot in time were OK but the error log entries indicate that something is going on. Perhaps there is noise ingress into the line(s) / an upstream channel / return path impairment somewhere.
And there are a fair number of uncorrectable bit errors, but that may not be significant depending on the total uptime of the modem since the last reboot.
There are other signal stat values that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees (The Digital Care Team) who are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check for any real-time degradation and / or error reports, see your node / cable plant, and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
Also, 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. Typically, after three visits, and the issue is not corrected, they should have written up an escalation ticket already....
Good luck !
(edited)
0
0
XfinityWilliam
Official Employee
•
1.1K Messages
15 days ago
I'm really sorry to hear about the ongoing issues with your internet service. It sounds incredibly frustrating to have intermittent drops for such a long time, especially after multiple modem replacements and technician visits. Let's see if we can get this resolved for you.
First, I want to assure you that your concerns are valid and important. You've been patient through multiple attempts to fix the issue, and it's time to explore other potential causes.
I'm really sorry to hear about the ongoing issues with your internet service. It sounds incredibly frustrating to have intermittent drops for such a long time, especially after multiple modem replacements and technician visits. Let's see if we can get this resolved for you.
First, I want to assure you that your concerns are valid and important. You've been patient through multiple attempts to fix the issue, and it's time to explore other potential causes.
4
0