RBR20 lag spikes

[wmickens]

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 as high as 1200ms. Pinging local IP addresses when the router is no more than 20 feet away should not produce such lag spikes. I started noticing it more frequently when playing my online game and I would get a brief disconnect. It would reconnect but sometimes it would take a few seconds. Both PCs are connecting wirelessly and the Orbi has been rebooted numerous of times.

Not to mention sometimes the web interface is slow to load or even won't display at all (500 internal server error). Before I replace this and the satellite I have for extended coverage what can be done to correct this

[plemans]

What modem are you connected to? 

What firmware is on the router? And the satellite(s)?

Have you tried turning off the satellites and seeing if you get the ping spikes just running the router? 

[wmickens]

It is a Spectrum modem but I'm only pinging the internal IP address. 

Model Name	Device Name	Current Version	Status
Router	RBR20	RBR20	V2.5.1.16
Satellite	RBW30	Sat-one	V2.6.1.6

With just the router I was getting the same spikes.

Here is a snippet of the ping to the router:

Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=18ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=12ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=323ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=16ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64

Here is the stats of the ping I just ran:

Ping statistics for 192.168.1.1:
Packets: Sent = 579, Received = 579, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1796ms, Average = 33ms

[plemans]

If you're getting this with the satellite powered off, it isn't the satellite. 

have you tried a factory reset on the router? 

when you reinstall it, do a clean install (not from backup).

Make sure to leave traffic monitoring, access control, parental controls all disabled. 

[wmickens]

Did a factory reset and left all of the mentioned options disabled...yet I'm still having the same issues. In some cases it is even worse:

Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1067ms TTL=64
Reply from 192.168.1.1: bytes=32 time=14ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=17ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=25ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=28ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 1324, Received = 1217, Lost = 107 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1340ms, Average = 18ms

Not worried about the lost packets as the running ping was done while the router was being set up. The maximum should not be over 1300ms just for pinging the router internally.

[plemans]

Are you doing these tests over wireless or wired? 

[mlodick]

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

[plemans]

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.