RBR20 lag spikes

Question

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 · Answer

What modem are you connected to?&nbsp;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?&nbsp;&nbsp;

wmickens · Answer

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 · Answer

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 · Answer

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:&nbsp;Reply from 192.168.1.1: bytes=32 time=7ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=11ms TTL=64Reply from 192.168.1.1: bytes=32 time=4ms TTL=64Reply from 192.168.1.1: bytes=32 time=7ms TTL=64Reply from 192.168.1.1: bytes=32 time=1067ms TTL=64Reply from 192.168.1.1: bytes=32 time=14ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=6ms TTL=64Reply from 192.168.1.1: bytes=32 time=4ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=6ms TTL=64Reply from 192.168.1.1: bytes=32 time=10ms TTL=64Reply from 192.168.1.1: bytes=32 time=5ms TTL=64Reply from 192.168.1.1: bytes=32 time=19ms TTL=64Reply from 192.168.1.1: bytes=32 time=8ms TTL=64Reply from 192.168.1.1: bytes=32 time=5ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=4ms TTL=64Reply from 192.168.1.1: bytes=32 time=19ms TTL=64Reply from 192.168.1.1: bytes=32 time=17ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=5ms TTL=64Reply from 192.168.1.1: bytes=32 time=6ms TTL=64Reply from 192.168.1.1: bytes=32 time=4ms TTL=64Reply from 192.168.1.1: bytes=32 time=25ms TTL=64Reply from 192.168.1.1: bytes=32 time=5ms TTL=64Reply from 192.168.1.1: bytes=32 time=5ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=4ms TTL=64Reply from 192.168.1.1: bytes=32 time=28ms TTL=64Reply from 192.168.1.1: bytes=32 time=4ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=13ms TTL=64Reply from 192.168.1.1: bytes=32 time=7ms TTL=64Reply from 192.168.1.1: bytes=32 time=3ms TTL=64Reply from 192.168.1.1: bytes=32 time=1ms TTL=64Reply from 192.168.1.1: bytes=32 time=9ms TTL=64Reply from 192.168.1.1: bytes=32 time=6ms TTL=64&nbsp;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&nbsp;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 · Answer

Are you doing these tests over wireless or wired?&nbsp;

Forum Discussion

RBR20 lag spikes

7 Replies