Forum Discussion

Brian_or_Elizab's avatar
Brian_or_Elizab
New Contributor
2 years ago

Internet Freezes

I am having an intermittent problem with my internet connection freezing which is affecting my ability to work at home (I video conference a lot). 

I have tried numerous options to improve things (using RG6 quad shielded cables and ensuring they are tight) including replacing my modem with a brand new one ... but the problem continues.  My speeds are wonderful when it is working (850+ Download and 35+ Upload).  Both my upstream and downstream dBmV levels are well within specification.  I have noticed that when I am having problems the counters for Correctables and Uncorrectables increase significantly.  These are my logs after just an hour of run time.

I currently have a 6db attenuator at my cable modem because without it, I was at 35-36 dBMV on Upstream Channel 5 (Channel ID 6) ... thinking it was out of specification.

I don't use my cable line for anything except internet modem (no splitters or other devices connected to it, such as cable tv boxes).

I almost always seems to lose connection at about 10am EST daily but it does happen at other times too.

Any advice?

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 29 849000000 Hz 1.6 dBmV 44.2 dB 54 141
2 Locked QAM256 1 681000000 Hz -2.2 dBmV 43.3 dB 70 30
3 Locked QAM256 2 687000000 Hz -2.1 dBmV 43.2 dB 457 1561
4 Locked QAM256 3 693000000 Hz -2.2 dBmV 43.1 dB 445 1648
5 Locked QAM256 4 699000000 Hz -2.3 dBmV 43.1 dB 433 1590
6 Locked QAM256 5 705000000 Hz -1.9 dBmV 43.2 dB 472 1536
7 Locked QAM256 6 711000000 Hz -1.9 dBmV 43.2 dB 472 1542
8 Locked QAM256 7 717000000 Hz -1.8 dBmV 43.2 dB 401 1559
9 Locked QAM256 8 723000000 Hz -1.7 dBmV 43.2 dB 413 1565
10 Locked QAM256 9 729000000 Hz -1.8 dBmV 43.2 dB 439 1542
11 Locked QAM256 10 735000000 Hz -1.9 dBmV 43 dB 433 1589
12 Locked QAM256 11 741000000 Hz -1.8 dBmV 42.9 dB 397 1634
13 Locked QAM256 12 747000000 Hz -2 dBmV 43 dB 415 1676
14 Locked QAM256 13 753000000 Hz -2 dBmV 43 dB 453 1676
15 Locked QAM256 14 759000000 Hz -1.9 dBmV 43 dB 436 1628
16 Locked QAM256 15 765000000 Hz -1.9 dBmV 43 dB 481 1608
17 Locked QAM256 16 771000000 Hz -1.3 dBmV 43.3 dB 408 1625
18 Locked QAM256 17 777000000 Hz -0.9 dBmV 43.5 dB 421 1663
19 Locked QAM256 18 783000000 Hz -0.4 dBmV 43.6 dB 337 1624
20 Locked QAM256 19 789000000 Hz -0.4 dBmV 43.7 dB 411 1623
21 Locked QAM256 20 795000000 Hz -0.5 dBmV 43.7 dB 456 1625
22 Locked QAM256 21 801000000 Hz -0.7 dBmV 43.5 dB 438 1677
23 Locked QAM256 22 807000000 Hz -0.5 dBmV 43.5 dB 519 1700
24 Locked QAM256 23 813000000 Hz -0.3 dBmV 43.5 dB 441 1611
25 Locked QAM256 24 819000000 Hz 0.4 dBmV 43.8 dB 490 1655
26 Locked QAM256 25 825000000 Hz 0.7 dBmV 44 dB 403 1603
27 Locked QAM256 26 831000000 Hz 0.6 dBmV 43.9 dB 359 1715
28 Locked QAM256 27 837000000 Hz 0.7 dBmV 43.9 dB 423 1651
29 Locked QAM256 28 843000000 Hz 1.2 dBmV 44.1 dB 361 1694
30 Locked QAM256 30 855000000 Hz 1.7 dBmV 44.3 dB 369 1641
31 Locked QAM256 31 861000000 Hz 1.4 dBmV 44.2 dB 380 1643
32 Locked QAM256 32 867000000 Hz 1.3 dBmV 44.3 dB 394 1578
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 17600000 Hz 46.8 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 24000000 Hz 47.5 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 30400000 Hz 47.3 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 36800000 Hz 47.3 dBmV
5 Locked ATDMA 6 2560 Ksym/sec 12800000 Hz 43.8 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 159 300000000 Hz -3.2 dBmV 43.0 dB 2216 ~ 5975 87490710 27181243 17118
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

Mon Oct 24 10:50:19 2022 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:49:51 2022 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:44:31 2022 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:44:00 2022 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:43:59 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:43:50 2022 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:41:14 2022 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:40:53 2022 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:40:24 2022 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:38:07 2022 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:37:38 2022 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:36:55 2022 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:36:35 2022 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:31:36 2022 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:31:29 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:31:26 2022 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:31:26 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:31:15 2022 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:31:14 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:31:05 2022 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:24:13 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:22:58 2022 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:22:36 2022 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:14:54 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:01:34 2022 Warning (5) Dynamic Range Window violation
Mon Oct 24 10:01:34 2022 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 10:00:55 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 09:59:39 2022 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 09:59:14 2022 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 09:58:54 2022 Warning (5) Dynamic Range Window violation
Mon Oct 24 09:58:54 2022 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 09:58:40 2022 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 09:58:40 2022 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 09:58:19 2022 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 09:58:19 2022 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 09:58:09 2022 Warning (5) Dynamic Range Window violation
Mon Oct 24 09:58:09 2022 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 09:58:09 2022 Warning (5) Dynamic Range Window violation
Mon Oct 24 09:58:09 2022 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=80:cc:9c:af:f2:38;CMTS-MAC=3c:41:0e:1f:6a:b1;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 24 09:58:08 2022 Warning (5) Dynamic Range Window violation

2 Replies

Replies have been turned off for this discussion
  • CplJ's avatar
    CplJ
    New Contributor II

    I suspect it has to do with the weather changing. I’d get a technician out to see if they can isolate the errors (Forward error correction or FEC) as coming from within your home or from cox’s network outside. If it’s from outside, the weather shift may have caused some amplifiers to lose unity gain which will cause bit errors. 

    • Bruce's avatar
      Bruce
      Honored Contributor III

      According to one of our resident experts, Profile ID: 0 in your log is a problem and when your connection recovers, it remains Profile ID: 0.  You may have bursts of noise somewhere on the Cox network and its getting worst.

      Yes, a tech would be your best choice.