My Mac's Wi-Fi Was Crawling at 50 Mbps With a Perfect Signal. The Fix Was Bizarre.

BugMeDaily

SubscribeSign in

My Mac's Wi-Fi Was Crawling at 50 Mbps With a Perfect Signal. The Fix Was Bizarre.<br>How I spent a night chasing routers, radios, and "Wi-Fi 6 interop bugs" — when the real culprit was a rotten macOS network config, and the fix took 30 seconds.

Enes Unal<br>Jul 01, 2026

Share

The short version: If your Mac has a great Wi-Fi signal but terrible speed, and the slowness follows the Mac to every network — different routers, both bands, even a phone hotspot — but disappears the moment you use USB or Ethernet, your macOS network configuration is corrupt.<br>The fix: create a new Network Location (System Settings → Network → ⋯ → Locations → Add Location), reconnect Wi-Fi, and test again. That’s the whole cure.<br>If you also say “bug me daily!”, you can tell me:

Subscribe

Now the story.

Is this you?

I wrote this so the right person finds it. If most of these match, you have exactly what I had:<br>Wi-Fi signal is excellent — full bars, high negotiated rate (1000+ Mbps).

Actual speed is stuck low — mine sat at 30–75 Mbps no matter what.

Other devices on the same router are fast. My iPhone hit 500+ Mbps on the same Wi-Fi.

The Mac is slow on both 2.4 GHz and 5 GHz.

The Mac is slow on other networks too — even a totally different router or a phone hotspot.

But it’s fast over USB tether or Ethernet (I got a clean 150 Mbps).

Latency under load is awful — idle ping ~15 ms, but under load it spikes to 400–850 ms.

It survives reboots. It survives macOS updates.

No errors anywhere. Everything looks perfectly healthy.

If that’s you: it’s not your ISP, not your router, not the band, and not broken hardware. It’s your Mac’s network config.

The setup

A MacBook Pro (M3 Pro) on macOS 26. Gigabit fibre. A Wi-Fi 6 router. The link was textbook-perfect: 160 MHz channel, signal at −44 dBm, top-tier modulation.<br>Real-world speed: about 50 Mbps. On a gigabit line.<br>Every metric screamed “your Wi-Fi is amazing.” Every download said otherwise.

The rabbit holes (so you don’t fall in them)

I burned hours on theories that were all wrong — and they were wrong for one sneaky reason: the signal looked flawless, so I kept staring at the radio. Here’s what I chased. You’ll be tempted by every one of these. Don’t be.<br>Red herring #1 — “It’s the ISP or DNS.” Killed fast. Multiple independent speed tests hit the identical ceiling. When everything caps at the same number, the problem is local.<br>Red herring #2 — “It’s AirDrop/Continuity stealing the radio” (AWDL). This is a real macOS thing: one radio time-shared between Wi-Fi and AirDrop. A packet capture even showed periodic ~90 ms blackouts on a clockwork cadence. Very convincing.<br>Test: sudo ifconfig awdl0 down right before a speed test. Result: no change. Innocent.

Red herring #3 — “160 MHz is fragile in a crowded building.” My best theory. A 160 MHz channel needs a lot of clean spectrum, and I live somewhere dense. It even explained why my iPhone (narrower channel) was fine.<br>Test: split the router into separate 2.4 GHz and 5 GHz networks and test each. Result: ~50 Mbps on both . But 2.4 GHz can’t even do 160 MHz — it’s completely different spectrum. If both bands fail identically, anything radio-specific is dead.

Red herring #4 — “A proxy or VPN is throttling it.” macOS even flagged “custom web proxy settings.” But every proxy toggle was actually off. False alarm.

The breakthrough: stop looking at the radio, look at the pattern

Here’s the reasoning that cracked it — and it’s the one lesson worth stealing from this whole mess.<br>Forget the metrics. Just map where the problem shows up and where it doesn’t:<br>Router 5 GHz → ~50–75 Mbps 🐢

Router 2.4 GHz → ~50 Mbps 🐢

A different router / phone hotspot → ~50–60 Mbps 🐢

iPhone on the same router → 500+ Mbps 🚀

The Mac over USB tether (no Wi-Fi) → 150 Mbps 🚀

Read that like a detective:<br>The slowness follows the Mac — across two bands and multiple routers. So it’s not the router, not the band, not the environment.

But it vanishes the instant Wi-Fi leaves the path (USB). So it’s not the Mac’s TCP stack, CPU, or apps either.

Only one thing is present in every slow case and absent from every fast one: the Mac’s Wi-Fi network configuration. Not the hardware (fast over USB, perfect signal). Not the airwaves (slow everywhere). The config layer sitting between them.<br>That’s the trick. When a fault follows a machine but only on one type of connection, you’ve isolated it to that machine’s config for that connection. No packet capture required.

The fix

macOS keeps your entire network configuration — every interface, service order, DHCP lease, IPv6 setup, DNS, proxies — inside something called a Network Location . Almost nobody knows it exists, because everyone lives in the default one (”Automatic”) forever.<br>Over time, that config rots. Reboots don’t help — config files persist. macOS updates don’t help — they persist across those too....