Re: lag spike every 15-20 seconds on N450

bensmith · ‎2016-11-02

Been chasing a networking problem I've been having for about 2 weeks now and think I have it narrowed down to the cable modem/router/switch, an N450, firmware version 3.01.06. I have service with Time Warner/Spectrum. After the device has been running for a few hours, every 15 to 20 seconds there's a lag spike. It helps for a while if I power cycle the device, as the lag spikes do not appear again until an hour or more has passed. I thought it was the connection to the Internet, but this morning I checked the LAN and saw the problem there. I also have to try several times before I can log into the web interface of the device.

I saw some errors in the event log that I thought might be related, so I had a Time Warner tech come out, and he reported that the line was in great shape.

I tried disconnecting everything except one device. Didn't help. Not seeing any viruses on my LAN either.

What could the problem be? Maybe it is overheating? But the device is well ventilated. And the spikes are too regular. Still, next thing I'll try is blowing out some dust. A change in configuration? But I haven't made any changes for months. Overfilled logs? Maybe new firmware that's buggy? I thought I might update the firmware, but seems that's out of my hands. According to the docs, the ISP does firmware updates automatically.

Pinging the LAN, from a PC connected via Ethernet:

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=47.8 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=16.3 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=16.6 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=40.3 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=21.7 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=16.7 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=1947 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=943 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=152 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=16.5 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=19.0 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=19.9 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=18.4 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=16.6 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=20.0 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=20.0 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=16.4 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=19.7 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=37.6 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=37.6 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=16.7 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=16.8 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=16.6 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=2203 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=1198 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=194 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=16.2 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=18.9 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=16.3 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=18.4 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=17.0 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=20.2 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=16.4 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=16.5 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=16.8 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=19.0 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=16.6 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=16.6 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=16.6 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=20.2 ms
64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=2707 ms
64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=1711 ms
64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=715 ms
64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=75.5 ms
64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=20.0 ms
64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=18.8 ms
64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=16.5 ms
64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=39.3 ms

Event log, with MAC addresses blotted out:

2016-11-01, 16:11:19.0 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-11-01, 16:11:19.0 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-11-01, 09:52:47.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:52:41.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:52:40.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:52:38.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:52:37.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:52:36.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:52:36.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:42:40.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-11-01, 09:42:39.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-11-01, 09:40:20.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:40:16.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:40:15.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:39:15.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:38:26.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-11-01, 09:37:19.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-11-01, 09:37:15.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-11-01, 09:37:15.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-11-01, 09:37:07.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-11-01, 05:24:50.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-10-31, 23:48:07.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-10-31, 23:47:40.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-10-31, 23:47:40.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-10-31, 23:47:32.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=1x:xx:xx:xx:xx:xx;CMTS-MAC=2x:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2016-10-31, 09:32:22.0 Critical (3) Resetting the cable modem due to docsDevResetNow

bensmith · ‎2016-11-02

After power cycling the devuce, these are my ping times:

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=8.39 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.66 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.78 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2.39 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=2.62 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=2.72 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=2.55 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=2.45 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=2.58 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=4.60 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=2.63 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=2.72 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=2.56 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=2.89 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=2.59 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=2.67 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=2.75 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=4.97 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=5.25 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=5.08 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=2.51 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=2.55 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=2.58 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=2.69 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=2.68 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=2.76 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=2.62 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=5.72 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=3.05 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=2.73 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=2.93 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=2.97 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=2.80 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=4.81 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=2.62 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=2.51 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=2.50 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=2.71 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=2.94 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=3.06 ms
64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=2.74 ms
64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=2.66 ms
64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=2.59 ms
64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=2.73 ms
64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=2.84 ms
64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=2.96 ms

bensmith · ‎2016-11-03

Interesting... ping times slowly degrade. After 12 hours, this is what I get:

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=22.0 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=25.3 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=24.8 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=22.3 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=32.3 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=21.9 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=22.3 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=95.3 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=3582 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=2583 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=1592 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=597 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=21.8 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=21.9 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=21.3 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=24.0 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=22.0 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=28.4 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=28.2 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=79.6 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=23.5 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=22.7 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=22.5 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=22.5 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=23.0 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=36.5 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=68.1 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=3346 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=2344 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=1341 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=338 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=22.3 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=21.9 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=22.3 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=40.1 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=22.5 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=24.2 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=22.1 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=22.0 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=22.0 ms
64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=22.0 ms
64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=21.6 ms
64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=22.1 ms
64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=27.6 ms
64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=22.1 ms
64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=3973 ms
64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=2970 ms
64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=1967 ms
64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=963 ms
64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=498 ms
64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=21.5 ms

Oleba · ‎2016-11-03

I came here for the exact same problem starting about 12 days ago. I am on TWC and every few hours my connection just drops. After about 5 minutes the router/modem will reboot itself and everything will be fine for a few hours.

Have not found the trigger but it appears the router stops traffic/responding. Have noticed I cannot even connect to the router during it via 192.

Same router. I first noticed it on I think a Monday night when my internet had degraded from 200mb service down to 9. I reset the modem/router and have had the issue every since.

TWC sees the connection drops and cleared the signal and all the power/snr/signal is fine. A reset on their end did nothing for it.

kpesce · ‎2016-11-05

Absolutely same thing happening here. Very frustrating. Thought it was WiFi related, but happens with wired connection as well.

Mydogsdad · ‎2016-11-06

I am having the same problem. I am on a grandfathered TWC plan with owned gateway. My problems started when Spectrum "upgraded" speeds from the standard 50 Mbps. Netgear site shows firmware version to be pushed by ISP (TWC) for this modem as v1.00.05. My equipment has v3.01.06 (which Netgear shows used by Comcast). I can't get anyone at Spectrum/TWC to even understand and acknowledge that ISP pushes firmware (even for customer-owned modems). It is supposedly escalated to engineering to confirm firmware version Spectrum/TWC should be pushing for my grandfathered TWC plan and this gateway. I suspect the problem lies with less than smooth transition from TWC to Spectrum/TWC.

Hoping for an answer to the problem here.

Offguys · ‎2016-11-14

I have had the same issue for the exact same amount of time. Massive spikes about every 10-15 seconds. I contacted time warner and they didn't help at all. Please keep this thread updated, I would love to see if someone comes up with a solution. This has been the biggest pain for me since I do a lot of online gaming.

DarrenM · ‎2016-11-16

Hello Offguys

Are your Seeing T3 and T4 timeouts in your logs when you are getting these spikes? If so this is related to a line issue with your ISP.

DarrenM

DeutschFace · ‎2016-11-17

It isnt related to a line issue with the ISP. It is a problem with the new firmware that was pushed to the modem/router.

https://community.netgear.com/t5/Cable-Modems-Routers/N450-CG3000Dv2-WiFi-drop-and-Interface-Lockup/...

Lot's of people (myself included) are having this same issue.

TWC blames netgear, netgear blames TWC, and I will never buy another netgear product.

DarrenM · ‎2016-11-21

Hello DeutschFace

Have you tried to factory reset the modem like others in the thread said it fixed the issue?

DarrenM

Scuttlebutt · ‎2016-11-26

I literally am having this exact issue. Model n450, firmware version 3.01.06, wired connection. TWC blames netgear, netgear blames TWC, but based on the amount of posts of people having this exact problem it's obvious that the issue is Netgear.

The ping is great then once every 20 seconds a massive spike occurs. I have to restart the modem to get the spikes to stop, and after about 1 hour they come back again. So frustrating, please help.

dmcguy · ‎2017-03-25

Apparently NetGear doesn't care. Been having this same problem for months and have come to the conclusion that the only solution is to buy another product and then never but an NetGear poduct again and spread the word that the N450 is a defective product.