Community Forum

CM1000 Modem Cutting out constantly; bad signal?

Regular Visitor

CM1000 Modem Cutting out constantly; bad signal?

Lately I have been having constant connectivity issues with my internet coming from Xfinity; Internet is up and down constantly and it's not showing up on the outage map in my area. I worked my way through my router logs and found nothing out of place except for internet signal loss from my modem. My Netgear CM1000 Modem Logs are full of critical errors with T3 timeouts (whatever that means).  I have always had issues getting full Gigabit speeds even after upgrading to a modem that is supposedly able to handle it.

 

Startup Procedure  
Procedure Status Comment
Acquire Downstream Channel 495000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only

 

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked QAM256 17 495000000 Hz -3.2 dBmV 31.4 dB 1058811536 206461 220563
2 Locked QAM256 12 465000000 Hz -1.4 dBmV 33.6 dB 1306491667 5101800 1743460
3 Locked QAM256 13 471000000 Hz -1.9 dBmV 33.0 dB 1303528119 6486043 2335630
4 Locked QAM256 14 477000000 Hz -2.2 dBmV 32.7 dB 1299795716 10355603 3057105
5 Locked QAM256 15 483000000 Hz -2.5 dBmV 32.2 dB 1297756171 11961458 3064712
6 Locked QAM256 16 489000000 Hz -3.2 dBmV 31.6 dB 1295131962 14312892 3418708
7 Locked QAM256 18 501000000 Hz -3.8 dBmV 31.0 dB 1290900962 21068514 5537172
8 Locked QAM256 19 507000000 Hz -3.9 dBmV 30.6 dB 1283994068 25829002 7020303
9 Locked QAM256 20 513000000 Hz -4.4 dBmV 30.2 dB 1274637289 31960581 9728277
10 Locked QAM256 21 519000000 Hz -4.6 dBmV 30.0 dB 1270810536 34156683 10415032
11 Locked QAM256 22 525000000 Hz -4.8 dBmV 29.8 dB 1275174748 32389787 8771476
12 Locked QAM256 23 531000000 Hz -5.2 dBmV 29.4 dB 1264964487 39403456 12103241
13 Locked QAM256 24 537000000 Hz -5.3 dBmV 29.1 dB 1256261774 44648130 16110722
14 Locked QAM256 25 543000000 Hz -5.6 dBmV 28.9 dB 1249472832 50129604 18530017
15 Locked QAM256 26 549000000 Hz -5.6 dBmV 28.9 dB 1254223512 47707896 13812229
16 Locked QAM256 27 555000000 Hz -5.4 dBmV 28.9 dB 1263620578 42039870 11402847
17 Locked QAM256 28 561000000 Hz -5.4 dBmV 28.9 dB 1262439084 43803550 11389430
18 Locked QAM256 29 567000000 Hz -5.5 dBmV 28.9 dB 1262683802 45681710 11858876
19 Locked QAM256 30 573000000 Hz -5.4 dBmV 28.9 dB 1260491948 45768761 13059583
20 Locked QAM256 31 579000000 Hz -5.2 dBmV 29.3 dB 1277757581 32088184 8386851
21 Locked QAM256 32 585000000 Hz -4.8 dBmV 29.4 dB 1286367725 26206867 5951391
22 Locked QAM256 33 591000000 Hz -4.7 dBmV 29.6 dB 1292873789 21550441 4492341
23 Locked QAM256 34 597000000 Hz -4.8 dBmV 29.9 dB 1298055594 17030491 3617534
24 Locked QAM256 35 603000000 Hz -4.7 dBmV 30.0 dB 1249850769 15608940 3226744
25 Locked QAM256 36 609000000 Hz -4.4 dBmV 30.4 dB 396945563 3791384 2392430
26 Locked QAM256 37 615000000 Hz -4.0 dBmV 30.8 dB 396780124 2449851 2062622
27 Locked QAM256 38 621000000 Hz -3.7 dBmV 31.0 dB 397532995 1879218 1908763
28 Locked QAM256 39 627000000 Hz -3.3 dBmV 31.5 dB 398144687 1493339 1770329
29 Locked QAM256 40 633000000 Hz -3.0 dBmV 31.6 dB 395539604 1069551 1525797
30 Locked QAM256 41 639000000 Hz -2.5 dBmV 32.1 dB 395940800 880612 1398166
31 Locked QAM256 42 645000000 Hz -1.8 dBmV 32.5 dB 396155253 784583 1274631
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0

 

Upstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power
1 Locked ATDMA 1 36100000 Hz 47.8 dBmV
2 Locked ATDMA 2 29600000 Hz 47.8 dBmV
3 Locked ATDMA 3 23000000 Hz 47.8 dBmV
4 Locked ATDMA 4 16500000 Hz 47.3 dBmV
5 Not Locked Unknown 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Hz 0.0 dBmV

 

Downstream OFDM Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked 0, 255 48 690000000 Hz 2.4 dBmV 33.8 dB 1348 ~ 2747 2552121222 2423001505 416
2 Not Locked 0, 255 0 0 Hz 6.1 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 Unknown 0 0 Hz 0 dBmV
2 Not Locked Unknown 0 0 Hz 0 dBmV

 

Error Log

Time Priority Description
2019-06-23, 20:46:16 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 12 13 14 15 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-Q
2019-06-23, 20:46:16 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:14 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 23 24 25 26 27 28 29 30 31 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:14 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:12 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 23 25 26 27 28 29 30 31 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:12 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:10 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 12 13 14 15 16 18 19 20 21 22 23 24 32 33 34 35 36 37 38 39 40 41 42 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:08 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 27 28 29 30 31 32 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:08 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:06 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 12 13 14 15 16 18 19 20 21 22 23 24 32 33 34 35 36 37 38 39 40 41 42 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:06 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 27 28 29 30 31 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:06 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:04 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 28 29 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:03 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:02 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 28 29 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:46:01 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:10:52 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 1 2 3 4 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:10:52 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:10:52 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:51 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 1 2 3 4 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:50 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:50 Notice (6) CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:49 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:49 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:49 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:44 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:43 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 2 3 4 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:42 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:42 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:25 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:19 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 2 3 4 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:18 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:18 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 2 3 4 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:17 Notice (6) CM-STATUS message sent. Event Type Code: 7; Chan ID: 4 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:16 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:09:16 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:08:09 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:08:05 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:07:25 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 12 13 14 15 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-Q
2019-06-23, 20:07:25 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:07:21 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 30 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:07:21 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:06:55 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 12 13 14 15 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-Q
2019-06-23, 20:06:54 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:06:51 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 26 28 29 30 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:06:50 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:06:49 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 26 29 30 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:06:48 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:06:46 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 29 30 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:06:46 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:06:40 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 12 13 14 15 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-Q
2019-06-23, 20:06:39 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 27 28 29 30 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:06:38 Warning (5) MDD message timeout;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:06:33 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 27 28 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1;CM-VER=3.1;
2019-06-23, 20:06:33 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 12 13 14 15 16 18 19 20 21 22 23 24 25 26 29 30 31 32 33 34 35 36 37 38 39 40 41 42 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= [MAC REMOVED];CMTS-MAC=00:01:5c:9c:9a:5a;CM-QOS=1.1
Expert

Re: CM1000 Modem Cutting out constantly; bad signal?

Yes. "Bad signal" ! The SNR is too low / out of spec. That can cause random disconnects, spontaneous re-booting of the modem, and speed and latency problems.

In a self troubleshooting effort to try to obtain better connectivity, 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-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

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.



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? Mark the post as Best Answer!
Regular Visitor

Re: CM1000 Modem Cutting out constantly; bad signal?

This was a line dropped to my brand new house back in 2015 and there's really nothing on it other than my Modem, no splitters that I remember but I'll look. Either way it sounds like that I need to have a technician out here to address the signal issues and maybe check the line out to the street.  Thanks for confirming my suspicions, I was worried I had equipment problems.

Expert

Re: CM1000 Modem Cutting out constantly; bad signal?

Good luck with it ! Please post back with how things turn out.



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? Mark the post as Best Answer!
Official Employee

Re: CM1000 Modem Cutting out constantly; bad signal?

Hi htxengy, thank you for reaching out and welcome to our community forums.  Please send me a private message if you are still experiencing disconnects and I can help schedule a technician for you.

 

Thank you 


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Official Employee

Re: CM1000 Modem Cutting out constantly; bad signal?

Hi htxengy, I haven't heard from you but please reach back out if you still need assistance and we will help.

 

Thank you 


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Regular Visitor

Re: CM1000 Modem Cutting out constantly; bad signal?

Xfinity support was unwilling to send a technician without me contacting my Modem manufacturer first. The manufacturer (Netgear) wanted to charge me money for support service to RMA the modem (which I already figured was not at fault given my continued monitoring of logs on my PC, router, and modem), so I opted not to do that based on the response on this forum. ATT customers in a neighborhood forum in my area mentioned that ATT had informed them of widespread signal issues in our area (similar details from Xfinity were not offered to ME even though it sounded like the same problem), so just waited it out. I have now been 121 hours without loss of internet after doing NOTHING but wait, and have not been contacted at any time by Xfinity of any issues that existed that were repaired.

 

Honestly I am very disappointed in the level of details that I were provided by xfinity and at no point did Xfinity attempt to inform me of ongoing issues when other ISPs were apparently very forthcoming.

Highlighted
Official Employee

Re: CM1000 Modem Cutting out constantly; bad signal?

Hello htxengy. We're sorry you feel that way. My colleague here in the Forums, ComcastPhill tried to reach out to you, so we can get your information to pull your account and troubleshoot. We never got a response. I am glad to hear you have been without loss of internet so far. 

 

Please let us know if you need any further assistance.  We're happy to help when needed. 


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Official Employee

Re: CM1000 Modem Cutting out constantly; bad signal?

Hi htxengy, thank you for working with us through private message and please reach back out if you need assistance in the future.

 

Thank you 


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!