NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi ping is awful
I have a new RBK853 system and my latency when pinging the router is just terrible. I see the same thing on multiple devices. 3-4ms pings with 80-120ms pings sprinkled in every couple seconds.
I can't imagine trying to play games on this network. It even happens when connected directly to the router and not a satellite (confirmed by the web UI).
I've done a lot of googling tonight, but nothing helpful has turned up. I've updated to the latest firmware (v3.2.16.6_1.4.4). Are there any actual fixes for this problem, or do I need to return the router and get something else?
4 Replies
I just tried connecting to a satellite and pinging it, it's even worse than the router.
PING 10.0.0.8 (10.0.0.8) 56(84) bytes of data. 64 bytes from 10.0.0.8: icmp_seq=1 ttl=64 time=5.76 ms 64 bytes from 10.0.0.8: icmp_seq=2 ttl=64 time=6.85 ms 64 bytes from 10.0.0.8: icmp_seq=3 ttl=64 time=5.96 ms 64 bytes from 10.0.0.8: icmp_seq=4 ttl=64 time=8.17 ms 64 bytes from 10.0.0.8: icmp_seq=5 ttl=64 time=67.9 ms 64 bytes from 10.0.0.8: icmp_seq=6 ttl=64 time=7.79 ms From 10.0.0.7 icmp_seq=7 Destination Host Unreachable From 10.0.0.7 icmp_seq=8 Destination Host Unreachable From 10.0.0.7 icmp_seq=9 Destination Host Unreachable From 10.0.0.7 icmp_seq=11 Destination Host Unreachable From 10.0.0.7 icmp_seq=12 Destination Host Unreachable From 10.0.0.7 icmp_seq=13 Destination Host Unreachable From 10.0.0.7 icmp_seq=14 Destination Host Unreachable From 10.0.0.7 icmp_seq=15 Destination Host Unreachable From 10.0.0.7 icmp_seq=16 Destination Host Unreachable 64 bytes from 10.0.0.8: icmp_seq=17 ttl=64 time=2087 ms 64 bytes from 10.0.0.8: icmp_seq=18 ttl=64 time=1064 ms 64 bytes from 10.0.0.8: icmp_seq=19 ttl=64 time=35.6 ms 64 bytes from 10.0.0.8: icmp_seq=20 ttl=64 time=2.59 ms 64 bytes from 10.0.0.8: icmp_seq=21 ttl=64 time=62.9 ms 64 bytes from 10.0.0.8: icmp_seq=22 ttl=64 time=3.18 ms 64 bytes from 10.0.0.8: icmp_seq=23 ttl=64 time=2.61 ms 64 bytes from 10.0.0.8: icmp_seq=24 ttl=64 time=22.9 ms 64 bytes from 10.0.0.8: icmp_seq=25 ttl=64 time=3.45 ms 64 bytes from 10.0.0.8: icmp_seq=26 ttl=64 time=0.676 ms 64 bytes from 10.0.0.8: icmp_seq=27 ttl=64 time=127 ms 64 bytes from 10.0.0.8: icmp_seq=28 ttl=64 time=72.8 ms 64 bytes from 10.0.0.8: icmp_seq=29 ttl=64 time=10.7 ms 64 bytes from 10.0.0.8: icmp_seq=30 ttl=64 time=3.46 ms 64 bytes from 10.0.0.8: icmp_seq=31 ttl=64 time=16.7 ms 64 bytes from 10.0.0.8: icmp_seq=32 ttl=64 time=126 ms
Coming from an ancient Linksys router that would consistently give 1ms pings, this $1000 mesh system is a huge disappointment.
Reasons why you may have bad pings:
Hardware issues, cable issues, WIFI interference, ISP issuesInternet connection speedFirewalls, especially if more than one used (example 3rd party and Windows built in)Distance between satellite and server
machrider wrote:I have a new RBK853 system and my latency when pinging the router is just terrible. I see the same thing on multiple devices. 3-4ms pings with 80-120ms pings sprinkled in every couple seconds.
I can't imagine trying to play games on this network. It even happens when connected directly to the router and not a satellite (confirmed by the web UI).
The connection to the router is over WiFi, correct?
machrider wrote:I have a new RBK853 system and my latency when pinging the router is just terrible. I see the same thing on multiple devices. 3-4ms pings with 80-120ms pings sprinkled in every couple seconds.
I just pinged my RBR50 (older, less powerful CPU) 500 times over WiFi using hrping (free). The results are
Fastest 1.294ms
Average 3.134ms
Slowest 9.483ms i.e. less than 1/100th of a second.
Supposing that there is 100ms latency from time-to-time. That is about 1/10th of a second. One would image that even veteran gamers would be tasked to respond (constantly) faster than 1/10th of a second. 3-4ms should be beyond anybody's capability.
WiFi is not nearly as efficient as ethernet. While I get a constant "under 1ms" response over ethernet, that never happens over WiFi. I suspect there is "something going on" in the RBK853 installation that is causing disruptions in WiFi performance.
