NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

pingles's avatar
pingles
Aspirant
Jan 03, 2017

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 ...
Troubleshooting
MarkC1024's avatar
MarkC1024
Luminary
Jan 03, 2017

I just did a test from my laptop connected to satellite via ethernet, not showing the same and actually very good and stable:

Pinging 192.168.1.1 with 32 bytes of data
Reply from 192.168.1.1: bytes=32 time=2ms 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=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms 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=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms 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=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms 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=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms 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=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=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=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms 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=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms 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=2ms 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=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms 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=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms 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=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=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=2ms TTL=64

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

 

  • MarkC1024's avatar
    MarkC1024
    Luminary
    Jan 03, 2017

    Disconnected ethernet and using Wi-Fi there is a lag at about 26 seconds, but overall not as bad as what you are getting.

     

    Pinging 192.168.1.1 with 32 bytes of data
    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=4ms 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=4ms 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=2ms 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=5ms 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=7ms 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=6ms 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=3ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=31ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=46ms 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=4ms 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=4ms 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=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=4ms 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=5ms 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=4ms 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=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=4ms 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=5ms 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=4ms 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=4ms TTL=64

    • MarkC1024's avatar
      MarkC1024
      Luminary
      Jan 03, 2017

      Ran via Wi-Fi one more time and this time clean.  I'd suspect you have something else going one:

       

      Pinging 192.168.1.1 with 32 bytes of data
      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=6ms 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=5ms 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=5ms 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=4ms 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=4ms 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=7ms 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=4ms TTL=64
      Reply from 192.168.1.1: bytes=32 time=6ms 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=9ms 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=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=4ms 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=5ms 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=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=4ms 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=4ms 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=4ms 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=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=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

      Ping statistics for 192.168.1.1:
          Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
          Minimum = 3ms, Maximum = 9ms, Average = 4ms

      • MarkC1024's avatar
        MarkC1024
        Luminary
        Jan 03, 2017

        Agree with Mikey.  A bit more info will help.  You may have something on your nework that is broadcasting (ARP or other) every 10 seconds.  Options are to trace the network to see who the offender is, or take components offline one at a time until you can isolate the source.

  • Mikey94025's avatar
    Mikey94025
    Hero
    Jan 03, 2017

    I also ran a ping test from my laptop connected to the satellite.  My ping results aren't as stable as MarkC1024's, but don't show the huge variation of the OP:

     

    Ping statistics for 192.168.1.1:
    Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 24ms, Average = 6ms

     

    Let's try to figure out what's going on for the OP:

     

    1. Have you run this same test on multiple clients?  That will eliminate a client-specific issue.

     

    2. What else do you have running on your wireless network?  What else is connected to the same satellite (Basic... Attached Devices)? I have 9 other clients attached to the same satellite as my laptop, including a Dropcam, so there's a bit of other traffic going on.

     

    3. What connection speed is your client using?  My laptop is 5G vs. 2.4G.  This doesn'treally tell us anything other than at least I'm connected the best way.  :-)