MacBook Pro experiencing ping spikes to local router I'm experiencing extreme ping spikes to my AirPort Extreme (local IP: 192.168.1.1), however I am not getting these ping spikes on another MacBook Pro right next to it. 

Here are my ping results.

PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=24.703 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=145.378 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=975.540 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=577.900 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.802 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=5.377 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=5.922 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=3.854 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=3.522 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=4.593 ms

--- 192.168.1.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.802/174.959/975.540/316.450 ms


MacBook Pro (Retina, 13-inch, Early 2015)
I'm posting this reply on a few threads to make it easier to find.  I chased the same issue and finally found the cause.

Locationd.  Open the console app and watch while you do a continuous ping.  Every time you see latency spike, you'll see entries for locationd.  Go to System Preferences -> Security &amp; Privacy -> Location Services.  From there, you can disable and you'll likely see the problem disappear.  However, you lose the "find my mac" ability. 

What made mine acceptable was going to system services (scroll down)->details->check show icon in menu bar when [...].  Then, take look at what is requesting location.  Disallowing Evernote helped a lot.  I pruned down to the minimum and the frequency of the spikes has gone down to an acceptable level for me.

edit: filed a bug with Apple because even when location services are disabled, locationd scans (verified in console), impacting latency. Apple marked it as a dupe, so hopefully fixed soon.