NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR20 lag spikes
This is very frustrating. I have an Orbi RBR20 that when I ping the router itself from two different machines (Linux and Windows) and a cell phone i get occasional lag spike that ranges from 60ms to ...
I'm having the same problems and it's driving me nuts. I just ran 100' of ethernet cable so the backhaul is wired now, I'm sitting 10 ft from my wireless access point, and I still get the same lag spikes (and timeouts), just pinging the router itself.
64 bytes from 192.168.177.1: icmp_seq=26 ttl=64 time=1.980 ms
64 bytes from 192.168.177.1: icmp_seq=27 ttl=64 time=1.858 ms
64 bytes from 192.168.177.1: icmp_seq=28 ttl=64 time=1.945 ms
64 bytes from 192.168.177.1: icmp_seq=29 ttl=64 time=1.242 ms
64 bytes from 192.168.177.1: icmp_seq=30 ttl=64 time=7.518 ms
64 bytes from 192.168.177.1: icmp_seq=31 ttl=64 time=1.654 ms
64 bytes from 192.168.177.1: icmp_seq=32 ttl=64 time=2.013 ms
64 bytes from 192.168.177.1: icmp_seq=33 ttl=64 time=3.644 ms
64 bytes from 192.168.177.1: icmp_seq=34 ttl=64 time=4.976 ms
64 bytes from 192.168.177.1: icmp_seq=35 ttl=64 time=2.309 ms
64 bytes from 192.168.177.1: icmp_seq=36 ttl=64 time=17.544 ms
64 bytes from 192.168.177.1: icmp_seq=37 ttl=64 time=2.398 ms
64 bytes from 192.168.177.1: icmp_seq=38 ttl=64 time=3.506 ms
64 bytes from 192.168.177.1: icmp_seq=39 ttl=64 time=9.223 ms
64 bytes from 192.168.177.1: icmp_seq=40 ttl=64 time=27.516 ms
64 bytes from 192.168.177.1: icmp_seq=41 ttl=64 time=69.829 ms
64 bytes from 192.168.177.1: icmp_seq=42 ttl=64 time=5.740 ms
64 bytes from 192.168.177.1: icmp_seq=43 ttl=64 time=171.762 ms
64 bytes from 192.168.177.1: icmp_seq=44 ttl=64 time=34.243 ms
64 bytes from 192.168.177.1: icmp_seq=45 ttl=64 time=4.469 ms
Request timeout for icmp_seq 46
Request timeout for icmp_seq 47
Request timeout for icmp_seq 48
Request timeout for icmp_seq 49
Request timeout for icmp_seq 50
Request timeout for icmp_seq 51
Request timeout for icmp_seq 52
Request timeout for icmp_seq 53
Request timeout for icmp_seq 54
Request timeout for icmp_seq 55
Request timeout for icmp_seq 56
Request timeout for icmp_seq 57
Request timeout for icmp_seq 58
Request timeout for icmp_seq 59
64 bytes from 192.168.177.1: icmp_seq=60 ttl=64 time=763.198 ms
64 bytes from 192.168.177.1: icmp_seq=61 ttl=64 time=60.923 ms
64 bytes from 192.168.177.1: icmp_seq=62 ttl=64 time=79.584 ms
64 bytes from 192.168.177.1: icmp_seq=63 ttl=64 time=112.959 ms
64 bytes from 192.168.177.1: icmp_seq=64 ttl=64 time=150.602 ms
64 bytes from 192.168.177.1: icmp_seq=65 ttl=64 time=4.830 ms
64 bytes from 192.168.177.1: icmp_seq=66 ttl=64 time=6.664 ms
64 bytes from 192.168.177.1: icmp_seq=67 ttl=64 time=7.855 ms
64 bytes from 192.168.177.1: icmp_seq=68 ttl=64 time=17.992 ms
64 bytes from 192.168.177.1: icmp_seq=69 ttl=64 time=6.075 ms
64 bytes from 192.168.177.1: icmp_seq=70 ttl=64 time=2.109 ms
64 bytes from 192.168.177.1: icmp_seq=71 ttl=64 time=5.273 ms
Try downgrading the firmware a version (or 2), factory reset and do a clean (not from backup) install. Disable auto-update.
Don't change anything from default other that whats needed to get online.
Then test ping.