Internet speeds drops every few minutes to ~1Mbs download /.08 Mbs upload using the (C7000v2)

Question

Repost to the relevant forum.Heyo,&nbsp;I am using the C7000v2 router and for the past month the download/upload speeds has been very slow and inconsistent compared to before and would drop to near 0mbs every few minutes. If anyone has an solution it would be greatly appreciated. Here are my logs and stuff.Startup ProcedureProcedureStatusCommentAcquire Downstream Channel615000000 HzLockedConnectivity StateOKOperationalBoot StateOKOperationalSecurityEnabledBPI+IP Provisioning ModeHonor MDDhonorMdd(4)&nbsp;Downstream Bonded Channels (Partial Service)ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables1LockedQAM25636615000000 Hz-8.4 dBmV41.6 dB267314082Not LockedUnknown21525000000 Hz0.0 dBmV0.0 dB003Not LockedUnknown22531000000 Hz0.0 dBmV0.0 dB004Not LockedUnknown23537000000 Hz0.0 dBmV0.0 dB005Not LockedUnknown24543000000 Hz0.0 dBmV0.0 dB006Not LockedUnknown25549000000 Hz0.0 dBmV0.0 dB007LockedQAM25626555000000 Hz-11.1 dBmV31.9 dB1256085713050578LockedQAM25627561000000 Hz-9.2 dBmV29.2 dB40379511145629LockedQAM25628567000000 Hz-9.7 dBmV32.3 dB526712062923410LockedQAM25629573000000 Hz-11.9 dBmV31.5 dB76516332471711LockedQAM25630579000000 Hz-12 dBmV31.3 dB13570617243202412LockedQAM25631585000000 Hz-10.2 dBmV35.2 dB3995031094213LockedQAM25632591000000 Hz-8.5 dBmV31.6 dB263304222322014Not LockedUnknown33597000000 Hz0.0 dBmV0.0 dB0015Not LockedUnknown34603000000 Hz0.0 dBmV0.0 dB0016LockedQAM25635609000000 Hz-9.5 dBmV36.3 dB25322580817LockedQAM25637621000000 Hz-8.6 dBmV30.4 dB67061642718LockedQAM25638627000000 Hz-10.6 dBmV28.5 dB195346857719LockedQAM25639633000000 Hz-11 dBmV34.7 dB57141578620LockedQAM25640639000000 Hz-10.9 dBmV38.6 dB24681126321Not LockedUnknown41645000000 Hz0.0 dBmV0.0 dB0022Not LockedUnknown42651000000 Hz0.0 dBmV0.0 dB0023LockedQAM25643657000000 Hz-11.2 dBmV39.8 dB0024LockedQAM25644663000000 Hz-11.3 dBmV39.3 dB00&nbsp;Upstream Bonded Channels (Partial Service)ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower1LockedATDMA25120 Ksym/sec22800000 Hz54 dBmV2LockedATDMA15120 Ksym/sec16400000 Hz53.9 dBmV3Not LockedUnknown30 Ksym/sec29200000 Hz0.0 dBmV4Not LockedUnknown40 Ksym/sec35600000 Hz0.0 dBmV5Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV6Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV7Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV8Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV&nbsp;TimePriorityDescription2023-7-16, 22:49:18Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:49:04Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:49:04Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:47:41Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:37:25Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:36:13Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:25:48Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:24:42Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:14:36Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:14:26Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:14:25Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:13:11Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:02:57Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:02:51Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:02:45Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 22:01:40Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:51:16Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:50:10Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:40:00Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:39:56Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:39:44Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:38:37Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:28:15Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:27:07Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:17:14Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:16:50Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:16:49Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:16:43Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:15:37Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:05:22Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:05:14Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:05:12Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 21:04:07Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 20:54:03Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 20:53:59Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 20:53:55Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 20:53:48Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 20:53:45Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 20:53:44Critical (3)No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;2023-7-16, 20:53:44Warning (5)MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;&nbsp;&nbsp;

FURRYe38 · Answer

You have some channels that are not getting any signal and they should be.
The channels that are getting signal, the power is TOO LOW:
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
&nbsp;
Also see a ton of correctables and un-correctables that should be zeros.
Any Criticals, Errors or Warnings seen in the event logs page needs to be reviewed by the ISP and resolved by the ISP.
&nbsp;
Have the ISP check the signal and line quality UP to the modem.&nbsp;Be sure the ISP provisions the modem correctly.Be sure there are no coax cable line splitters in the between the modem and ISP service box.&nbsp;Be sure your using good quality RG6 coax cable up to the modem.&nbsp;Start with removing any amplifiers, signal attenuators, or splitters from the coax.From there check the line for kinks, damage, moisture in the line.Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.Be sure to power OFF the modem for 1 minute then back ON.https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.htmlhttps://highspeed.tips/docsis-events/

Forum Discussion

Internet speeds drops every few minutes to ~1Mbs download /.08 Mbs upload using the (C7000v2)

1 Reply

Time	Priority	Description
2023-7-16, 22:49:18	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:49:04	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:49:04	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:47:41	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:37:25	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:36:13	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:25:48	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:24:42	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:14:36	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:14:26	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:14:25	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:13:11	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:02:57	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:02:51	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:02:45	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 22:01:40	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:51:16	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:50:10	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:40:00	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:39:56	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:39:44	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:38:37	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:28:15	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:27:07	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:17:14	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:16:50	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:16:49	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:16:43	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:15:37	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:05:22	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:05:14	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:05:12	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 21:04:07	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 20:54:03	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 20:53:59	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 20:53:55	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 20:53:48	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 20:53:45	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 20:53:44	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;
2023-7-16, 20:53:44	Warning (5)	MDD message timeout;CM-MAC=14:59:c0:0a:70:c8;CMTS-MAC=00:90:f0:7e:01:00;CM-QOS=1.1;CM-VER=3.0;