cm500 keeps loosing connection

[Dexrngr]

I’ve had this router for 2+years. All of the sudden about 3 weeks ago I keep loosing my internet connection. Unplug for a minute then plug back in and it will work. Sometimes for days other times for 15 minutes then lose connection again. Any help?

[plemans · Accepted solution]

Please screen snip it. It's easier to read

[plemans]

A couple things I'd recommend. 

1. Include a screen snip of your modem connections page and your logs page. These are important to see how the signal is coming into your modem.

2. Remove any line splitters, amplifiers, attenuators, 90 degree elbows, worn cables, kinked cables, or extended runs. Inspect for loose connections or moisture within the coax lines. These causes many problems.  

[Dexrngr]

Starting Frequency

Startup Procedure Procedure Status Comment Acquire Downstream Channel 519000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD honorMdd(4)

Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 34 519000000 Hz -1.8 dBmV 39.7 dB 3111 3140 2 Locked QAM256 35 525000000 Hz -1.8 dBmV 39.6 dB 3024 4071 3 Locked QAM256 36 531000000 Hz -1.7 dBmV 39.6 dB 2702 5146 4 Locked QAM256 37 537000000 Hz -1.6 dBmV 39.5 dB 2629 4119 5 Locked QAM256 1 543000000 Hz -1.9 dBmV 39.4 dB 2509 3848 6 Locked QAM256 2 549000000 Hz -2.2 dBmV 39.5 dB 2651 3748 7 Locked QAM256 3 555000000 Hz -2.2 dBmV 39.5 dB 2498 4046 8 Locked QAM256 4 561000000 Hz -2.3 dBmV 39.5 dB 2602 3746 9 Locked QAM256 5 567000000 Hz -2.4 dBmV 39.6 dB 2502 3446 10 Locked QAM256 6 573000000 Hz -2.9 dBmV 33.8 dB 4589 3238 11 Locked QAM256 7 579000000 Hz -3.4 dBmV 36.5 dB 3119 2639 12 Locked QAM256 8 585000000 Hz -3.6 dBmV 39.1 dB 1964 2432 13 Locked QAM256 9 591000000 Hz -3.8 dBmV 38.9 dB 1985 2805 14 Locked QAM256 10 597000000 Hz -4.7 dBmV 38.7 dB 2191 3190 15 Locked QAM256 11 603000000 Hz -5.3 dBmV 38.5 dB 1489 2203 16 Locked QAM256 12 609000000 Hz -6 dBmV 38 dB 1623 2239

Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 5 5120 Ksym/sec 35800000 Hz 53 dBmV 2 Locked ATDMA 6 5120 Ksym/sec 29400000 Hz 53.5 dBmV 3 Locked ATDMA 7 5120 Ksym/sec 23000000 Hz 54 dBmV 4 Locked ATDMA 8 5120 Ksym/sec 16600000 Hz 54 dBmV

Extended Upstream Transmit Power Enable Extended Upstream Transmit Power

Current System Time:Mon Nov 04 18:12:05 2019 System Up Time:21:14:53

Time Priority Description 2019-11-4, 11:34:46 Notice (6) Honoring MDD; IP provisioning mode = IPv6 2019-11-4, 11:34:41 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.0;CM-VER=3.0; 2019-11-4, 11:34:31 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-4, 10:46:08 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-4, 08:37:07 Notice (6) Honoring MDD; IP provisioning mode = IPv6 2019-11-4, 08:36:43 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 21:04:05 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:29 Notice (6) Honoring MDD; IP provisioning mode = IPv6 1970-1-1, 00:00:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2019-11-3, 12:04:05 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 11:03:24 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 10:46:03 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 10:41:30 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 10:36:37 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 10:23:45 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 09:57:38 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 09:24:40 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 09:23:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.0;CM-VER=3.0; 2019-11-3, 09:23:36 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.0;CM-VER=3.0; 2019-11-3, 09:23:14 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.0;CM-VER=3.0; 2019-11-3, 09:18:49 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.0;CM-VER=3.0; 2019-11-3, 09:18:40 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:28:17 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:28:16 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:28:16 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:27:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:27:54 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:27:54 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:26:07 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:24:44 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:23:45 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:22:20 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:21:40 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:19:52 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:09:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 06:09:03 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 05:48:13 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.1;CM-VER=3.0; 2019-11-3, 05:24:04 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:f4:65:b8;CMTS-MAC=00:01:5c:96:08:4f;CM-QOS=1.0;CM-VER=3.0;

[plemans · Accepted solution]

Please screen snip it. It's easier to read

[Dexrngr]

i have to uplaod each snip as its own file? this is stupid and will take forever

[plemans]

Just do the connections page. Should be only 2-3 arty max. Most can get it on one

[Dexrngr]

1

[Dexrngr]

last 2 are the connections snips 

capture and capture 1

[plemans]

Way to many errors on your downstream and your upstream power is to hot.
Your ISP needs to check your lines. If you have splitters, amps, bad coax, 90 degree elbows, bad/loose connectors replace them. They can cause errors too.

[Dexrngr]

ok thank you.  im pretty sure i on a straight line from my outside connection.  which comes down to my wall jack and to my modem.

[Dexrngr]

what should my normal upstream and downstream look like?

[plemans]

This article goes through some basics.
https://pickmymodem.com/signal-levels-docsis-3-03-1-cable-modem/