Visitor
•
2 Messages
my downstream power is -10 to -16 dBmV and status is showing red/poor.
Cable Diagnostic
Status: Poor
Action:
[Downstream Power Level]
Try these actions (Click the Refresh button after each step):
1) Make sure the coaxial cable is tightly connected.
2) Remove any unnecessary splitters.
3) Replace any required splitters.
4) Contact your service provider for troubleshooting help.
CM Status: Good
Downstream Status: Bad
Downstream Power Level: Bad
Downstream power is poor (-15.7dBmV). The recommended level is between -10dBmV to 10dBmV.
Downstream SNR Level: Good
Upstream Status: Good
Upstream Power Level: Good
Current Time: Tue Jul 21 09:00:58 2026
Startup Procedure
Acquire Downstream Channel: 423000000 Hz Locked
Connectivity State: OK Operational
Boot State: OK Operational
Security: Enabled BPI+
IP Provisioning Mode: Honor MDD IPv6 only
Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 4 423000000 Hz -15.2 38.6 0 0
2 Locked QAM256 1 405000000 Hz -15 38.7 0 0
3 Locked QAM256 2 411000000 Hz -15.3 38.4 0 0
4 Locked QAM256 3 417000000 Hz -15.2 38.4 0 0
5 Locked QAM256 5 429000000 Hz -15.2 38.6 0 0
6 Locked QAM256 6 435000000 Hz -15.3 38.5 0 0
7 Locked QAM256 7 441000000 Hz -15.5 38.4 0 0
8 Locked QAM256 8 447000000 Hz -15.5 37.6 0 0
9 Locked QAM256 9 453000000 Hz -15.7 37.4 0 0
10 Locked QAM256 10 459000000 Hz -15.1 38.2 0 0
11 Locked QAM256 11 465000000 Hz -14.9 38.3 0 0
12 Locked QAM256 12 471000000 Hz -15.2 38 0 0
13 Locked QAM256 13 477000000 Hz -15.3 37.3 0 0
14 Locked QAM256 14 483000000 Hz -15.3 36.9 0 0
15 Locked QAM256 15 489000000 Hz -15.3 37.1 0 0
16 Locked QAM256 16 495000000 Hz -15.5 37.1 0 0
17 Locked QAM256 17 501000000 Hz -15.4 32.6 0 0
18 Locked QAM256 18 507000000 Hz -14.7 38.2 0 0
19 Locked QAM256 19 513000000 Hz -14.4 38.4 0 0
20 Locked QAM256 20 519000000 Hz -14.9 38.4 0 0
21 Locked QAM256 21 525000000 Hz -14.8 38.1 0 0
22 Locked QAM256 22 531000000 Hz -14.6 38.1 0 0
23 Locked QAM256 23 537000000 Hz -14.1 38.8 0 0
24 Locked QAM256 24 543000000 Hz -13.7 39.1 0 0
25 Locked QAM256 25 549000000 Hz -14.1 39 0 0
26 Locked QAM256 26 561000000 Hz -13.9 39.3 0 0
27 Locked QAM256 27 567000000 Hz -13 40 0 0
28 Locked QAM256 28 573000000 Hz -11.7 41 0 0
29 Locked QAM256 29 579000000 Hz -11.2 41.3 0 0
30 Locked QAM256 30 585000000 Hz -10.9 41.5 0 0
31 Locked QAM256 31 591000000 Hz -10.7 41.5 0 0
32 Locked QAM256 32 597000000 Hz -10.3 41.9 0 0
Upstream Bonded Channels
Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 3 5120 Ksym/sec 29200000 Hz 54.8 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 22800000 Hz 50.5 dBmV
3 Locked ATDMA 1 5120 Ksym/sec 16400000 Hz 49.3 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 35600000 Hz 52.5 dBmV
5 Not Locked Unknown 0 0 0 0.0
6 Not Locked Unknown 0 0 0 0.0
7 Not Locked Unknown 0 0 0 0.0
8 Not Locked Unknown 0 0 0 0.0
Downstream OFDM Channels
Channel LockedStatus ProfileID ChannelID Frequency Power SNR/MER ActiveSubcarrier Unerror Correctable Uncorrectable
1 Locked 0 ,1 ,2 ,3 193 690000000 Hz -11.02 dBmV 38.3 dB 688 ~ 3407 20483576 19693707 1912
2 Locked 0 ,1 ,2 ,3 194 957000000 Hz -17.72 dBmV 32.9 dB 148 ~ 3947 21344988 10236041 10560728
Upstream OFDMA Channels
Channel LockedStatus ProfileID ChannelID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV
Event Log
Time Priority Description
Tue Jul 21 08:43:31 2026 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 08:42:08 2026 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 08:41:54 2026 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 08:41:48 2026 Notice (6) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 08:41:47 2026 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 08:41:40 2026 Notice (6) TLV-11 - unrecognized OID;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 08:41:31 2026 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Tue Jul 21 08:41:29 2026 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 08:41:23 2026 Warning (5) ToD request sent - No Response received;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 07:51:16 2026 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 07:51:10 2026 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 07:51:09 2026 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 07:51:08 2026 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 07:51:08 2026 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 07:50:44 2026 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];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=[Edited: “Personal Information”];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 10 12:08:53 2026 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Fri Jul 10 09:45:45 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Thu Jul 09 07:01:02 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Thu Jul 09 06:02:31 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Wed Jul 08 16:33:33 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Wed Jul 08 11:31:17 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Wed Jul 08 03:41:18 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Tue Jul 07 14:24:28 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 06 11:30:38 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 06 07:55:33 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 06 03:59:22 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 06 01:54:44 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 05 12:51:57 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 05 11:55:48 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Sat Jul 04 13:47:01 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Sat Jul 04 07:54:20 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Sat Jul 04 06:07:01 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Sat Jul 04 01:11:59 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Fri Jul 03 06:45:02 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Thu Jul 02 08:34:43 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Thu Jul 02 03:30:55 2026 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Thu Jul 02 03:03:43 2026 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;


XfinityBenjaminM
Official Employee
•
3.2K Messages
17 hours ago
2
0
EG
Expert
•
119.5K Messages
10 hours ago
@user_a9mi7z
Yes. The downstream power is too low / out of spec, and it may be intermittently fluctuating even lower. The upstream power is too high as well. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/reconfigured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also, check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, or animal chews.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
Good luck with it !
(edited)
0
0