Sporadic High Ping Times and Even Packet Loss when using WiFi

[dietkinnie]

So I've had this router for quite some time now and its been working flawelssley for normal day-to-day workloads, ex: reading emails, browsing the web, streaming content online etc. However, after purchasing a game and trying to play online I've realised that this Nightehawk D7000 router/modem is unable to deliver a reliable service enen though its marketed to do so.  (Using my ISP Router actually resulted in better overall results)

Below is a ping from my Mac to the Routers Default Gateway using a Wired Connection, as you can see the ping times are stable and are at acceptable elvels.

$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.956 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.843 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.964 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.973 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.971 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.973 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=1.031 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=0.995 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.850 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=1.025 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=0.982 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=1.024 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=0.976 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=0.916 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=0.979 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=0.980 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=0.942 ms

However, the below ping results (using Wifi) are really alarming. Same Mac Laptop, practically located alongside the D7000 device and pinging the Routers default Gateway:

PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=53.197 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=120.464 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=489.218 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=440.806 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=480.331 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=661.044 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=67.691 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=124.872 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=193.450 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=1.206 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=2.769 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=2.235 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=2.732 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=1.278 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=2.702 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=377.972 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=5.355 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=556.979 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=324.584 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=2.162 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=1.609 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=2.206 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=2.795 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=1.528 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=1.141 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=254.306 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=432.283 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=198.975 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=737.982 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=26.613 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=1.280 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=1.183 ms

As can be seen from the above, the ping times fluctuate drastically and make online game play impossible due to the added latency. Regardless though, this clearly indicates that the D7000 device is unable to deliever a reliable WiFI service on both 2G and 5G bands.

I've also read online that it would be worth Factory Resetting the device, which I have done and also ran an PING to its default GW IP right after resetting the device. (So without any other configuration setting in place).  Guess what? Same output, so the factory reset did not help in any way. I have also tried upgrading to the lastest Firmware, downgrading to multiple versions however sporadic high ping times and latency still persist.

I would greatly appreciate some help/advice since I've run out of options and after spending quite a bit of money on this device, really expected better.

[antinode]

> [...] this Nightehawk D7000 [...]

   Plain/"v1" "D7000", or "D7000v2"?  Firmware version?

> [...] the D7000 device is unable to deliever a reliable WiFI service
> on both 2G and 5G bands.

   A wireless connection is inherently less reliable than a wired
connection.  Radio interference is one of the differences.

> [...] (Using my ISP Router actually resulted in better overall
> results)

   Not a very detailed description of that device, its configuration, or
the "better overall results".

> I've also read online [...]

   I saw it (somewhere) on the Internet, so it must be true?  A settings
reset can resolve some problems which are related to bad/corrupt
settings.  There are other classes of problems.

> [...] expected better.

   Perhaps so, but that, by itself, doesn't mean much.  (I, for example,
expect people with router questions to reveal their model numbers and
firmware versions.  I'm often disappointed.)

   Have you tried different radio channels?  Which channel(s) was your
(unspecified) "my ISP Router" using?  I gather that there are programs
out there which will scan the local radio channels and provide a report
on how busy each one is.  That might be informative.

[dietkinnie]

Hi thanks for your reply. I've left some comments inline below.

- Plain/"v1" "D7000", or "D7000v2"?  Firmware version?
Yes it's the Plain/"V1" "D7000" and currently running on the most recent Firmware Version V1.0.1.64_1.0.1 althout I had also downgraded to D7000_FW_V1.0.1.48_1.0.1 and D7000_FW_V1.0.1.44_1.0.1 to test, factory reset and applied setting manually. Each time experiencing the same results.

- A wireless connection is inherently less reliable than a wired connection.  Radio interference is one of the differences.

I agree with you here, and as I mentioned the Device is doing a good job for normal workloads. However when used for low latency purposes, it's horrible. When using my ISP's modem with in-built Wifi, I get much better performance overall and latency is much better when pining the ISP router default GW and also external resources such as 1.1.1.1

- Not a very detailed description of that device, its configuration, or the "better overall results".

As stated above, the latency issues are not experienced when using its In-Built wifi functionality provided with my ISP's router, even from further away. The reason why I opted pfor the D7000 series  router was for better overall coverage and the "Guest Network" functionalitiy.


- I saw it (somewhere) on the Internet, so it must be true?  A settings reset can resolve some problems which are related to bad/corruptsettings.  There are other classes of problems.
 
I'm not an expert and have utilised a lot of my time trying to find a solution before coming to the community and asking for help and raising my concerns. Clearly there are other individuals experiencing similar issues and there is no clear cut solution.  https://community.netgear.com/t5/DSL-Modems-Routers/Nighthawk-AC1900-Model-D7000-Intermittent-high-p... and https://community.netgear.com/t5/DSL-Modems-Routers/Nighthawk-D7000-2-4Ghz-WiFi-issues/td-p/1439984/... amongst otheres.


- Perhaps so, but that, by itself, doesn't mean much.  (I, for example, expect people with router questions to reveal their model numbers and firmware versions.  I'm often disappointed.)

You are correct and apologies for not providning all the required details. However, my lack of adding information has nothing to do with the letdown of this device, which is marketed till today as "Get today's fastest available speeds with the NETGEAR AC1900 WiFi Nighthawk VDSL/ADSL Modem Router. Enjoy the ultimate in WiFi speeds up to 1.9Gbps and a powerful dual core processor for extreme performance. High-powered amplifiers, external antennas and Beamforming+ improve range and reliability. Nighthawk supports ADSL/ADSL2/ADSL2+ and VDSL/VDSL2. Using Amazon Alexa™, control your home network with voice commands."  Source: https://www.netgear.com/home/products/networking/dsl-modems-routers/D7000.aspx

When I compare the reliability provided by my ISP router (which is Free) compared to the D7000 which i paid for, then I'm sure you can understand why I feel this way and clearly expect better.

- Have you tried different radio channels?  Which channel(s) was your
(unspecified) "my ISP Router" using?  I gather that there are programs
out there which will scan the local radio channels and provide a report
on how busy each one is.  That might be informative.

I have tried different channels on 2G being 5,6 and 11 the latter is the same channel used by my ISP device

On the 5G band I'm currently using 44 but also tried 48 and 116(DFS) and the results were identical.

[dietkinnie]

Actually after upgrading to V1.0.1.64_1.0.1  yesterday, I am now  experiencing even worse reliability issues. So far I experienced 3 Drops in Wifi 2 x  on 5G and 1 x on 2G bands, which require me to re-establish the wifi connections for all "previously" connected divices.

[tominwi]

My own D7000v1 has serious lockup problems with .64 so I downgraded to .60, but still had daily lockups.

I found with .60 that by turning Beamforming off I now at least have not had to reboot my D7000 in 5 days.

Suggesting, because it's easy to try, that you turn-off Beamforming and see if your results improve, as (to me at least) there are some serious bugs with it.