MacBook Pro experiencing ping spikes to local router

Question

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)

Answer 1

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

Answer 2

I've had exactly the same problem, it was troubling me quite a long time. It is especially annoying when working remotely over SSH or playing multiplayer games. Here is my long-term solution:

Diagnosis

Run ping with frequency 10 scans per second to see when is the glitch occurring:

ping 8.8.8.8 -i 0.1

Scanning & Location services

As mentioned by others, WiFi spikes are typically caused by WiFi daemon scanning another WiFi networks around. The scanning goes through all channels so if the current receiving channel is not the same as your AP is transmitting, you have a ping spike.

The scanning is usually triggered by location services. You can review the location services in: System Preferences -> Security & Privacy -> Privacy tab -> Location Services.

If you go to Advanced check the Show location icon in the menu bar... to see when the apps are querying location thus scanning WiFi neighborhood.

Location services were still active because of System services. Mainly Time Zone & System Customisation and Significant Locations. But after turning that off I still had a WiFi glitch in spite of that Location setting window showed no other application acquiring the location.

Finding the culprit

You need to enable WiFi logging to see why is WiFi daemon doing the scan.

Hold option/alt key (next to the command key) and click WiFi icon in the top toolbar. Click Enable Wi-Fi Logging.

After that open a new terminal:

tail -f /var/log/wifi.log

You should see something like this:

Mon Jan 14 20:01:21.353 AutoJoin: <airportd[83093]> Successful cache-assisted scan request for texstudio with channels {(
Mon Jan 14 20:01:21.353     <CWChannel: 0x7fbcfadc5b20> [channelNumber=56(5GHz), channelWidth={40MHz(-1)}, active, DFS],
Mon Jan 14 20:01:21.353     <CWChannel: 0x7fbcfadcbfb0> [channelNumber=60(5GHz), channelWidth={40MHz(+1)}, active, DFS],
Mon Jan 14 20:01:21.353     <CWChannel: 0x7fbcfd44c790> [channelNumber=64(5GHz), channelWidth={40MHz(-1)}, active, DFS],
Mon Jan 14 20:01:21.353     <CWChannel: 0x7fbcfadc6ba0> [channelNumber=149(5GHz), channelWidth={80MHz}, active],
Mon Jan 14 20:01:21.353     <CWChannel: 0x7fbcfad2be90> [channelNumber=153(5GHz), channelWidth={80MHz}, active],
Mon Jan 14 20:01:21.353     <CWChannel: 0x7fbcfadf4870> [channelNumber=157(5GHz), channelWidth={80MHz}, active]
Mon Jan 14 20:01:21.353 )} took 0.0005 seconds, returned 2 results
Mon Jan 14 20:01:21.353 Scan: <airportd[83093]> Cache-assisted scan request for texstudio on channel 161 does not require a live scan
Mon Jan 14 20:01:21.353 Scan: <airportd[83093]> Cache-assisted scan request for texstudio on channel 165 does not require a live scan
Mon Jan 14 20:01:21.353 Scan: <airportd[83093]> Cache-assisted scan request for texstudio on channel 100 does not require a live scan
Mon Jan 14 20:01:21.353 Scan: <airportd[83093]> Cache-assisted scan request for texstudio on channel 104 does not require a live scan
Mon Jan 14 20:01:21.353 Scan: <airportd[83093]> Cache-assisted scan request for texstudio on channel 108 does not require a live scan
Mon Jan 14 20:01:21.353 Scan: <airportd[83093]> Cache-assisted scan request for texstudio on channel 112 does not require a live scan
Mon Jan 14 20:01:21.353 Scan: <airportd[83093]> Cache-assisted scan request for texstudio does not require a live scan

Now observe ping terminal and wifi log terminal next to each other. You can clearly see the glitch occurrs precisely when WiFi is doing the scan.

In my case the culprit was a program texstudio, as you can see from the log. It was acquiring location every 5 seconds (wt.?), which was is confirmed also by this guy: https://justus.berlin/2016/04/reducing-cpu-load-and-energy-consumption-of-texstudio-on-the-mac/

This solved my problem. The Texstudio was not mentioned in the location services list so this advanced approach was necessary.

Summary:

• The culprit is location services and wifi scanning
• Check location services you have enabled
• Hold Option keyboard key, click the WiFi icon in the top toolbar, click Enable Wi-Fi Logging
• Execute in terminal: ping 8.8.8.8 -i 0.1
• Execute in terminal: tail -f /var/log/wifi.log, in a new window. Observe side by side, wait for glitch.
• Check the log when the glitch was observed, kill the program.

Answer 3

In my case, something related to the AWDL was causing ping spikes, and in order to fix it, I had to shut down the awdl0 network interface.

TLDR: this command resolved my ping spike issues: sudo ifconfig awdl0 down

How did I come up with the command above

I've used multiple recommendations from other answers in this thread. I've disabled the Location Services and Bluetooth and still had regular ping spikes. Then I enabled wifi logging by holding alt\option key and clicking wifi icon. Then I've opened two consoles side by side:

1. ping -i 0.25 192.168.1.1 --apple-time
2. tail -f /var/log/wifi.log

The ping results were stable until a log message appears:

Tue Feb 16 15:03:40.621 Info: <airportd[12479]> AWDL started

It's interesting that after this message there were no other suspicious messages in the wifi.log, but there were constant ping spikes.

I've continued the investigation and occasionally found this thread on Github with a recommendation to run the command below:

sudo log stream | grep -iE --color 'location|wireless|awdl|phone|rapport|sharing|handoff' That command streams system logs, showing you any lines containing any of those words.

I've run the command above in the third console.

Then I've noticed a lot of messages with a text like "AWDL is still enabled due to active sockets, but no services[nonAirplay:0 Airplay 0]"

2021-02-16 15:39:16.602945+0700 0x1337f7   Default     0x0                  0      0    kernel: (IO80211Family) com.apple.p2p: IO80211AWDLPeerManager::monitorAWDLState AWDL is still enabled due to active sockets, but no services[nonAirplay:0 Airplay 0]

Further digging has led me to the suggestions to verify if awdl0 status is active. (last property in the output)

$ ifconfig awdl0

awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484
    options=400<CHANNEL_IO>
    nd6 options=201<PERFORMNUD,DAD>
    media: autoselect
    status: active

And if the awdl0 is active, in that case, there was a recommendation to shut it down:

sudo ifconfig awdl0 down

After stopping it, ping spikes have gone and the messages "AWDL is still enabled due to active sockets, but no services[nonAirplay:0 Airplay 0]" were gone too.

When I start awdl0 again by calling sudo ifconfig awdl0 up ping spikes return.

Answer 4

Please run this script from the Terminal.app:

while x=1; do /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I | grep Ctl; ping -c 1 192.168.1.1; sleep 1; done

This script checks for Signal/Noise ratio. You probably have some interference.

Answer 5

Following this guide worked for me:

Fix Wi-Fi problems on MacOs Sierra

essentially in the folder /Library/Preferences/SystemConfiguration/ backup and delete files

com.apple.airport.preferences.plist
com.apple.network.eapolclient.configuration.plist
com.apple.wifi.message-tracer.plist
NetworkInterfaces.plist
preferences.plist

Then restart your Mac.

Answer 6

From my experience, in 90% of all cases, restarting the router will fix the issue.

Answer 7

In addition to disabling Location Services, disable Wi-Fi roaming too. It turns out that periodically my Mac decides to scan for any other networks that might have better signal, right in the middle of the game, causing Wi-Fi disconnect for a few seconds.

This is how it looks in /var/log/wifi.log:

==> Tue Oct 13 02:54:06.014 AutoJoin: <airportd[2664]> BEST CONNECTED SCAN request on interface en0 for network 'XXXXXX' 
    Tue Oct 13 02:54:06.140 Driver Event: <airportd[2664]> _bsd_80211_event_callback: SCAN_CACHE_UPDATED (en0)
    Tue Oct 13 02:54:06.142 AutoJoin: <airportd[2664]> Successful cache-assisted background scan request with channels {(
    Tue Oct 13 02:54:06.142     <CWChannel: 0x7fc439c40cc0> [channelNumber=1(2GHz), channelWidth={20MHz}, active],
    Tue Oct 13 02:54:06.142     <CWChannel: 0x7fc439c44240> [channelNumber=2(2GHz), channelWidth={20MHz}, active],
    Tue Oct 13 02:54:06.142     <CWChannel: 0x7fc439c246b0> [channelNumber=3(2GHz), channelWidth={20MHz}, active]
    Tue Oct 13 02:54:06.142 )} took 0.1262 seconds, returned 2 results
    Tue Oct 13 02:54:06.142 Info: <Wi-Fi Menu Extra[296]> scan cache updated

This is how it's fixed:

sudo defaults write /Library/Preferences/com.apple.airport.opproam disabled -bool true

Reboot after applying.

If you'll need to enable Wi-Fi roaming again, replace true with false in the command above.

Answer 8

In my case, it was an app for taking screenshots. I detected it by doing the following: I ran ping command and was closing apps one by one, then I noticed after closing this app, ping spikes had gone.

Answer 9

In my case the high pings were caused by the Deepl application. Hope this helps somebody.

Answer 10

Same issue here - can't comment yet, but a little more insight nonetheless:

For me the issue was resolved with regards to the top comment, simply disabled locationd. (mbp 2010, osx 10.13, fresh install)

However, for me it occurred ONLY on en0 = ethernet, but somehow not on WiFi. This might sound benign, but having said that, for someone looking for this issue, the tags "wifi and airport" may sound diverting if their setup is similar to mine.

Also - the ping spikes are not limited to the local router for me. My setup consists of an Access point, connected to my separate (wifi-less) router. My ping spikes were as follows:

• MacBook -> Access Point (plugged in Ethernet Switchport)
• MacBook -> Router (via AP Switch)
• MacBook -> Internet

Also also - it wasn't even spikes for me - more like avg. pings around 1000ms, with frequent drops to the low 100s or almost "normal"

Answer 11

I have tracked similar problems to Airplay/Bonjour, ping spikes while airplay is in use or being checked.

I believe this behaviour is actually linked to the bluetooth of the device being linked with the wireless adapter in the device.

I am going to conduct some more tests soon and submit an apple bug report.

if you keep bluetooth disabled you will probably find you will get no ping spikes.

Answer 12

The problem still occurs on Mojave, so let me put my two cents here. The source of the problem was locationd and to fix the spikes all I had to was to go to Settings -> Security & Privacy -> Location Services -> (System Services) Details -> uncheck "Time Zone & System Customization"

No idea why would the Mac check time zone every few minutes...

Answer 13

Adding for more information as identifying why my mac was dropping off WiFi was excruciatingly painful and time wasteful. TL;DR look at the airportd log to see who is requesting WiFi scans.

The 2.4GHz radio in my mac seems dead. And coincident with that failure, the mac was constantly scanning creating obvious ping spikes to the local gateway which were shown as dependent on the scanning. I believe the ping time went up as networking was blocked on kernel_task. airportd was receiving requests from locationd and this traced to the "Find my mac" feature. When turned off, the MBP stopped scanning. I wonder if dead 2.4GHz hardware results in missed cache hits and actual scanning occurring (vs a several minute cache expiration).

Here is my report to Apple:

I was experiencing the exact same thing on an early 2015 MBP w/ Catalina. It was extremely aggravating as the 2.4GHz radio seems dead and 5GHz wasn't working well due to location relative to AP. Timestamping ping and running "/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/airport logger" showed that there was dependence on ping spikes (~1.5ms jumping up to ~200ms) to the local gateway with this airportd autojoin message, "Wed Jan 27 10:53:47: AutoJoin: <airportd[219]> Successful cache-assisted scan request for locationd" The MBP was constantly scanning, and without a decent WiFi connection, networking would ultimately fail.

The ping spikes were also dependent on the "kernel_task" process running, which probably means that networking was blocked in the kernel during the time airportd was doing a scan for locationd.

So, observing that all this was dependent and locationd had way more CPU time then one would imagine, it quickly led to the "Find My Mac" feature. Turning this off quieted locationd and the MBP completely stopped doing a WiFi scans.

Answer 14

Turn of the bluetooth. worked for me

Answer 15

I’m working to correlate log files with this but I don’t yet know how to track/explain/produce these two wifi.log events.

• Driver Event: <airport[310]> _bsd_80211_event_callback: APPLE80211_M_RSSI_CHANGED (en0)

• BTC: <airport[310]> __BluetoothCoexHandleUpdateForNode: Driver supports APPLE80211_CAP_COEX_PROFILE_OFFLOAD. Airportd won't BluetoothCoexModeSet() and defer coex profile loading to UDM coex manager (UCM/WRM) ...

My experience is they log before the spikes happen.

Answer 16

The following almost completely removed spikes and brought average ping times to 192.168.1.1 (my router) to 3-5s:

while sleep 1; do sudo ifconfig awdl0 down; done

This AWDL interface keeps restarting on its own when AirPlay, AirDrop, Location Services or Bluetooth are changed. This loop from the command line keeps it down. I found that is all I need to do.

Answer 17

If all else in this thread fails...

Restart your Mac!

I've tried every single suggestion here and nothing worked. Then I restarted my Mac and voila - back to stable 10ms pings and no spikes.