NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bensmith
Nov 02, 2016Tutor
lag spike every 15-20 seconds on N450
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 Ti...
bensmith
Nov 02, 2016Tutor
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
- bensmithNov 03, 2016Tutor
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- OlebaNov 04, 2016Aspirant
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.
- kpesceNov 05, 2016Aspirant
Absolutely same thing happening here. Very frustrating. Thought it was WiFi related, but happens with wired connection as well.