NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi latency peaks every 10s
Hi, I've noticed that pinging the Orbi Router when connected to the satellite shows latency peaking every 10s, and lasts for about 3s. I'm hoping this isn't to be expected and something that ...
I see similar when I connect to the Router via wifi also:
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.304 ms 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.652 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.817 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.252 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=4.162 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=76.322 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.992 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=96.374 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.776 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=2.334 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=4.596 ms 64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=2.277 ms 64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=9.073 ms 64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=1.859 ms 64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=19.726 ms 64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1.696 ms 64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=4.143 ms 64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=12.565 ms 64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=37.218 ms 64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=107.542 ms 64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=62.228 ms 64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=2.990 ms 64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=0.985 ms 64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=2.310 ms 64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=1.149 ms 64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=2.073 ms 64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=1.936 ms 64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=3.625 ms 64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=2.067 ms 64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=2.030 ms 64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=4.240 ms 64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=2.331 ms 64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=77.865 ms 64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=25.668 ms 64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=1.954 ms
This is from the same MacBook Pro Retina (OSX 10.11.6) as the earlier test. I'll do some more wired/other client tests tomorrow and report back on what I find. Thanks for everyone's help.
pingles wrote:This is from the same MacBook Pro Retina (OSX 10.11.6) as the earlier test. I'll do some more wired/other client tests tomorrow and report back on what I find. Thanks for everyone's help.
I'm starting to wonder if its my Retina MacBook Pro. I noticed that if I have ping going I can make the response times skyrocket by simply clicking on the Wi-Fi icon in system menu bar. Whenever I click the icon I see the same three seconds of high latency