Orbi latency peaks every 10s

[pingles]

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 could be fixed/improved by changing a setting or a later firmware update given the pings the rest of the time are pretty decent (and way better than my Powerline used to be!).

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=226.184 ms64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=198.941 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=8.368 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=8.117 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.093 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=7.980 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=7.061 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=8.927 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=7.143 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=7.072 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=6.487 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=7.305 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=219.613 ms64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=189.920 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=163.318 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=4.781 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=6.972 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=8.442 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=7.766 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=6.369 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=6.157 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=8.370 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=6.842 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=8.006 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=5.929 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=170.300 ms64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=146.993 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=123.569 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=7.265 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=7.403 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=8.525 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=10.524 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=8.520 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=9.497 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=9.036 ms
64 bytes from 192.168.1.1: icmp_seq=35 ttl=64 time=7.962 ms
64 bytes from 192.168.1.1: icmp_seq=36 ttl=64 time=8.587 ms
64 bytes from 192.168.1.1: icmp_seq=37 ttl=64 time=9.092 ms
64 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=139.300 ms64 bytes from 192.168.1.1: icmp_seq=39 ttl=64 time=121.157 ms
64 bytes from 192.168.1.1: icmp_seq=40 ttl=64 time=94.661 ms
64 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=6.622 ms

[MarkC1024]

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]

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

[Mikey94025]

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.  🙂

[MarkC1024]

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]

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.

[djc6]

pingles,

I am seeing the same thing when connected to a satellite via wifi.  Its more noticable if i decrease the ping interval from 1 second to a fraction of a second - in the following example I use an interval of a 10th of a second.

ping -c 1000 192.168.1.1 -i .1

I do NOT see this when connected to router via Wi-Fi - only when talking to Satellite via Wi-Fi.  Test was performed using Mid-2012 Retina MacBook Pro running OS X Sierra 10.12.2.  My Oribi RBK53 (Costco 3 pack) is running firmware V1.4.0.18

pingles: how many satellites do you have?  I have 1 router and 2 satellites.

64 bytes from 192.168.1.1: icmp_seq=451 ttl=64 time=4.997 ms
64 bytes from 192.168.1.1: icmp_seq=452 ttl=64 time=5.568 ms
64 bytes from 192.168.1.1: icmp_seq=453 ttl=64 time=4.252 ms
64 bytes from 192.168.1.1: icmp_seq=454 ttl=64 time=4.796 ms
64 bytes from 192.168.1.1: icmp_seq=455 ttl=64 time=4.808 ms
64 bytes from 192.168.1.1: icmp_seq=456 ttl=64 time=5.918 ms
64 bytes from 192.168.1.1: icmp_seq=457 ttl=64 time=4.896 ms
64 bytes from 192.168.1.1: icmp_seq=458 ttl=64 time=4.875 ms
64 bytes from 192.168.1.1: icmp_seq=459 ttl=64 time=3.767 ms
64 bytes from 192.168.1.1: icmp_seq=460 ttl=64 time=5.479 ms
64 bytes from 192.168.1.1: icmp_seq=461 ttl=64 time=4.147 ms
64 bytes from 192.168.1.1: icmp_seq=462 ttl=64 time=5.974 ms
64 bytes from 192.168.1.1: icmp_seq=463 ttl=64 time=6.681 ms
64 bytes from 192.168.1.1: icmp_seq=464 ttl=64 time=4.803 ms
64 bytes from 192.168.1.1: icmp_seq=465 ttl=64 time=5.929 ms
64 bytes from 192.168.1.1: icmp_seq=466 ttl=64 time=5.216 ms
64 bytes from 192.168.1.1: icmp_seq=467 ttl=64 time=8.082 ms
64 bytes from 192.168.1.1: icmp_seq=468 ttl=64 time=5.430 ms
64 bytes from 192.168.1.1: icmp_seq=469 ttl=64 time=4.777 ms
64 bytes from 192.168.1.1: icmp_seq=470 ttl=64 time=7.027 ms
64 bytes from 192.168.1.1: icmp_seq=471 ttl=64 time=4.805 ms
64 bytes from 192.168.1.1: icmp_seq=472 ttl=64 time=7.067 ms
64 bytes from 192.168.1.1: icmp_seq=473 ttl=64 time=4.367 ms
64 bytes from 192.168.1.1: icmp_seq=474 ttl=64 time=4.655 ms
64 bytes from 192.168.1.1: icmp_seq=475 ttl=64 time=4.671 ms
64 bytes from 192.168.1.1: icmp_seq=476 ttl=64 time=4.624 ms
64 bytes from 192.168.1.1: icmp_seq=477 ttl=64 time=5.801 ms
64 bytes from 192.168.1.1: icmp_seq=478 ttl=64 time=4.724 ms
64 bytes from 192.168.1.1: icmp_seq=479 ttl=64 time=4.095 ms
64 bytes from 192.168.1.1: icmp_seq=480 ttl=64 time=4.839 ms
64 bytes from 192.168.1.1: icmp_seq=481 ttl=64 time=5.581 ms
64 bytes from 192.168.1.1: icmp_seq=482 ttl=64 time=4.024 ms
64 bytes from 192.168.1.1: icmp_seq=483 ttl=64 time=5.493 ms
64 bytes from 192.168.1.1: icmp_seq=484 ttl=64 time=5.539 ms
64 bytes from 192.168.1.1: icmp_seq=485 ttl=64 time=5.540 ms
64 bytes from 192.168.1.1: icmp_seq=486 ttl=64 time=4.102 ms
64 bytes from 192.168.1.1: icmp_seq=487 ttl=64 time=6.181 ms
64 bytes from 192.168.1.1: icmp_seq=488 ttl=64 time=35.406 ms
64 bytes from 192.168.1.1: icmp_seq=489 ttl=64 time=119.046 ms
64 bytes from 192.168.1.1: icmp_seq=490 ttl=64 time=19.870 ms
64 bytes from 192.168.1.1: icmp_seq=491 ttl=64 time=122.219 ms
64 bytes from 192.168.1.1: icmp_seq=492 ttl=64 time=108.944 ms
64 bytes from 192.168.1.1: icmp_seq=493 ttl=64 time=44.019 ms
64 bytes from 192.168.1.1: icmp_seq=494 ttl=64 time=112.745 ms
64 bytes from 192.168.1.1: icmp_seq=495 ttl=64 time=9.956 ms
64 bytes from 192.168.1.1: icmp_seq=496 ttl=64 time=195.285 ms
64 bytes from 192.168.1.1: icmp_seq=497 ttl=64 time=96.414 ms
64 bytes from 192.168.1.1: icmp_seq=498 ttl=64 time=3.949 ms
64 bytes from 192.168.1.1: icmp_seq=499 ttl=64 time=58.528 ms
64 bytes from 192.168.1.1: icmp_seq=500 ttl=64 time=248.221 ms
64 bytes from 192.168.1.1: icmp_seq=501 ttl=64 time=143.193 ms
64 bytes from 192.168.1.1: icmp_seq=502 ttl=64 time=46.081 ms
64 bytes from 192.168.1.1: icmp_seq=503 ttl=64 time=35.972 ms
64 bytes from 192.168.1.1: icmp_seq=504 ttl=64 time=231.457 ms
64 bytes from 192.168.1.1: icmp_seq=505 ttl=64 time=129.308 ms
64 bytes from 192.168.1.1: icmp_seq=506 ttl=64 time=28.345 ms
64 bytes from 192.168.1.1: icmp_seq=507 ttl=64 time=94.077 ms
64 bytes from 192.168.1.1: icmp_seq=508 ttl=64 time=5.232 ms
64 bytes from 192.168.1.1: icmp_seq=509 ttl=64 time=179.847 ms
64 bytes from 192.168.1.1: icmp_seq=510 ttl=64 time=83.300 ms
64 bytes from 192.168.1.1: icmp_seq=511 ttl=64 time=3.749 ms
64 bytes from 192.168.1.1: icmp_seq=512 ttl=64 time=44.362 ms
64 bytes from 192.168.1.1: icmp_seq=513 ttl=64 time=233.889 ms
64 bytes from 192.168.1.1: icmp_seq=514 ttl=64 time=133.388 ms
64 bytes from 192.168.1.1: icmp_seq=515 ttl=64 time=33.705 ms
64 bytes from 192.168.1.1: icmp_seq=516 ttl=64 time=104.128 ms
64 bytes from 192.168.1.1: icmp_seq=517 ttl=64 time=4.008 ms
64 bytes from 192.168.1.1: icmp_seq=518 ttl=64 time=6.274 ms
64 bytes from 192.168.1.1: icmp_seq=519 ttl=64 time=3.883 ms
64 bytes from 192.168.1.1: icmp_seq=520 ttl=64 time=6.042 ms
64 bytes from 192.168.1.1: icmp_seq=521 ttl=64 time=5.978 ms
64 bytes from 192.168.1.1: icmp_seq=522 ttl=64 time=6.475 ms
64 bytes from 192.168.1.1: icmp_seq=523 ttl=64 time=5.549 ms
64 bytes from 192.168.1.1: icmp_seq=524 ttl=64 time=5.455 ms
64 bytes from 192.168.1.1: icmp_seq=525 ttl=64 time=5.751 ms
64 bytes from 192.168.1.1: icmp_seq=526 ttl=64 time=5.832 ms
64 bytes from 192.168.1.1: icmp_seq=527 ttl=64 time=4.702 ms
64 bytes from 192.168.1.1: icmp_seq=528 ttl=64 time=4.082 ms
64 bytes from 192.168.1.1: icmp_seq=529 ttl=64 time=4.590 ms
64 bytes from 192.168.1.1: icmp_seq=530 ttl=64 time=5.860 ms
64 bytes from 192.168.1.1: icmp_seq=531 ttl=64 time=3.874 ms
64 bytes from 192.168.1.1: icmp_seq=532 ttl=64 time=5.861 ms
64 bytes from 192.168.1.1: icmp_seq=533 ttl=64 time=5.321 ms
64 bytes from 192.168.1.1: icmp_seq=534 ttl=64 time=5.039 ms
64 bytes from 192.168.1.1: icmp_seq=535 ttl=64 time=4.444 ms
64 bytes from 192.168.1.1: icmp_seq=536 ttl=64 time=5.166 ms
64 bytes from 192.168.1.1: icmp_seq=537 ttl=64 time=3.715 ms
64 bytes from 192.168.1.1: icmp_seq=538 ttl=64 time=7.307 ms
64 bytes from 192.168.1.1: icmp_seq=539 ttl=64 time=4.303 ms
64 bytes from 192.168.1.1: icmp_seq=540 ttl=64 time=4.320 ms
64 bytes from 192.168.1.1: icmp_seq=541 ttl=64 time=4.574 ms
64 bytes from 192.168.1.1: icmp_seq=542 ttl=64 time=6.064 ms
64 bytes from 192.168.1.1: icmp_seq=543 ttl=64 time=5.582 ms

[pingles]

I see similar when I connect to the Router via wifi also:

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.304 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.652 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.817 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.252 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=4.162 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=76.322 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.992 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=96.374 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.776 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=2.334 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=4.596 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=2.277 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=9.073 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=1.859 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=19.726 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1.696 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=4.143 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=12.565 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=37.218 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=107.542 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=62.228 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=2.990 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=0.985 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=2.310 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=1.149 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=2.073 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=1.936 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=3.625 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=2.067 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=2.030 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=4.240 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=2.331 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=77.865 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=25.668 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=1.954 ms

This is from the same MacBook Pro Retina (OSX 10.11.6) as the earlier test. I'll do some more wired/other client tests tomorrow and report back on what I find. Thanks for everyone's help.

[djc6]

---

@pingles wrote:

This is from the same MacBook Pro Retina (OSX 10.11.6) as the earlier test. I'll do some more wired/other client tests tomorrow and report back on what I find. Thanks for everyone's help.

---

I'm starting to wonder if its my Retina MacBook Pro. I noticed that if I have ping going I can make the response times skyrocket by simply clicking on the Wi-Fi icon in system menu bar.  Whenever I click the icon I see the same three seconds of high latency

[ShrinivasKR]

I also see results like that when connected wirelessly to my Satellite.

On games like league of legends, this shows insane packet loss, rendering it completely unplayable. Connecting to it via ethernet works perfectly.

I have tested this on multiple devices

[Rustproofcorn]

How do u do the ping test?

[Dan_H]

No issues here.