Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I'm having significant issues with networking on beta 2... do not recommend the update. Turning off limit IP tracking has done little to resolve the issues.
 
For anyone experiencing network connection problems or having issues with loading websites while using a network filter like Little Snitch or LuLu - Disabling the filter immediately restores connectivity.
Best Solution for now ist disabling Private Relay because that restores connectivity.
 
I've never had private relay on (and I don't bother with lulu or LS):
1772014432645.png
 
I’m interested to see where this goes. I’ve installed 26.4b2, and haven’t had any networking issues yet.

Am I just lucky, or is there some variable that’s in play?
 
I’m interested to see where this goes. I’ve installed 26.4b2, and haven’t had any networking issues yet.

Am I just lucky, or is there some variable that’s in play?
Let's say that to get an idea, we would at least need to know the model and connection method.

I have no problems with a MacBook M1 Pro connected via Ethernet (Realtek 8157). No filtering software, just the normal firewall active.
 
Last edited:
I can confirm that uninstalling Little Snitch and disabling "Limit IP Tracking" resolved networking issues for me. It's worth a shot for anyone else experiencing similar issues.
 
Let's say that to get an idea, we would at least need to know the model and connection method.

I have no problems with a MacBook M1 Pro connected via Ethernet (Realtek 8157). No filtering software, just the normal firewall active.
I have an M3 Pro MacBook Pro connected via WiFi, don’t yet 3rd party networking software, have limit IP tracking and private relay turned on.
 
I can confirm that uninstalling Little Snitch and disabling "Limit IP Tracking" resolved networking issues for me. It's worth a shot for anyone else experiencing similar issues.

I lately canceled my iCloud+ membership and lost Private Relay. I wonder if "Limit IP address tracking even is doing anything without Private Relay.

It's still activated on my Mac and I don't have any problems since all network filters are gone. But I remember seeing a message that it doesn't have any affect anymore when Private Relay was disabled automatically after my iCloud downgrade.


Screenshot 2026-02-25 at 17.37.54.png


Safari:

Screenshot 2026-02-25 at 17.49.13.png


In Mail I am always blocking everything and that disables the first option:

Screenshot 2026-02-25 at 17.51.34.png


How do I know if those options still work without Private Relay? It's not even mentioned in the help.

Screenshot 2026-02-25 at 17.59.34.png
 
Last edited:
Somehow my Internet was partially broken. Not sure if it was the updates fault. But it seems restarting the router helped.

Edit: Seems I am not the only one with Internet issues.

Edit2: YouTube is almost unusable at the moment.
I'm seeing serious Internet issues too. Dropbox (or rather, Maestral) isn't connecting, and I can't access local IP addresses. Some websites are loading okay-ish, but Mail is taking forever to download. I'm on an M1 Pro MacBook Pro.

It seems pretty borked, and I'd advise folks to steer clear for now.
 
Search bar in the Settings app now diffuses background items in the sidebar better.
 

Attachments

  • Image 2-25-26 at 4.48 PM.png
    Image 2-25-26 at 4.48 PM.png
    374.9 KB · Views: 96
  • Like
Reactions: goro123
I too experience networking issues. My work VPN/ssh access do not function correctly. Restart fixes it very briefly, and after 5 minutes it's out again. Very annoying.
 
Strange release.

Personally, I encountered the installer problem, but Onyx solved it (others did not).

No network problems, full and stable speed internal and external network access (2.5gbps).

I can customize icons as before.


It reminds me of this from many years ago:

“Apple's attempt to replace mDNSResponder with discoveryd in OS X Yosemite (10.10) caused major network instability, forcing a return to mDNSResponder in El Capitan. This transition resulted in high CPU usage, erratic DNS behavior, and dropped connections for many users, marking a notorious period in macOS networking.”
 
  • Like
Reactions: losthismarbles
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.