4 Messages
Unstable upstream
Hello, my internet has been very unstable in the past week. I'm currently using a Netgear Nighthawk CM2000 modem paired with asus router, and I've been experiencing connection issues every 1-2 times hourly. My modem page says there is a upstream problem. Also the xfinity app shows all of my equipment is offline, when it isn't. Please advise!
Here's the cable diagnostic from my modem
Cable Diagnostic
Status: Poor
Action:
[Partial Service]
If the Partial Service mode does not go away within a few hours (Click the Refresh button after each step):
1) Make sure the coaxial cable is tightly connected.
2) Remove any unnecessary splitters.
3) Replace any required ones.
4) Contact your service provider for troubleshooting help.
[Upstream Power Level]
Try these actions (Click the Refresh button after each step):
1) Make sure the coaxial cable is tightly connected.
2) Remove any unnecessary splitters.
3) Replace any required splitters.
CM Status: Good
Downstream Status: Good
Downstream Power Level: Good
Downstream SNR Level: Good
Upstream Status: Bad
Partial Service: Poor
Cable modem is in partial service mode. Your service provider might be under maintenance. Most of the time it won't affect your traffic and will automatically clear when work is complete.
Upstream Power Level: Bad
Upstream power is poor (59.3dBmV). The recommended level is from 30 to 55dBmV.
Current Time: Mon Jun 03 22:00:18 2024
Startup Procedure
Acquire Downstream Channel: 591000000 Hz Locked
Connectivity State: OK Operational
Boot State: OK Operational
Security: Enabled BPI+
IP Provisioning Mode: Honor MDD IPv6 only
Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 28 591000000 Hz -3.2 44.5 15297 14538
2 Locked QAM256 13 501000000 Hz -5 44.3 15268 10674
3 Locked QAM256 14 507000000 Hz -4.9 44.2 39626 54185
4 Locked QAM256 15 513000000 Hz -4.9 44.4 48289 67152
5 Locked QAM256 16 519000000 Hz -4.9 44.2 41625 51237
6 Locked QAM256 17 525000000 Hz -4.7 44.2 46224 62189
7 Locked QAM256 18 531000000 Hz -4.6 44.5 43544 62774
8 Locked QAM256 19 537000000 Hz -5 44.2 40495 48653
9 Locked QAM256 20 543000000 Hz -5.1 44.2 49000 67630
10 Locked QAM256 21 549000000 Hz -4.9 44.4 40483 48335
11 Locked QAM256 22 555000000 Hz -4.8 44.5 48948 65442
12 Locked QAM256 23 561000000 Hz -4.4 44.7 49755 66952
13 Locked QAM256 24 567000000 Hz -4.3 44.5 53267 86856
14 Locked QAM256 25 573000000 Hz -4.2 44.4 49114 66412
15 Locked QAM256 26 579000000 Hz -4.1 44.4 48810 65345
16 Locked QAM256 27 585000000 Hz -3.6 44.7 51151 83970
17 Locked QAM256 29 597000000 Hz -3 44.9 41593 57168
18 Locked QAM256 30 603000000 Hz -3.1 44.9 46977 76757
19 Locked QAM256 31 609000000 Hz -3 45.1 41240 56627
20 Locked QAM256 32 615000000 Hz -2.8 45.4 39770 54664
21 Locked QAM256 33 621000000 Hz -2.8 45.4 37024 51930
22 Locked QAM256 34 627000000 Hz -2.8 45.3 46429 77636
23 Locked QAM256 35 633000000 Hz -2.8 45.2 46605 78908
24 Locked QAM256 36 639000000 Hz -2.9 45.1 47258 79579
25 Locked QAM256 37 645000000 Hz -2.7 45.2 35689 45416
26 Locked QAM256 38 651000000 Hz -2.8 45.2 42106 56676
27 Locked QAM256 39 657000000 Hz -3 45.1 40839 53451
28 Locked QAM256 40 663000000 Hz -3.4 44.9 52390 84022
29 Locked QAM256 41 669000000 Hz -3.4 44.9 46905 59658
30 Locked QAM256 42 675000000 Hz -3.2 43.9 46574 58297
31 Locked QAM256 43 681000000 Hz -3 45.1 40817 41798
32 Locked QAM256 44 687000000 Hz -2.7 44.8 42976 53942
Upstream Bonded Channels (Partial Service)
Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Not Locked Unknown 0 0 0 0.0
2 Locked ATDMA 2 5120 Ksym/sec 22800000 Hz 59.3 dBmV
3 Not Locked Unknown 0 0 0 0.0
4 Not Locked Unknown 0 0 0 0.0
5 Locked ATDMA 1 5120 Ksym/sec 16400000 Hz 59.3 dBmV
6 Not Locked Unknown 0 0 0 0.0
7 Not Locked Unknown 0 0 0 0.0
8 Not Locked Unknown 0 0 0 0.0
Downstream OFDM Channels
Channel LockedStatus ProfileID ChannelID Frequency Power SNR/MER ActiveSubcarrier Unerror Correctable Uncorrectable
1 Locked 0 ,1 ,2 ,3 193 722000000 Hz 0.18 dBmV 46.0 dB 1108 ~ 2987 61630566 341370 62861
2 Not Locked 0 0 0 Hz 0 dBmV 0 dB 0 ~ 4095 0 0 0
Upstream OFDMA Channels
Channel LockedStatus ProfileID ChannelID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV
Event Log
Time Priority Description
Mon Jun 03 21:50:48 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:49:32 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:49:31 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:49:21 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Mon Jun 03 21:48:48 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:45:22 2024 Warning (5) ToD request sent - No Response received;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:45:22 2024 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:45:00 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:52 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:48 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:48 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:33 2024 Error (4) DBC-ACK not received;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:32 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:29 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:27 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:18 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:03 2024 Warning (5) Dynamic Range Window violation
Mon Jun 03 21:44:03 2024 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:03 2024 Warning (5) Dynamic Range Window violation
Mon Jun 03 21:44:03 2024 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:03 2024 Warning (5) Dynamic Range Window violation
Mon Jun 03 21:44:03 2024 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:03 2024 Warning (5) Dynamic Range Window violation
Mon Jun 03 21:44:03 2024 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:44:01 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:59 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:59 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:47 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:47 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:40 2024 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:39 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:38 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:38 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:37 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:36 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:31 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:31 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:26 2024 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:13 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;
Mon Jun 03 21:43:03 2024 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;
EG
Expert
•
110.4K Messages
1 year ago
The upstream power is way out of spec (too high) ! And only two channels are locked in. The downstream power is a bit on the weak side as well.. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, 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 !
(edited)
4
0
EG
Expert
•
110.4K Messages
1 year ago
Apparently something intermittent is going on. You should consider getting a tech out to investigate 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 up 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 !
0
0