Community Forum

Internet T3 drops and modem rebooting.

New Poster

Internet T3 drops and modem rebooting.

I'm having serious issues with my cable modem recently.  Its dropping out about 5-6 times a day and takes a few minutes to reboot.  At first I thought it was my modem, which is a netgear cm600, so I switched it to my other modem an Arris sb6183.  The same thing is happening on two different modems.  I've already had 5 technicians and 1 supervisor come out changing various splitters and cables etc and i'm still stuck with this same issue.  I've had service with comcast since 2008 with pretty much zero issues.  I'm starting to think it has nothing to do with my house.   Here is my modem log and status

 

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel   Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK  
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed  

 

 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 32 585000000 Hz 2.6 dBmV 41.4 dB 8 0
2 Locked QAM256 33 591000000 Hz 2.5 dBmV 41.2 dB 3 0
3 Locked QAM256 34 597000000 Hz 2.1 dBmV 40.9 dB 12 0
4 Locked QAM256 35 603000000 Hz 2.1 dBmV 40.8 dB 6 0
5 Locked QAM256 36 609000000 Hz 1.9 dBmV 40.8 dB 8 0
6 Locked QAM256 37 615000000 Hz 1.9 dBmV 40.6 dB 7 0
7 Locked QAM256 38 621000000 Hz 1.4 dBmV 40.5 dB 17 0
8 Locked QAM256 39 627000000 Hz 1.0 dBmV 40.3 dB 15 0
9 Locked QAM256 40 633000000 Hz 0.7 dBmV 40.2 dB 12 0
10 Locked QAM256 41 639000000 Hz 0.5 dBmV 40.1 dB 14 0
11 Locked QAM256 42 645000000 Hz 0.3 dBmV 40.1 dB 17 0
12 Locked QAM256 43 651000000 Hz -0.6 dBmV 39.9 dB 26 0
13 Locked QAM256 44 657000000 Hz -1.1 dBmV 39.6 dB 24 0
14 Locked QAM256 45 663000000 Hz -1.8 dBmV 39.3 dB 28 0
15 Locked QAM256 46 669000000 Hz -2.1 dBmV 39.2 dB 18 0
16 Locked QAM256 47 675000000 Hz -3.0 dBmV 38.5 dB 23 0

 

 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 5 5120 Ksym/sec 36100000 Hz 51.5 dBmV
2 Locked ATDMA 6 5120 Ksym/sec 29600000 Hz 53.8 dBmV
3 Locked ATDMA 7 5120 Ksym/sec 23000000 Hz 54.0 dBmV
4 Locked ATDMA 8 5120 Ksym/sec 16500000 Hz 54.0 dBmV



 

Current System Time: Wed Aug 21 19:28:16 2019

 

Time Priority Description
Tue Aug 20 00:31:45 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:31:45 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:31:45 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:32:47 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:32:47 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:32:47 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:33:16 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:33:16 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:33:16 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:40:00 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:40:00 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:40:00 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 00:40:25 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 07:53:18 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 07:54:43 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 08:27:18 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 08:28:04 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 08:28:26 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 08:29:00 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 08:29:03 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 08:58:11 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 08:58:36 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 09:01:36 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 09:02:01 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 09:02:43 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 09:03:09 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 09:27:58 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 09:27:59 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 09:28:28 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 09:28:30 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 09:30:28 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 09:31:33 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 09:31:34 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 10:55:59 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 10:56:01 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 10:56:40 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 10:56:41 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 10:57:36 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 10:57:42 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 10:59:30 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 11:00:56 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 11:01:02 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 11:01:55 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 16:05:55 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 16:27:37 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 16:27:37 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 16:27:37 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 16:27:59 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 16:27:59 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 16:27:59 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 16:28:17 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 16:28:17 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 16:28:17 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Tue Aug 20 16:28:26 2019 Critical (3) No Ranging Response received - T3 time-out
Wed Aug 21 09:50:30 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 09:50:30 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 09:50:30 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 10:15:39 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 10:15:39 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 10:15:39 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 10:16:06 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 10:16:06 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 10:16:06 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 12:24:39 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 12:24:39 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 12:24:39 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 13:12:36 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 13:12:36 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 13:12:36 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 14:49:12 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 14:53:32 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 15:57:11 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Wed Aug 21 16:01:31 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Wed Aug 21 18:34:09 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e4:95:17;CMTS-MAC=00:01:5c:9e:78:62;CM-QOS=1.1;CM-VER=3.0;

 
 
 

 

 

 

 

Expert

Re: Internet T3 drops and modem rebooting.

The upstream power is on the high side and it may be intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, and latency problems.

In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, 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 get the techs reinvolved until it is fixed properly.

 

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 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.




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!
New Poster

Re: Internet T3 drops and modem rebooting.

Well the technician came and replaced the amplifer in the attic.  He said its the cause of the higher upstream power levels.  This was also recently installed by the first tech that came out about a month ago.  Is there any chance that heat is main issue cause of these issues?  It just seems like there are quite a few posts regarding similar issues in these summer months.

Highlighted
Expert

Re: Internet T3 drops and modem rebooting.

Sure it's possible. Heat is an enemy to electronics !! So what do the stats look like now ,


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!
New Poster

Re: Internet T3 drops and modem rebooting.

Back in range again.

 

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 22 525000000 Hz 2.9 dBmV 40.3 dB 0 0
2 Locked QAM256 23 531000000 Hz 3.0 dBmV 40.3 dB 0 0
3 Locked QAM256 24 537000000 Hz 2.8 dBmV 40.2 dB 0 0
4 Locked QAM256 25 543000000 Hz 2.6 dBmV 40.1 dB 0 0
5 Locked QAM256 26 549000000 Hz 2.7 dBmV 40.1 dB 0 0
6 Locked QAM256 27 555000000 Hz 2.9 dBmV 40.1 dB 0 0
7 Locked QAM256 28 561000000 Hz 2.7 dBmV 40.1 dB 0 0
8 Locked QAM256 29 567000000 Hz 2.5 dBmV 40.0 dB 0 0
9 Locked QAM256 30 573000000 Hz 2.6 dBmV 39.9 dB 0 0
10 Locked QAM256 31 579000000 Hz 2.5 dBmV 39.9 dB 0 0
11 Locked QAM256 32 585000000 Hz 2.3 dBmV 39.8 dB 0 0
12 Locked QAM256 33 591000000 Hz 2.0 dBmV 39.7 dB 0 0
13 Locked QAM256 34 597000000 Hz 1.7 dBmV 39.5 dB 0 0
14 Locked QAM256 35 603000000 Hz 1.7 dBmV 39.5 dB 0 0
15 Locked QAM256 36 609000000 Hz 1.4 dBmV 39.4 dB 0 0
16 Locked QAM256 37 615000000 Hz 1.1 dBmV 39.2 dB 0 0

 

 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 5 5120 Ksym/sec 36100000 Hz 35.3 dBmV
2 Locked ATDMA 6 5120 Ksym/sec 29600000 Hz 35.0 dBmV
3 Locked ATDMA 7 5120 Ksym/sec 23000000 Hz 34.8 dBmV
4 Locked ATDMA 8 5120 Ksym/sec 16500000 Hz 34.5 dBmV



 

Current System Time: Thu Aug 22 20:21:04 2019