mcavallari's profile

Frequent Visitor

 • 

18 Messages

Sunday, December 18th, 2022 8:21 PM

Closed

Intermitten Drops - Gigabit Internet - Event Type 16 Errors in Modem Logs

I think I may need an XFinity tech to come out an inspect our outside line as we have for a number of weeks now been getting drops / slowness in our internet connection (multiple times per hour). Upon further inspection of our modem logs (SB8200) I can see many Event Type Code: 16 and subsequent Event Type Code: 24 per hour.

This conversation is no longer open for comments or replies and is no longer visible to community members.

Expert

 • 

110.3K Messages

2 years ago

What do the modem's signal stats look like ? 

Please 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.

Please post those error log entries as well in their entirety (copy and paste them, don't post a screenshot) but redact the CM MAC and the CMTS MAC addresses for your privacy. They are considered to be personal information. The posting of personally identifying information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically.

Is this with a router / WiFi connection in the mix ?

Frequent Visitor

 • 

18 Messages

2 years ago

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
4 Locked QAM256 471000000 Hz -3.6 dBmV 42.7 dB 0 0
1 Locked QAM256 453000000 Hz -2.4 dBmV 43.6 dB 0 0
2 Locked QAM256 459000000 Hz -3.0 dBmV 43.2 dB 0 0
3 Locked QAM256 465000000 Hz -3.4 dBmV 43.0 dB 0 0
5 Locked QAM256 477000000 Hz -3.7 dBmV 42.6 dB 0 0
6 Locked QAM256 483000000 Hz -3.7 dBmV 42.7 dB 0 0
7 Locked QAM256 489000000 Hz -3.6 dBmV 42.8 dB 0 0
8 Locked QAM256 495000000 Hz -3.6 dBmV 42.8 dB 0 0
9 Locked QAM256 501000000 Hz -3.8 dBmV 42.8 dB 0 0
10 Locked QAM256 507000000 Hz -3.9 dBmV 42.4 dB 0 0
11 Locked QAM256 513000000 Hz -4.5 dBmV 42.2 dB 0 0
12 Locked QAM256 519000000 Hz -5.2 dBmV 41.6 dB 0 0
13 Locked QAM256 525000000 Hz -5.8 dBmV 41.2 dB 0 0
14 Locked QAM256 531000000 Hz -6.0 dBmV 41.2 dB 0 0
15 Locked QAM256 537000000 Hz -6.3 dBmV 41.0 dB 0 0
16 Locked QAM256 543000000 Hz -6.5 dBmV 40.8 dB 0 0
17 Locked QAM256 549000000 Hz -6.5 dBmV 40.8 dB 0 0
18 Locked QAM256 555000000 Hz -6.5 dBmV 38.6 dB 0 0
19 Locked QAM256 561000000 Hz -6.2 dBmV 41.1 dB 0 0
20 Locked QAM256 567000000 Hz -6.8 dBmV 40.1 dB 0 0
21 Locked QAM256 573000000 Hz -7.0 dBmV 39.6 dB 0 0
22 Locked QAM256 579000000 Hz -7.6 dBmV 40.0 dB 0 0
23 Locked QAM256 585000000 Hz -7.5 dBmV 40.2 dB 0 0
24 Locked QAM256 591000000 Hz -7.8 dBmV 39.6 dB 0 0
25 Locked QAM256 597000000 Hz -7.7 dBmV 39.9 dB 0 0
26 Locked QAM256 603000000 Hz -7.8 dBmV 39.8 dB 0 0
27 Locked QAM256 609000000 Hz -7.7 dBmV 40.2 dB 0 0
28 Locked QAM256 615000000 Hz -7.5 dBmV 40.4 dB 0 0
29 Locked QAM256 621000000 Hz -7.6 dBmV 40.2 dB 0 0
30 Locked QAM256 627000000 Hz -7.7 dBmV 39.9 dB 0 0
31 Locked QAM256 633000000 Hz -8.0 dBmV 39.9 dB 0 0
32 Locked QAM256 639000000 Hz -7.8 dBmV 40.0 dB 0 0
193 Locked Other 957000000 Hz -13.7 dBmV 29.0 dB 1078578162 2543


Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 17 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 40.0 dBmV
2 18 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 41.0 dBmV
3 19 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 42.0 dBmV
4 20 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 42.0 dBmV


Date Time Event ID Event Level Description
12/18/2022 16:00 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:59 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:59 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:58 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:58 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:57 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:56 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:56 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:54 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:53 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:50 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:49 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:47 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:46 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:45 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:44 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:42 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:41 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:40 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:40 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:32 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:31 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:31 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:30 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:28 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:27 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:26 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:26 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:25 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:24 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:22 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:21 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:21 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:20 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:19 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:18 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:17 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:15 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:15 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:14 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:14 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:13 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:13 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
12/18/2022 15:10 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"

Frequent Visitor

 • 

18 Messages

2 years ago

The intermittent connectivity issues occur on both devices connected to Wifi (via Google Wifi AC1200 Dual-Band) as well as those connected directly via ethernet cable (router)

Expert

 • 

110.3K Messages

2 years ago

The downstream power is on the low / weak side and it may be intermittently fluctuating even lower to out of spec levels. The OFDM channel is already out of spec. It appears that a condition exists that is called *cable tilt*. This is where the higher frequency downstream channel's power levels roll-off more compared to the lower channels). 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 Radio Shack, Home Depot, Target, 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 perhaps it's best to book a tech visit to investigate and correct.


Good luck with it !

Frequent Visitor

 • 

18 Messages

@EG​ Wanted to get your thoughts on my current signals and event logs given that the coax cable from pedestal/road to house was replaced. Xfinity tech was out a few weeks back and mentioned two issues 1) Signal loss between road and house was too large and recommend replacing line (which was recently completed). 2) Reported signal levels at pedestal/road was low.

Why is the OFDM channel having the most issues (low power & Bad SNR)?

Thanks in advance - greatly appreciated!

Signal Levels 

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
20 Locked QAM256 567000000 Hz -4.7 dBmV 41.3 dB 0 0
13 Locked QAM256 525000000 Hz -4.0 dBmV 42.2 dB 0 0
14 Locked QAM256 531000000 Hz -4.1 dBmV 42.2 dB 0 0
15 Locked QAM256 537000000 Hz -4.5 dBmV 42.0 dB 0 0
16 Locked QAM256 543000000 Hz -4.6 dBmV 41.9 dB 0 0
17 Locked QAM256 549000000 Hz -4.6 dBmV 42.0 dB 0 0
18 Locked QAM256 555000000 Hz -4.5 dBmV 41.5 dB 0 0
19 Locked QAM256 561000000 Hz -4.2 dBmV 42.4 dB 0 0
21 Locked QAM256 573000000 Hz -4.9 dBmV 41.6 dB 0 0
22 Locked QAM256 579000000 Hz -5.5 dBmV 41.6 dB 0 0
23 Locked QAM256 585000000 Hz -5.4 dBmV 41.4 dB 0 0
24 Locked QAM256 591000000 Hz -5.7 dBmV 40.5 dB 0 0
25 Locked QAM256 597000000 Hz -5.7 dBmV 41.2 dB 1 0
26 Locked QAM256 603000000 Hz -5.8 dBmV 41.2 dB 0 0
27 Locked QAM256 609000000 Hz -5.6 dBmV 41.6 dB 0 0
28 Locked QAM256 615000000 Hz -5.5 dBmV 41.7 dB 0 0
29 Locked QAM256 621000000 Hz -5.5 dBmV 41.5 dB 0 0
30 Locked QAM256 627000000 Hz -5.6 dBmV 41.4 dB 0 0
31 Locked QAM256 633000000 Hz -5.9 dBmV 41.2 dB 1 0
32 Locked QAM256 639000000 Hz -5.7 dBmV 41.4 dB 1 0
33 Locked QAM256 645000000 Hz -6.2 dBmV 40.9 dB 1 0
34 Locked QAM256 651000000 Hz -6.3 dBmV 40.7 dB 1 0
35 Locked QAM256 657000000 Hz -6.6 dBmV 40.5 dB 2 0
36 Locked QAM256 663000000 Hz -6.7 dBmV 40.6 dB 2 0
37 Locked QAM256 669000000 Hz -6.8 dBmV 40.4 dB 1 0
38 Locked QAM256 675000000 Hz -7.2 dBmV 38.7 dB 0 0
39 Locked QAM256 681000000 Hz -7.0 dBmV 40.2 dB 0 0
40 Locked QAM256 687000000 Hz -7.1 dBmV 40.0 dB 1 0
41 Locked QAM256 693000000 Hz -6.7 dBmV 40.4 dB 0 0
42 Locked QAM256 699000000 Hz -6.7 dBmV 40.3 dB 0 0
43 Locked QAM256 705000000 Hz -6.5 dBmV 40.5 dB 0 0
44 Locked QAM256 711000000 Hz -6.6 dBmV 40.4 dB 164 141
193 Locked Other 957000000 Hz -11.9 dBmV 30.5 dB 705614700 3868


 

Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 17 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 39.0 dBmV
2 18 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 40.0 dBmV
3 19 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 41.0 dBmV
4 20 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 42.0 dBmV


 

Current System Time: Tue Jan 10 15:11:36 2023

Event Logs

Date Time Event ID Event Level Description
01/10/2023 15:05 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 15:05 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 15:04 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:59 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:44 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:41 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:41 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:11 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:11 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:10 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:09 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:07 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:07 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:06 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:05 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:03 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:01 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 14:00 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:59 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:58 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:58 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:55 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:54 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:53 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:43 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:41 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:37 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:34 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:34 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:25 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:16 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:15 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:15 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:07 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:07 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:06 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 13:03 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 12:17 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 12:17 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 12:17 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/10/2023 12:16 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"

Expert

 • 

110.3K Messages

@mcavallari​ 

It's just as bad as it was..... More work needs to be done. You need to get the techs involved again until the problem gets fixed properly. I'll state this again; "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."

You wrote: "Why is the OFDM channel having the most issues (low power & Bad SNR)?"

Because it operates at such a high frequency, and as I stated, and there is an existing cable tilt condition that makes the higher frequency channel power levels roll off much more than the lower frequencies. And low power creates low SNR. The signal is not high enough above the noise floor. I can't believe that the tech left it that way....... You are going to have to keep leaning on Comcast !! Good luck with it !

(edited)

I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Please mark an Accepted Answer!tick

Frequent Visitor

 • 

18 Messages

2 years ago

I confirmed there are no splitters used in my setup - we are located at the end of a cul-de-sac and my next door neighbor mentioned that they have been experiencing intermittent outages with their Xfinity TV service (we are internet only). I have NOT made any changes to my internal COAX in years (nor any other network changes) and this problem is recent in past couple of months. Looking at logs from past few days looks like issues start occurring late morning (11am ish) and looking at Event logs (as seen above) issue corrects itself usually within a minute but can occasional take much longer.

Event logs shows Type code 16 errors always on Channel ID: 193 (Not on any other channel) not sure if that means anything.

(edited)

Expert

 • 

110.3K Messages

2 years ago

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 !

Frequent Visitor

 • 

18 Messages

Thanks @EG​.  Is there a way to initiate a tech visit online?

Expert

 • 

110.3K Messages

2 years ago

I think that you can through the Xfinity App if you have it.

Frequent Visitor

 • 

18 Messages

2 years ago

Update: Xfinity Tech came out and stated the power levels at street was low and that the loss in signal from the road/drop to our house was more than expected. His recommendation was to replace the underground cable from drop/road to our house as well as have another crew/team address the power levels at road/drop location.

Cable from drop/road to our house was recently replaced - I do NOT know or have insight into what if anything was done to address power levels at street / drop location.

HOWEVER - I am still experiencing internet disruptions and see the following error codes in modem event logs (today). Any suggestions?

Event Log

01/05/2023 15:19 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 11:40 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 11:39 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 11:39 74010100 6 "CM-STATUS message sent. Event Type Code: 5; Chan ID: 33 34 35 36 37 38 39 40 41 42 43 44; 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;"
01/05/2023 11:39 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; 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;"
01/05/2023 11:39 82000400 3 "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;"
01/05/2023 11:39 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 11:39 84020300 5 "MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 11:16 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 06:09 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 04:01 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:54 74010100 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=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:54 85000200 3 "UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:54 67061600 6 "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;"
01/05/2023 03:44 85000200 3 "UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:35 74010100 6 "CM-STATUS message sent. Event Type Code: 1; Chan ID: 193; 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;"
01/05/2023 03:34 84020300 5 "MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:34 74010100 6 "CM-STATUS message sent. Event Type Code: 21; Chan ID: 193; 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;"
01/05/2023 03:34 85000200 3 "UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:34 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:34 85000200 3 "UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:34 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:34 85000200 3 "UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:34 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:34 67061600 6 "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;"
01/05/2023 03:34 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
01/05/2023 03:34 85000200 3 "UCD invalid or channel unusable;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:33 84000100 3 "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;"
01/05/2023 03:30 82000400 3 "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;"
01/05/2023 03:30 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:30 82000400 3 "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;"
01/05/2023 03:30 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:29 84020300 5 "MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:29 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:29 84020300 5 "MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 03:29 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"
01/05/2023 02:29 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;"

Status

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
20 Locked QAM256 567000000 Hz -4.9 dBmV 38.5 dB 84 216
13 Locked QAM256 525000000 Hz -4.4 dBmV 38.7 dB 1 0
14 Locked QAM256 531000000 Hz -4.5 dBmV 38.8 dB 92 481
15 Locked QAM256 537000000 Hz -4.7 dBmV 38.6 dB 97 477
16 Locked QAM256 543000000 Hz -4.7 dBmV 38.6 dB 87 491
17 Locked QAM256 549000000 Hz -4.7 dBmV 38.5 dB 99 478
18 Locked QAM256 555000000 Hz -4.6 dBmV 38.7 dB 105 472
19 Locked QAM256 561000000 Hz -4.4 dBmV 39.0 dB 96 482
21 Locked QAM256 573000000 Hz -5.1 dBmV 38.4 dB 97 436
22 Locked QAM256 579000000 Hz -5.8 dBmV 38.0 dB 76 457
23 Locked QAM256 585000000 Hz -5.6 dBmV 38.1 dB 91 455
24 Locked QAM256 591000000 Hz -5.9 dBmV 37.9 dB 112 436
25 Locked QAM256 597000000 Hz -5.8 dBmV 37.8 dB 113 506
26 Locked QAM256 603000000 Hz -6.0 dBmV 37.7 dB 103 502
27 Locked QAM256 609000000 Hz -5.8 dBmV 37.9 dB 114 493
28 Locked QAM256 615000000 Hz -5.7 dBmV 37.9 dB 113 499
29 Locked QAM256 621000000 Hz -5.8 dBmV 37.6 dB 93 520
30 Locked QAM256 627000000 Hz -6.0 dBmV 37.6 dB 103 519
31 Locked QAM256 633000000 Hz -6.4 dBmV 37.4 dB 118 509
32 Locked QAM256 639000000 Hz -6.2 dBmV 37.7 dB 170 521
33 Locked QAM256 645000000 Hz -6.6 dBmV 37.3 dB 169 577
34 Locked QAM256 651000000 Hz -6.7 dBmV 37.1 dB 284 1042
35 Locked QAM256 657000000 Hz -7.0 dBmV 36.7 dB 343 1033
36 Locked QAM256 663000000 Hz -7.1 dBmV 36.4 dB 289 1043
37 Locked QAM256 669000000 Hz -7.2 dBmV 36.4 dB 278 1015
38 Locked QAM256 675000000 Hz -7.9 dBmV 35.1 dB 276 1020
39 Locked QAM256 681000000 Hz -7.7 dBmV 36.0 dB 197 1039
40 Locked QAM256 687000000 Hz -7.9 dBmV 36.0 dB 193 1003
41 Locked QAM256 693000000 Hz -7.3 dBmV 36.6 dB 219 1021
42 Locked QAM256 699000000 Hz -7.4 dBmV 36.6 dB 190 905
43 Locked QAM256 705000000 Hz -7.1 dBmV 36.6 dB 174 922
44 Locked QAM256 711000000 Hz -7.2 dBmV 36.4 dB 184 911
193 Locked Other 957000000 Hz -12.6 dBmV 26.0 dB 2363451139 1460806921


Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 17 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 39.0 dBmV
2 18 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 40.0 dBmV
3 19 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 41.0 dBmV
4 20 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 42.0 dBmV


Current System Time: Thu Jan 5 15:34:17 2023

(edited)

Problem Solver

 • 

908 Messages

Hello @mcavallari

 

Thank you for reaching out with an update for us. Let's try some remote troubleshooting. Please send a direct message with your first and last name, as well as complete service address to "Xfinity Support". To do so, click on the chat icon located at the top right of this forums page.
 
 1. Click "Sign In" if necessary
 2. Click the "Direct Messaging" icon (upper right corner of this page)
 3. Click the "New message" (pencil and paper) icon
 4. Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list
 5. Type your message in the text area near the bottom of the window
Press Enter to send your message

I no longer work for Comcast.

Frequent Visitor

 • 

18 Messages

2 years ago

@EG  - Wanted to see if you could review my current modem signals (to rule in or out connection issues) and provide any suggestions. An Xfinity Line crew made some changes in my neighborhood which improved the signal levels and SNR; however, I am still experiencing some network "hicups" where I will get brief (15 secs to 1 min) drops in connection - network quality. Not sure if it may be an issue my my modem (SB8200) or my Google Wifi Mesh units.  

Note: These brief network disruptions (before the Xfinity Line Crew changes today) was linked to Event Type 16 & 24 errors in my modem event log) - last few hours I have NOT seen those but have had some brief network performance hicups.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 567000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

 

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
20 Locked QAM256 567000000 Hz 2.6 dBmV 42.4 dB 1 0
1 Locked QAM256 453000000 Hz 5.5 dBmV 43.5 dB 0 0
2 Locked QAM256 459000000 Hz 4.9 dBmV 43.4 dB 0 0
3 Locked QAM256 465000000 Hz 4.7 dBmV 43.2 dB 0 0
4 Locked QAM256 471000000 Hz 4.5 dBmV 43.0 dB 0 0
5 Locked QAM256 477000000 Hz 4.5 dBmV 43.0 dB 1 0
6 Locked QAM256 483000000 Hz 4.5 dBmV 43.3 dB 1 0
7 Locked QAM256 489000000 Hz 4.7 dBmV 43.1 dB 1 0
8 Locked QAM256 495000000 Hz 4.8 dBmV 43.3 dB 0 0
9 Locked QAM256 501000000 Hz 4.7 dBmV 43.4 dB 0 0
10 Locked QAM256 507000000 Hz 4.6 dBmV 43.2 dB 0 0
11 Locked QAM256 513000000 Hz 4.1 dBmV 43.0 dB 0 0
12 Locked QAM256 519000000 Hz 3.5 dBmV 42.6 dB 0 0
13 Locked QAM256 525000000 Hz 3.0 dBmV 42.6 dB 0 0
14 Locked QAM256 531000000 Hz 2.9 dBmV 42.6 dB 0 0
15 Locked QAM256 537000000 Hz 2.7 dBmV 42.5 dB 0 0
16 Locked QAM256 543000000 Hz 2.6 dBmV 42.4 dB 0 0
17 Locked QAM256 549000000 Hz 2.7 dBmV 42.5 dB 0 0
18 Locked QAM256 555000000 Hz 2.8 dBmV 42.7 dB 0 0
19 Locked QAM256 561000000 Hz 3.1 dBmV 42.9 dB 1 0
21 Locked QAM256 573000000 Hz 2.5 dBmV 41.9 dB 0 0
22 Locked QAM256 579000000 Hz 2.0 dBmV 42.2 dB 0 0
23 Locked QAM256 585000000 Hz 2.2 dBmV 42.4 dB 2 0
24 Locked QAM256 591000000 Hz 1.9 dBmV 42.3 dB 1 0
25 Locked QAM256 597000000 Hz 2.1 dBmV 42.3 dB 0 0
26 Locked QAM256 603000000 Hz 2.0 dBmV 42.3 dB 0 0
27 Locked QAM256 609000000 Hz 2.2 dBmV 42.4 dB 0 0
28 Locked QAM256 615000000 Hz 2.3 dBmV 42.4 dB 0 0
29 Locked QAM256 621000000 Hz 2.3 dBmV 42.5 dB 0 0
30 Locked QAM256 627000000 Hz 2.2 dBmV 42.5 dB 0 0
31 Locked QAM256 633000000 Hz 2.0 dBmV 42.4 dB 0 0
32 Locked QAM256 639000000 Hz 2.3 dBmV 42.5 dB 0 0
193 Locked Other 957000000 Hz -1.7 dBmV 36.2 dB 305985690 0


 

Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 17 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 40.0 dBmV
2 18 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 40.0 dBmV
3 19 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 41.0 dBmV
4 20 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 42.0 dBmV


 

Current System Time: Wed Jan 25 16:27:41 2023

Problem Solver

 • 

908 Messages

@mcavallari Thanks for continuing to work with our expert, @EG (thank you, @EG for your help here!) Has their last suggestion helped at all?

I no longer work for Comcast.

Expert

 • 

110.3K Messages

2 years ago

@mcavallari 

Sure. There is still a bit of a roll-off of power of the higher frequency channels (+5.5 dB at channel #1 to -1.7 dB at the *Other* / OFDM channel) but 957 MHz is a very high frequency ! But it is very much better ! You are on a 1000 / 1002 MHz plant now. Years ago cable plants only went to 550 MHz and then to 850 MHz.

That said. To narrow things down, see if a computer that is hardwired via an ethernet cable to the main Google mesh router has the same problem. You could even hardwire directly to the 8200 cable modem and see.

forum icon

New to the Community?

Start Here