Ping spikes after the Sonoma's update

Hello,


I was using Monterey for a long time and decided to get the update to 14.2.1. After the update I started to notice ping spikes in all games I play from GeForce Now, Steam. I'm getting stuttering all the time with a period like 0.5s. I've started to investigate the reason and solution, but the only thing I found, that the issue disappears after the wifi's disabling/enabling (or laptop's reboot), but not for a long time, it returns after some time. I've tried disabling location/bluetooth/airdrop services, rebooting the router, disabling the maccleaner's defender, played around autoboot items and a lot of other stuff. I think it's more like software's issue, because I haven't faced such issues before the update. Monitoring systems are fine, nothing suspicious even with a game. Network's diagnosis is not showing any issues, the same in EtreCheck. Something is happening after some time after enabling the wifi.


Actually, do not really want to downgrade, so I'm trying to find a solution or at least assumptions what could be a reason for that? Thanks in advance!


Here is a ping:


I've also tried to ping via iPhone - no issues, so, again, I assume it's not a provider's issue.


P.S.: I was looking through the internet, found some similar discussions, but they were without responses, so, probably, this topic may be helpful for a workaround.


Macbook Pro (2020) 13" M1, 16gb RAM, 512gb SSD, MacOS Sonoma 14.2.1

MacBook Pro (M1, 2020)

Posted on Dec 23, 2023 9:48 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 12, 2024 9:17 AM

Thanks for posting on this, relieved to see it as I was convinced I was going mad and/or I had some external issue which I had to track down. Just to concur I'm seeing an identical issue after updating to Sonoma 14.2.1 on my 2021 MBP M1. Also to confirm my scenario has zero to do with the internet, as the spikes are experienced when pinging my local router (inside interface). I work from home quite frequently and this is effecting real-time video calls (Teams/Zoom).


The only change on my side was after updating to Sonoma. From my MBP 2021 14.2.1 if I ping my inside router I'll see rtt range from 1ms-5ms and then regular spikes from 200ms-1500ms which always coincide with the video/audio freeze on the Teams/Zoom call. On my earlier MacBook Intel Pro 2017 running Ventura 13.6.1, with otherwise identical SSID and pings the rtt ranges from 1ms-5ms with what I consider expectable and reasonable (Normal for any home wifi with various devices connected and contending) occasional spikes to 40-100ms. Essentially the 2017 MacBook can run Teams calls with zero momentary video/audio freezes vs the 2021 MacBook experiencing video/audio freezes almost every min or few. This phenomena didn't occur before the Sonoma update.


Following the link here (thanks!) https://apple.stackexchange.com/questions/451646/force-disabling-awdl-on-ventura-or-above/454060, I have moved my WiFi 5 channel from 36 to 44 and this seems to have so far drastically reduced the spikes on the 2021 MBP. There's reasons specifically behind changing the channel (AWDL) as explained in that link and FWIW I have scanned (NetSpot) my home WiFi and confirmed that 36 and 44 are otherwise free and available. My point being the problem isn't caused by a conflict on either channel 36 or 44 at my home, rather AWDL prefers operating on channel 44 vs 36.


I will put it to the test on the Teams/Zoom call. Be interesting if anybody else experiencing the problem can try this.

17 replies
Question marked as Top-ranking reply

Jan 12, 2024 9:17 AM in response to clvmswtf

Thanks for posting on this, relieved to see it as I was convinced I was going mad and/or I had some external issue which I had to track down. Just to concur I'm seeing an identical issue after updating to Sonoma 14.2.1 on my 2021 MBP M1. Also to confirm my scenario has zero to do with the internet, as the spikes are experienced when pinging my local router (inside interface). I work from home quite frequently and this is effecting real-time video calls (Teams/Zoom).


The only change on my side was after updating to Sonoma. From my MBP 2021 14.2.1 if I ping my inside router I'll see rtt range from 1ms-5ms and then regular spikes from 200ms-1500ms which always coincide with the video/audio freeze on the Teams/Zoom call. On my earlier MacBook Intel Pro 2017 running Ventura 13.6.1, with otherwise identical SSID and pings the rtt ranges from 1ms-5ms with what I consider expectable and reasonable (Normal for any home wifi with various devices connected and contending) occasional spikes to 40-100ms. Essentially the 2017 MacBook can run Teams calls with zero momentary video/audio freezes vs the 2021 MacBook experiencing video/audio freezes almost every min or few. This phenomena didn't occur before the Sonoma update.


Following the link here (thanks!) https://apple.stackexchange.com/questions/451646/force-disabling-awdl-on-ventura-or-above/454060, I have moved my WiFi 5 channel from 36 to 44 and this seems to have so far drastically reduced the spikes on the 2021 MBP. There's reasons specifically behind changing the channel (AWDL) as explained in that link and FWIW I have scanned (NetSpot) my home WiFi and confirmed that 36 and 44 are otherwise free and available. My point being the problem isn't caused by a conflict on either channel 36 or 44 at my home, rather AWDL prefers operating on channel 44 vs 36.


I will put it to the test on the Teams/Zoom call. Be interesting if anybody else experiencing the problem can try this.

Jan 16, 2024 12:05 PM in response to KGreenway20

I have the exact same problem on a MacBook air M2 with Sonoma 14.2.1; AWDL scans-, and traffic, will cause unacceptable latency spikes on my primary network, rendering Facetime, Zoom, Teams etc. performing really bad.


As of now, I have three workarounds working:

1) Switch AP to channel 44 (I'm in Europe)

2) Switch to cabled ethernet

3) Shut down AWDL (and keep it down)


I found this tool, which works exactly as advertised; shutting down the awdl0 interface, and keep it down whenever it auto-activates:


https://github.com/jamestut/awdlkiller


An easy way to identify the problem; latency spikes or not, I have used this service:

https://packetlosstest.com/

  • Preset approximation: Zoom
  • Choose a server relatively near you
  • And then try to provoke AWDL traffic. - For me, just waking up my iPad will often cause the issue to materialize.

Jan 9, 2024 3:51 AM in response to clvmswtf

There is one certain method to prove or disprove " not assumptions. "


This is not presently lightly


How to erase all content and settings


Then install ALL Required Applications from the Apple Apps Store ( exception CleanMyMac ) or Directly from the Developers Website


Do Not Migrate anything from a Previous Time Machine Backup


Test the ping results and compare


The suggestions have been put forth on a volunteer basis, in good faith and in the best interests of the computer.


EDITED - me

Jan 10, 2024 8:33 PM in response to Owl-53

PRP_53 and VikingOSX are muddying the thread with irrelevant lectures on how pings to the external internet work and other topics.


Both clvmswtf and myself see consistent issues with Sonoma reproducible within our own Wifi networks. Simultaneously, two different devices show two ping profiles--one healthy and one degraded. The degraded ping spike issue is seen only on the Sonoma device. The other Mac device, which itself is a newer generation MacBook is on Ventura and _does not_ see the issue. Therefore, it's not related to the external internet (both devices are on the same Wifi network to the same shared _local_ router), yet the only difference is the OS: Sonoma. Sonoma is showing ping spikes for me, and it seems for other people.


The other posters are spam, please ignore them.

Jan 9, 2024 1:57 AM in response to clvmswtf

User wrote " disabling the maccleaner's defender, "


Any Third Party Applications that will interfere with the normal operation of the OS,  is an invitation for disaster. 


Certain Applications maybe available on the Apple Apps Store - this only means the Developer is prepared to pay Apple a portion on each sale. 


What the Application may do to the computer is up to the User to check this out before purchase


Any of the below should be removed as per Developers Instructions 


Disk Cleaner 


This will include CleanMyMac , aka “ BrickMyMac


Specific to CleanMyMac aka “ BrickMyMac


To put the CleanMyMac in context and the damages it may have or has already done.


This application can or will Muck Up your User Account ( Home Folder ) of this machine.


It does not touch the Operating System itself unless you consider your User Account ( Home Folder ) as part of the Operating System


Then in that specific context - it has Mucked Up the Operating  System

Jan 12, 2024 9:29 AM in response to KGreenway20

Thanks for sharing, that the link helped you. Here is one more related explanation regarding the issue: https://forums.macrumors.com/threads/wi-fi-jitter-erratic-ping-latency-due-to-awdl-airdrop-airplay.2373916/ (AdriftAtlas's comment). It's also recommended to switch 2.4GHz to 6 channel. 5GHz to 44 channel, as you've already done. Important note that these channel's solution is only available for Europe, I assume.


Anyway, it solves the issue only for the home's network, I assume that somewhere else we may also encounter it again.

Jan 9, 2024 2:18 AM in response to clvmswtf

Having used this piece of software, " CleanMyMac aka “ BrickMyMac “ on a previous version of macOS may not have shown issues


Having upGraded to Sonoma or UpDated a version within Sonoma may have amplified the extent of the possible damage this software has inflicted on the Operating System


Doing " And yes, I’ve tried a clean setup and had same issue. " and migrating over from a TM Backup would have effectively Re-Introduced the then existing issue back into the otherwise Pristine and Virginal Installation


In so doing Negating the hard work that was done



Dec 23, 2023 10:09 AM in response to clvmswtf

Ping is directly dependent on the overall health of the Internet, which is continuously changing, and the destination of your ping request. You can see this in the variety of delays in your ping of Google's DNS address. A Wi-Fi connection to your own router is not a constant but variable rate too, just as is the ISP's network segment your neighborhood utilizes has variable rates of saturation.


I upgraded from Ventura to Sonoma 14.2.1 and my network response rates improved. I can qualify that by stating that before the Sonoma upgrade, I replaced my Apple AirPort BaseStation Extreme, old cable modem with a 2.5 Gb rated DOCSIS 3.1 unit, and a 2.5 Gb network switch. Introduced CAT7 cable for the 2.5 Gb devices to augment the CAT 5E cable in the house. Before I made the network infrastructure upgrades, my average speedtest.net throughput to Comcast was around 70 MB/s and afterward, 270 MB/s without changing the Internet plan.

Dec 23, 2023 10:16 AM in response to VikingOSX

Thanks for the reply, but your answer gives me nothing helpful. Everything was fine before the update, as mentioned above. Also, I've already mentioned, that I was testing the connection with iPhone and other devices, which confirmed my assumptions, that the issue is not related to network hardware or provider. Currently, I'm facing explicit connection issues, which could not be affected by my actions, since the only thing I've done, was the upgrade to Sonoma.


P.S.: speed test is showing 300 mbs, so that's not the issue of speed.

Jan 8, 2024 6:10 PM in response to timeisapear

This issue is really noticeable in latency-important apps (like streaming apps). I assume the issue is still not fixed in Ventura and higher OSes, the biggest part is just not noticing this issue with daily usage. You may try to go through steps, which are described in the comment (that with a link) above, to get rid of ping issues at least within home network.

Jan 9, 2024 2:49 AM in response to Owl-53

As a casual user (from buyer's perspective), I have not to take care, which app (downloaded from the official AppStore!) is breaking my laptop's OS implicitly (or potentially may break), especially on the OS core level (I assume so, because the issue was gone after the setting router's channels explicitly), if it may potentially break something, then it has to be restricted on the core layer. Anyway, I still think these arguments are not related to the real issue, I'd like to see potential solutions (or at least an information, that the issue is investigated), not assumptions.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Ping spikes after the Sonoma's update

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.