U

Wednesday, July 26th, 2023 8:08 PM

Closed

Losing internet 3-4 times per day.

Hello,

I am have been having a problem with my internet for the past month or so.  It drops out for a couple of minutes several times a day.  I had an xfinity tech come out and he tightened the connections and swapped out a splitter but it has not helped.  I have rebooted the modem several times both before and after the tech’s visit but it did not help.  I have included the information from my modem. I have a Nighthawk cm2050v.

Time Priority Description
Wed Jul 26 11:20:08 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 11:16:52 2023 (Notice (6)) 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=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 11:14:10 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 11:14:08 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 11:14:07 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 11:12:11 2023 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 11:04:09 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 11:03:43 2023 (Notice (6)) 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=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 11:03:40 2023 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 08:05:41 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 08:00:24 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 07:43:08 2023 (Notice (6))

CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Wed Jul 26 07:37:53 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 07:36:53 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 07:36:40 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 07:34:01 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 07:27:21 2023 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 07:00:15 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 06:58:56 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 06:22:20 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 06:17:01 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 06:13:40 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 06:10:14 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 05:43:40 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 05:38:52 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 05:35:19 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 05:31:32 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 05:15:20 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 05:14:50 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 05:02:09 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 04:56:07 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 04:46:41 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 04:41:25 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 04:16:16 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 04:14:27 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 04:02:13 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 03:56:48 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 03:40:35 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 03:39:06 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 26 03:28:21 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Expert

 • 

110.8K Messages

2 years ago

Please also copy all of the text in its entirety of the *Downstream Power Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.



3 Messages

2 years ago

Sorry!  Thought I had included them in the first post.  Here they are:

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 711000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 44 711000000 Hz -7.5 dBmV 39.9 dB 639 543
2 Locked QAM256 13 525000000 Hz -6.2 dBmV 41.4 dB 686 1302
3 Locked QAM256 14 531000000 Hz -6.9 dBmV 40.8 dB 607 1218
4 Locked QAM256 15 537000000 Hz -7.5 dBmV 40.6 dB 598 1090
5 Locked QAM256 16 543000000 Hz -7.3 dBmV 40.6 dB 450 684
6 Locked QAM256 17 549000000 Hz -7.2 dBmV 40.7 dB 358 301
7 Locked QAM256 18 555000000 Hz -6.0 dBmV 41.3 dB 369 236
8 Locked QAM256 19 561000000 Hz -6.5 dBmV 40.9 dB 528 329
9 Locked QAM256 20 567000000 Hz -6.6 dBmV 40.7 dB 558 497
10 Locked QAM256 21 573000000 Hz -7.7 dBmV 40.1 dB 754 637
11 Locked QAM256 22 579000000 Hz -7.7 dBmV 40.1 dB 893 947
12 Locked QAM256 23 585000000 Hz -8.1 dBmV 39.8 dB 946 1412
13 Locked QAM256 24 591000000 Hz -7.7 dBmV 40.2 dB 760 1716
14 Locked QAM256 25 597000000 Hz -7.1 dBmV 40.2 dB 588 1265
15 Locked QAM256 26 603000000 Hz -6.2 dBmV 40.8 dB 496 744
16 Locked QAM256 27 609000000 Hz -6.0 dBmV 40.9 dB 496 522
17 Locked QAM256 28 615000000 Hz -6.1 dBmV 41.1 dB 575 620
18 Locked QAM256 29 621000000 Hz -6.7 dBmV 40.8 dB 679 1094
19 Locked QAM256 30 627000000 Hz -7.8 dBmV 40.2 dB 890 1957
20 Locked QAM256 31 633000000 Hz -7.6 dBmV 40.2 dB 971 2482
21 Locked QAM256 32 639000000 Hz -8.0 dBmV 39.9 dB 870 2601
22 Locked QAM256 33 645000000 Hz -8.0 dBmV 39.7 dB 597 2027
23 Locked QAM256 34 651000000 Hz -9.4 dBmV 39.0 dB 381 1199
24 Locked QAM256 35 657000000 Hz -8.8 dBmV 39.4 dB 184 433
25 Locked QAM256 36 663000000 Hz -9.1 dBmV 39.3 dB 80 116
26 Locked QAM256 37 669000000 Hz -7.6 dBmV 40.1 dB 91 59
27 Locked QAM256 38 675000000 Hz -7.1 dBmV 39.7 dB 121 49
28 Locked QAM256 39 681000000 Hz -6.0 dBmV 40.9 dB 174 1
29 Locked QAM256 40 687000000 Hz -7.2 dBmV 40.2 dB 93 26
30 Locked QAM256 41 693000000 Hz -7.5 dBmV 40.1 dB 167 32
31 Locked QAM256 42 699000000 Hz -7.7 dBmV 39.9 dB 148 106
32 Locked QAM256 43 705000000 Hz -7.7 dBmV 40.0 dB 517 604
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 16400000 Hz 48.8 dBmV
2 Locked ATDMA 2 5120 22800000 Hz 48.8 dBmV
3 Locked ATDMA 3 5120 29200000 Hz 49.0 dBmV
4 Locked ATDMA 4 5120 35600000 Hz 49.8 dBmV
5 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
 
Downstream OFDM Channels
Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier
Number Range
Unerrored
Codewords
Correctable
Codewords
Uncorrectable
Codewords
1 Locked 0 ,1 ,2 ,3 193 957000000 Hz -10.8 dBmV 37.4 dB 148 ~ 3947 440543586 330405483 3339
2 Not Locked 0 0 0 Hz 0 dBmV 0.0 dB 0 ~ 4095 0 0 0
 
Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV

Official Employee

 • 

1.5K Messages

@EG, Thank you for your help resolving this issue! Are you still experiencing the connection drops @user_7998f9 ?

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Expert

 • 

110.8K Messages

2 years ago

The downstream and the upstream power levels are borderline to out of spec, and they may be intermittently fluctuating even farther out of spec. 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 there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1000 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, etc.

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 you'll need to get the techs re-involved until things get fixed properly.

Good luck with it !

3 Messages

2 years ago

Thanks so much for your tips and advice - I really appreciate it. 

I checked and we only have a single splitter coming in from the street and there aren’t any other splitters. All the cables are in good shape and there aren’t any kinks or sharp bends.  I checked all the fittings, took them apart and cleaned the center wire and retightened them all.  However, we have still been having outages today.  Here are today’s stats:

Time Priority Description
Fri Jul 28 13:22:38 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 13:16:07 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 12:01:07 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:56:50 2023 (Notice (6)) 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=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:56:45 2023 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:04:13 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:03:49 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:03:44 2023 (Critical (3)) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:03:44 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:03:41 2023 (Critical (3)) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:03:41 2023 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:03:39 2023 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:03:31 2023 (Notice (6)) Honoring MDD; IP provisioning mode = IPv6
Fri Jul 28 11:03:15 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:03:04 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:02:54 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:01:56 2023 (Error (4)) DBC-ACK not received;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:01:56 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:01:54 2023 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:01:53 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:01:53 2023 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:00:57 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:00:27 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:00:18 2023 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:00:17 2023 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 11:00:11 2023 (Notice (6)) Honoring MDD; IP provisioning mode = IPv6
Fri Jul 28 11:00:03 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 10:59:53 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 10:58:56 2023 (Error (4)) DBC-ACK not received;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 10:58:56 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 10:58:53 2023 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 10:22:01 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 10:19:11 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 08:53:56 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 08:53:29 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 08:53:21 2023 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 08:53:20 2023 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 08:53:10 2023 (Notice (6)) Honoring MDD; IP provisioning mode = IPv6
Fri Jul 28 08:52:48 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 28 08:52:28 2023 (Critical (3)) UCD invalid or channel unusable;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 471000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 4 471000000 Hz -5.1 dBmV 42.5 dB 6853 10010
2 Locked QAM256 1 453000000 Hz -6.6 dBmV 41.8 dB 6030 7281
3 Locked QAM256 2 459000000 Hz -5.8 dBmV 42.2 dB 5879 7101
4 Locked QAM256 3 465000000 Hz -4.8 dBmV 42.6 dB 8964 14603
5 Locked QAM256 5 477000000 Hz -4.7 dBmV 42.6 dB 3524 5626
6 Locked QAM256 6 483000000 Hz -5.1 dBmV 42.5 dB 5240 8530
7 Locked QAM256 7 489000000 Hz -5.5 dBmV 42.3 dB 4912 4282
8 Locked QAM256 8 495000000 Hz -6.3 dBmV 41.7 dB 6461 8661
9 Locked QAM256 9 501000000 Hz -7.4 dBmV 41.2 dB 6738 8928
10 Locked QAM256 10 507000000 Hz -8.4 dBmV 40.8 dB 5845 6589
11 Locked QAM256 11 513000000 Hz -7.9 dBmV 41.1 dB 6895 7578
12 Locked QAM256 12 519000000 Hz -6.7 dBmV 41.7 dB 7205 10519
13 Locked QAM256 13 525000000 Hz -6.7 dBmV 41.8 dB 13406 14793
14 Locked QAM256 14 531000000 Hz -7.2 dBmV 41.4 dB 9959 13738
15 Locked QAM256 15 537000000 Hz -7.7 dBmV 41.2 dB 5957 14347
16 Locked QAM256 16 543000000 Hz -7.5 dBmV 41.1 dB 13305 8038
17 Locked QAM256 17 549000000 Hz -7.4 dBmV 41.3 dB 5410 4759
18 Locked QAM256 18 555000000 Hz -6.2 dBmV 41.8 dB 6833 8849
19 Locked QAM256 19 561000000 Hz -6.8 dBmV 41.5 dB 7712 9758
20 Locked QAM256 20 567000000 Hz -6.9 dBmV 41.2 dB 6716 8781
21 Locked QAM256 21 573000000 Hz -8.2 dBmV 40.5 dB 6392 8603
22 Locked QAM256 22 579000000 Hz -8.4 dBmV 40.4 dB 6418 10128
23 Locked QAM256 23 585000000 Hz -8.7 dBmV 40.2 dB 5851 8046
24 Locked QAM256 24 591000000 Hz -7.9 dBmV 40.8 dB 5636 6284
25 Locked QAM256 25 597000000 Hz -7.0 dBmV 40.9 dB 5177 5665
26 Locked QAM256 26 603000000 Hz -6.1 dBmV 41.3 dB 5628 7814
27 Locked QAM256 27 609000000 Hz -6.1 dBmV 41.5 dB 6604 7051
28 Locked QAM256 28 615000000 Hz -6.3 dBmV 41.6 dB 6606 7058
29 Locked QAM256 29 621000000 Hz -6.9 dBmV 41.3 dB 4981 3974
30 Locked QAM256 30 627000000 Hz -8.0 dBmV 40.8 dB 4414 3855
31 Locked QAM256 31 633000000 Hz -7.7 dBmV 40.7 dB 5853 7974
32 Locked QAM256 32 639000000 Hz -7.9 dBmV 40.6 dB 5883 6341
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 16400000 Hz 49.0 dBmV
2 Locked ATDMA 2 5120 22800000 Hz 49.8 dBmV
3 Locked ATDMA 3 5120 29200000 Hz 49.0 dBmV
4 Locked ATDMA 4 5120 35600000 Hz 50.5 dBmV
5 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
 
Downstream OFDM Channels
Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier
Number Range
Unerrored
Codewords
Correctable
Codewords
Uncorrectable
Codewords
1 Locked 0 ,1 ,2 ,3 193 957000000 Hz -10.6 dBmV 38.2 dB 148 ~ 3947 1081643734 760891591 6572
2 Not Locked 0 0 0 Hz 0 dBmV 0.0 dB 0 ~ 4095 0 0 0
 
Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV
 
Current System Time:Fri Jul 28 16:21:53 2023
System Up Time:3 days 06:28:52

Official Employee

 • 

1.5K Messages

Thank you for that additional information, we may need to get another set of eyes on this. Can you please send us a direct message to get started?

 

Here's the detailed steps to direct message us: • Click "Sign In" if necessary • Click the "Peer to peer chat" 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. 

If you could send our team a private message with your full name, the name listed on the account (if different), and the service address associated with your account, I'd be more than happy to look into this for you. 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Expert

 • 

110.8K Messages

2 years ago

@user_7998f9 

If there is nothing more that can be done to improve the connection quality, then you'll need a tech visit as stated. 


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 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 !

forum icon

New to the Community?

Start Here