DS Power Level Jumped Today - Time Warner Internet

#1
I've been monitoring my signals for over two weeks. By monitor, I mean I'm writing a program that monitors the CM's status page and logs it, so I got to see those stats continuously for a while now.

This morning, I noticed about a 7dBm jump in my receive levels, accompanied by high error rates. This evening, it is still this way, a snapshot of two 5-minute intervals:
Status as of Saturday, October 1, 2016, 19:05:39 (EST):

Downstream Channel | | Locked
Connectivity State | OK | Operational
Boot State | OK | Operational
Configuration File | OK |
Security | Enabled | BPI+
DOCSIS Net Access | Allowed |

SB6183-9.2.0.0-GA-03-29-NOSH DOCSIS 3.0 uptime is almost 8 hours.

5:17 | Locked | QAM256 | 555 | 38.4 | 9.4 | 697 | 0 | +71 | |
2:18 | Locked | QAM256 | 561 | 38.3 | 9.4 | 882 | 0 | +95 | |
3:19 | Locked | QAM256 | 567 | 38.1 | 9.4 | 1.0K| 0 | +96 | |
4:20 | Locked | QAM256 | 573 | 38.1 | 9.4 | 1.3K| 0 |+116 | |
1:21 | Locked | QAM256 | 579 | 38.2 | 9.7 | 1.2K| 0 |+104 | |
6:22 | Locked | QAM256 | 585 | 38.2 | 9.7 | 1.2K| 0 |+112 | |
7:23 | Locked | QAM256 | 591 | 38.5 | 10.3 | 906 | 0 | +72 | | HI
8:24 | Locked | QAM256 | 597 | 38.8 | 10.8 | 629 | 0 | +69 | | HI
9:25 | Locked | QAM256 | 603 | 39.2 | 11.5 | 349 | 0 | +32 | | HI
10:26 | Locked | QAM256 | 609 | 39.7 | 12.5 | 172 | 0 | +23 | | HI
11:27 | Locked | QAM256 | 615 | 39.7 | 12.7 | 140 | 32 | +16 | | HI
12:28 | Locked | QAM256 | 621 | 37.7 | 9.7 | 1.4K| 81 |+230 | |
13:29 | Locked | QAM256 | 627 | 36.2 | 7.4 | 14K| 40 |+1.5K| |
14:30 | Locked | QAM256 | 633 | 35.7 | 7.0 | 29K| 24 |+2.5K| |
15:31 | Locked | QAM256 | 639 | 35.5 | 6.9 | 37K| 0 |+3.0K| |
16:32 | Locked | QAM256 | 645 | 35.6 | 7.3 | 33K| 0 |+2.7K| |
Downstream Bonding Group power spread: 5.8 | 125K| 177 | +10K| |

4:1 | Locked | TDMA | 19.4 | 2560 | 37.5 | |
2:2 | Locked | ATDMA | 24.2 | 5120 | 37.5 | |
3:3 | Locked | ATDMA | 30.6 | 5120 | 37.8 | |
1:4 | Locked | ATDMA | 37.0 | 2560 | 36.5 | |

No new events logged since Saturday, October 1, 2016, 11:07:52.



Status as of Saturday, October 1, 2016, 19:10:48 (EST):

Downstream Channel | | Locked
Connectivity State | OK | Operational
Boot State | OK | Operational
Configuration File | OK |
Security | Enabled | BPI+
DOCSIS Net Access | Allowed |

SB6183-9.2.0.0-GA-03-29-NOSH DOCSIS 3.0 uptime is 8 hours.

5:17 | Locked | QAM256 | 555 | 38.6 | 9.2 | 766 | 0 | +69 | |
2:18 | Locked | QAM256 | 561 | 38.5 | 9.3 | 988 | 0 |+106 | |
3:19 | Locked | QAM256 | 567 | 38.4 | 9.2 | 1.1K| 0 |+111 | |
4:20 | Locked | QAM256 | 573 | 38.3 | 9.3 | 1.4K| 0 |+130 | |
1:21 | Locked | QAM256 | 579 | 38.4 | 9.5 | 1.3K| 0 |+123 | |
6:22 | Locked | QAM256 | 585 | 38.4 | 9.5 | 1.3K| 0 |+116 | |
7:23 | Locked | QAM256 | 591 | 38.7 | 10.1 | 981 | 0 | +75 | | HI
8:24 | Locked | QAM256 | 597 | 39.1 | 10.7 | 682 | 0 | +53 | | HI
9:25 | Locked | QAM256 | 603 | 39.4 | 11.3 | 380 | 0 | +31 | | HI
10:26 | Locked | QAM256 | 609 | 39.8 | 12.4 | 189 | 0 | +17 | | HI
11:27 | Locked | QAM256 | 615 | 39.9 | 12.6 | 150 | 32 | +10 | | HI
12:28 | Locked | QAM256 | 621 | 38.0 | 9.6 | 1.6K| 81 |+210 | |
13:29 | Locked | QAM256 | 627 | 36.4 | 7.3 | 16K| 40 |+1.4K| |
14:30 | Locked | QAM256 | 633 | 36.0 | 6.8 | 31K| 24 |+2.2K| |
15:31 | Locked | QAM256 | 639 | 35.8 | 6.7 | 40K| 0 |+2.8K| |
16:32 | Locked | QAM256 | 645 | 36.0 | 7.1 | 35K| 0 |+2.6K| |
Downstream Bonding Group power spread: 5.9 | 135K| 177 | +10K| |

4:1 | Locked | TDMA | 19.4 | 2560 | 37.5 | |
2:2 | Locked | ATDMA | 24.2 | 5120 | 37.5 | |
3:3 | Locked | ATDMA | 30.6 | 5120 | 37.8 | |
1:4 | Locked | ATDMA | 37.0 | 2560 | 36.5 | |

No new events logged since Saturday, October 1, 2016, 11:07:52.The short uptime is due to my rebooting the modem and checking the torque on the coax.
Contrast this with a snapshot two days ago, 5 hrs after a reboot, same time:
Status as of Thursday, September 29, 2016, 19:11:34 (EST):

Downstream Channel | | Locked
Connectivity State | OK | Operational
Boot State | OK | Operational
Configuration File | OK |
Security | Enabled | BPI+
DOCSIS Net Access | Allowed |

SB6183-9.2.0.0-GA-03-29-NOSH DOCSIS 3.0 uptime is over 5 hours.

5:17 | Locked | QAM256 | 555 | 40.2 | 3.0 | 0 | 0 | | |
2:18 | Locked | QAM256 | 561 | 40.2 | 3.1 | 0 | 0 | | |
3:19 | Locked | QAM256 | 567 | 40.2 | 3.2 | 0 | 0 | | |
4:20 | Locked | QAM256 | 573 | 40.3 | 3.4 | 0 | 0 | | |
1:21 | Locked | QAM256 | 579 | 40.5 | 3.7 | 0 | 0 | | |
6:22 | Locked | QAM256 | 585 | 40.4 | 3.7 | 0 | 0 | | |
7:23 | Locked | QAM256 | 591 | 40.6 | 4.2 | 0 | 0 | | |
8:24 | Locked | QAM256 | 597 | 40.6 | 4.4 | 0 | 0 | | |
9:25 | Locked | QAM256 | 603 | 40.4 | 4.6 | 0 | 0 | | |
10:26 | Locked | QAM256 | 609 | 40.2 | 4.3 | 0 | 0 | | |
11:27 | Locked | QAM256 | 615 | 40.0 | 4.1 | 0 | 0 | | |
12:28 | Locked | QAM256 | 621 | 39.7 | 3.5 | 0 | 0 | | |
13:29 | Locked | QAM256 | 627 | 39.4 | 2.9 | 0 | 0 | | |
14:30 | Locked | QAM256 | 633 | 39.2 | 2.3 | 0 | 0 | | |
15:31 | Locked | QAM256 | 639 | 38.7 | 1.6 | 0 | 0 | | |
16:32 | Locked | QAM256 | 645 | 38.7 | 1.2 | 0 | 0 | | |
Downstream Bonding Group power spread: 3.4 | |

4:1 | Locked | TDMA | 19.4 | 2560 | 37.3 | |
2:2 | Locked | ATDMA | 24.2 | 5120 | 37.0 | |
3:3 | Locked | ATDMA | 30.6 | 5120 | 36.5 | |
1:4 | Locked | ATDMA | 37.0 | 2560 | 36.3 | |

Since Thursday, September 29, 2016, 13:55:48, optimal uptime is 5 hours, 15 minutes.



I have one cable run from the modem to the barrel connector outside, where the connection there goes to the pole.

The barrel connector is enclosed in a box, is horizontal, has drip loops, is properly torqued, and has dielectric grease on the threads (as of a week ago).

All three connectors are in great shape, stingers are shiny and proper length.

All contact surfaces are clean with no corrosion or tarnishing.

What could cause this change?

Is there a way for me to look at work being done in my area that may affect me?
[Note that my response to "Call support" will be 1) the point of this was to avoid calling support on a non-trouble and 2) "Is there a way I can verify what support tells me about work/no work being done in my area/region?"]

Thanks in advance.
 
Top