NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
N450 WiFi keeps disconnecting
Hello, So I bought my Netgear N450 WiFi cable modem router on April 30, 2015 and in the past month I've been having WiFi connection problems. The internet works just fine, but for some reason the...
Hello,
This issue is happening to me too, have N450 and I'm a TWC customer
This is affecting all conectivity in the modem (wired and wifi).
This happend after someone (TWC or Netgear) pushed firmware 3.01.06
and it started about 10 days ago
Try to reset the modem and initiate a constant ping 'ping XXX.XXX.XXX.XXX -t'
After reset you should see regular latency numbers, as time goes by you will notice
that every 16 packet, the latency is much higher, if you leave the modem without restarting
for more then a day you might see 3000+ ms latency for something that is usually 30+ ms
Here is a constant ping to one of the servers (about 8 hours after restarting the modem) :
Reply from 24.93.40.116: bytes=32 time=31ms TTL=247
Reply from 24.93.40.116: bytes=32 time=46ms TTL=247
Reply from 24.93.40.116: bytes=32 time=29ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=69ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=45ms TTL=247
Reply from 24.93.40.116: bytes=32 time=32ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=56ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1361ms TTL=247
Reply from 24.93.40.116: bytes=32 time=26ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=31ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=31ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=40ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=29ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1293ms TTL=247
Reply from 24.93.40.116: bytes=32 time=46ms TTL=247
Reply from 24.93.40.116: bytes=32 time=43ms TTL=247
Reply from 24.93.40.116: bytes=32 time=42ms TTL=247
Reply from 24.93.40.116: bytes=32 time=26ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=31ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=29ms TTL=247
Reply from 24.93.40.116: bytes=32 time=26ms TTL=247
Reply from 24.93.40.116: bytes=32 time=38ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1304ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=52ms TTL=247
Reply from 24.93.40.116: bytes=32 time=43ms TTL=247
Reply from 24.93.40.116: bytes=32 time=29ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=17ms TTL=247
Reply from 24.93.40.116: bytes=32 time=44ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1386ms TTL=247
Reply from 24.93.40.116: bytes=32 time=94ms TTL=247
Reply from 24.93.40.116: bytes=32 time=62ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=32ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=17ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=17ms TTL=247
Reply from 24.93.40.116: bytes=32 time=27ms TTL=247
Reply from 24.93.40.116: bytes=32 time=18ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1570ms TTL=247
Reply from 24.93.40.116: bytes=32 time=38ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=26ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=27ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=75ms TTL=247
Reply from 24.93.40.116: bytes=32 time=51ms TTL=247
Reply from 24.93.40.116: bytes=32 time=36ms TTL=247
Reply from 24.93.40.116: bytes=32 time=20ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1383ms TTL=247
Reply from 24.93.40.116: bytes=32 time=28ms TTL=247
Reply from 24.93.40.116: bytes=32 time=41ms TTL=247
Reply from 24.93.40.116: bytes=32 time=30ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=18ms TTL=247
Reply from 24.93.40.116: bytes=32 time=28ms TTL=247
Reply from 24.93.40.116: bytes=32 time=70ms TTL=247
Reply from 24.93.40.116: bytes=32 time=22ms TTL=247
Reply from 24.93.40.116: bytes=32 time=17ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=23ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=27ms TTL=247
Reply from 24.93.40.116: bytes=32 time=1562ms TTL=247
Reply from 24.93.40.116: bytes=32 time=21ms TTL=247
Reply from 24.93.40.116: bytes=32 time=27ms TTL=247
Reply from 24.93.40.116: bytes=32 time=24ms TTL=247
Reply from 24.93.40.116: bytes=32 time=25ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
Reply from 24.93.40.116: bytes=32 time=19ms TTL=247
EXACTLY every 16 packets there is a much bigger latency.
Smells like a software issue.
I started seeing messages about this at the end of last month, probably someone initiated
this push, but I see that this issue has been going on for months from the posts here.
TWC says they don't push firmware updates to customer modems, and Netgear says
only TWC can push the firmware
TWC and NETGEAR - stop blaiming each other, take responsibility and fix this issue !!!
Folks, I suggest that if you want this resolved, start making noise in both companies.
Totally agree with you, we need to make more noise to be heard...
Btw, here is the so called "tier 3" tech support number of TWC: 718-358-0900
One of their excuse was: if we pushed out wrong firmware we should have seen many complaints now...
I came here looking for help because I have had the same issue. We have had the N450 just over a year and it worked fine until about a month ago. Then the wireless started becoming a problem. Computers were connected but had no internet and the only solution was to restart the N450. This happeded every few days. The past 3 days, the speed has been horrible. The disconects are getting worse. I see that this is a issue for many others and the blame is being tossed around. I chose Netgear because I have been satisfied with Netgear products in the past, but it looks like it's time to abandon Netagear and look elsewhere. One of my roomates works from home and this just will not do. We need a solution.
After installing the third N450, it has now gone six months without losing wifi connectivity. I suspect a major batch came out with hardware faults and sympathize with those of you whose problem didn't occur until after the warranty expired. If you are one of those, I suggest you try a new and different model if you can afford it. Until you get one without the fault, the problem recurrs despite all other efforts on yours, Netgear tech support or your isp's part to fix it. If my modem/router starts doing it again, I will not hesitate to shop for a new one, not an N450.