Visitor

 • 

2 Messages

Friday, August 14th, 2026 10:25 AM

Low Upstream Power and frequent internet connectivity issues

I've been dealing with a few issues on and off over the years. Finally doing some actual troubleshooting myself as the tech support has not been helpful. Symptoms are random internet connectivity issues/slowdown (not related to wifi) and also random reboots of my Orbi router, which I always was assumed was an Orbi problem up until recently (ChatGPT suggests that the WAN instability caused by low upstream power causes it to "protect itself" and reboot - see more on this below).

Last year, a tech did come to the house and said "your signal levels are way too low". He replaced the drop to the house (the line was full of water he said) and for a few months everything seemed to be good again, including the Orbi not rebooting.

Now more recently have had issue again. Looked at modem stats (I have my own Netgear CM1200). Everything looked good except upstream power was around 31 dBmV, which is apparently too low? I did some troubleshooting on my end to confirm no issues with house wiring. Removed all splitters and had a direct connection to the modem. Upstream power dropped to around 26-28 dBmV (depending on the channel). Interesting to note that when running with this low upstream power, my Orbi router went from "three times a day randomly rebooting" to "constant rebooting and 100% unusable" - so clearly GPT was correct and the upstream power is causing overall instability.

I put the splitter back in line and got my Orbi stable again. A tech did come out and said "your power levels are fine and the Orbi has nothing to do with it". He replaced my two way splitter with a three way splitter and left.

Internet still usable, but occasionally unstable.


Now fast forward three weeks from that. Internet is randomly dropping/slowing down (Orbi seems OK at those times, but still has it's own rebooting issues). I checked the CM1200 logs and it has a lot of "notice" messages which GPT says is indicating problems in the line and the modem is throttling back - which matches my symptoms without having told it what I was experiencing.

Tech support is unhelpful. What do I do? Upstream power is in the low 30s because a -7.5dBmV was put in line. Here are my CM1200 logs:

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 321000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD IPv6 only
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 4 321000000 Hz 2.8 dBmV 42.9 dB 1641 310
2 Locked QAM256 1 303000000 Hz 3.1 dBmV 42.9 dB 1594 370
3 Locked QAM256 2 309000000 Hz 3 dBmV 43.1 dB 1659 338
4 Locked QAM256 3 315000000 Hz 2.9 dBmV 43 dB 1699 320
5 Locked QAM256 5 327000000 Hz 2.8 dBmV 42.9 dB 1585 291
6 Locked QAM256 6 333000000 Hz 2.7 dBmV 42.9 dB 1606 360
7 Locked QAM256 7 339000000 Hz 2.5 dBmV 42.4 dB 1618 331
8 Locked QAM256 8 345000000 Hz 2.4 dBmV 42.8 dB 1760 264
9 Locked QAM256 9 351000000 Hz 2.5 dBmV 42.7 dB 1752 256
10 Locked QAM256 10 357000000 Hz 2.3 dBmV 42.3 dB 1713 248
11 Locked QAM256 11 363000000 Hz 2.3 dBmV 42.6 dB 1601 240
12 Locked QAM256 12 369000000 Hz 2.2 dBmV 42.6 dB 1541 202
13 Locked QAM256 13 375000000 Hz 2.2 dBmV 42.7 dB 1591 229
14 Locked QAM256 14 381000000 Hz 2.2 dBmV 42.7 dB 1442 239
15 Locked QAM256 15 387000000 Hz 2.3 dBmV 42.8 dB 7052 199
16 Locked QAM256 16 393000000 Hz 2.4 dBmV 42.8 dB 1400 261
17 Locked QAM256 17 399000000 Hz 2.3 dBmV 42.9 dB 1315 202
18 Locked QAM256 18 405000000 Hz 2.4 dBmV 42.9 dB 1259 169
19 Locked QAM256 19 411000000 Hz 2.3 dBmV 42.2 dB 1167 149
20 Locked QAM256 20 417000000 Hz 2.2 dBmV 42.8 dB 1125 174
21 Locked QAM256 21 423000000 Hz 2.2 dBmV 42.8 dB 1188 157
22 Locked QAM256 22 429000000 Hz 2.1 dBmV 42.8 dB 1077 169
23 Locked QAM256 23 435000000 Hz 2.1 dBmV 42.8 dB 1053 182
24 Locked QAM256 24 441000000 Hz 1.9 dBmV 42.7 dB 1119 162
25 Locked QAM256 25 447000000 Hz 1.7 dBmV 42.6 dB 1049 108
26 Locked QAM256 26 453000000 Hz 1.8 dBmV 42.6 dB 966 100
27 Locked QAM256 27 459000000 Hz 1.6 dBmV 42.7 dB 884 103
28 Locked QAM256 28 465000000 Hz 1.7 dBmV 42.7 dB 887 112
29 Locked QAM256 29 471000000 Hz 1.8 dBmV 42.7 dB 874 101
30 Locked QAM256 30 477000000 Hz 2 dBmV 42.8 dB 982 119
31 Locked QAM256 31 483000000 Hz 2.1 dBmV 42.9 dB 878 112
32 Locked QAM256 32 489000000 Hz 2.3 dBmV 42.8 dB 805 134
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 17 5120 Ksym/sec 16400000 Hz 32.8 dBmV
2 Locked ATDMA 18 5120 Ksym/sec 22800000 Hz 33.3 dBmV
3 Locked ATDMA 19 5120 Ksym/sec 29200000 Hz 33.5 dBmV
4 Locked ATDMA 20 5120 Ksym/sec 35600000 Hz 34 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 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 ,1 ,2 ,3 193 150000000 Hz 6.2 dBmV 42.8 dB 148 ~ 3947 1160680893 307433558 8665
2 Locked 0 ,1 ,2 ,3 194 900000000 Hz -3.3 dBmV 38.2 dB 268 ~ 3827 942937997 864917405 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

Modem Event logs:

Time

Priority

Description

Fri Aug 14 05:17:50 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Fri Aug 14 05:11:58 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 04:18:35 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Fri Aug 14 04:11:32 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 04:10:04 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 03:27:24 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Fri Aug 14 03:17:04 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 02:41:16 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Fri Aug 14 02:35:37 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 02:12:18 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Fri Aug 14 02:05:05 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 01:51:16 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Fri Aug 14 01:46:19 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 01:25:30 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Fri Aug 14 01:16:27 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 01:03:11 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Fri Aug 14 01:00:08 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 00:58:57 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 00:48:02 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Fri Aug 14 00:38:01 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 00:35:15 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Fri Aug 14 00:31:09 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 00:21:40 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Fri Aug 14 00:18:56 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Fri Aug 14 00:00:11 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Thu Aug 13 23:53:25 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; 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;

Thu Aug 13 21:53:18 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Thu Aug 13 21:50:04 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Thu Aug 13 21:42:30 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Thu Aug 13 21:39:46 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Thu Aug 13 20:22:03 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Thu Aug 13 19:25:34 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Thu Aug 13 19:23:49 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Thu Aug 13 18:55:44 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; 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;

Thu Aug 13 18:42:50 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Thu Aug 13 18:40:18 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Thu Aug 13 18:27:18 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Thu Aug 13 18:22:24 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Thu Aug 13 17:46:17 2026

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Thu Aug 13 17:42:10 2026

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=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

 

Oldest First
Selected Oldest First

Official Employee

 • 

386 Messages

5 hours ago

Hi there @user_t7fpeo Thank you so much for reaching out on our Xfinity Community Forum.  I'll be happy to assist.  Can you confirm the date of your last tech visit?

forum icon

New to the Community?

Start Here