A SignalDrop guide · May 11, 2026

Why your Mac silently drops WiFi (and how to catch it)

macOS doesn't tell you when your WiFi disconnects. It just stops working, quietly, while you keep typing into a chat that doesn't send. This is a guide to the seven most common reasons it happens, how to figure out which one is yours, and what to do about each.

The reason macOS doesn't warn you

You'd expect modern macOS to send a banner when your WiFi connection dies. It doesn't. The menu-bar icon changes from full bars to empty bars and assumes you'll look up. You won't. You'll find out three minutes later when your Zoom call freezes, your upload stops, or your terminal hangs.

Apple's apparent reasoning is that macOS auto-reconnects fast enough that notifications would be noise. In practice, the reconnect can take 30 seconds, two minutes, or never — and that's exactly the window in which you need to know. There's no native way to surface it; you need a third-party menu-bar utility.

For most users that's SignalDrop, which registers for kernel-level CoreWLAN events and pushes a native macOS notification the instant the state changes. But before you install anything, it helps to know which of the seven common failure modes is hitting you. The fix depends on the cause.

The seven causes, in rough order of frequency

1. Your ISP is having a quiet outage

This is the most common cause and the hardest one to diagnose without tooling. Your WiFi connection to the router is fine — full bars, fully associated. But the link from your router to the internet has gone dead. You see "Connected" in the menu bar; you also see "We can't reach Google.com" everywhere.

The decisive signal: WiFi itself stays connected, but internet is unreachable. Apple's Network framework (NWPathMonitor) detects this — it distinguishes "WiFi associated" from "internet reachable" and reports them separately. A good WiFi monitor will surface the difference. SignalDrop labels this state explicitly: "Internet: Unreachable" while the SSID still shows as connected.

The fix: nothing on your end. The fix is your ISP. The leverage is having data — timestamps and durations of every outage — to argue with their support team. Without data, the conversation usually ends with "we ran a line test and everything looks fine."

2. Your router is rebooting itself silently

Consumer routers reboot themselves more often than you'd expect. Some firmware schedules a nightly restart. Others crash and recover. Either way, you lose WiFi for 30-90 seconds, your Mac reconnects automatically, and you never knew anything happened — except your meeting drops at the exact same time every Tuesday.

Diagnostic: look for disconnects that cluster at predictable times of day. A reliability log binned by hour-of-day surfaces this fast. SignalDrop's per-network reliability tracking aggregates uptime per SSID and shows the pattern over time.

The fix: replace the router, update its firmware, or disable scheduled reboots in its admin panel.

3. Channel interference from neighbors

If you live in an apartment building, your 2.4 GHz WiFi is competing with ten of your neighbors' 2.4 GHz WiFi. Same physical spectrum, overlapping channels, mutual signal degradation. Older devices that only support 2.4 GHz suffer most. Even newer 5 GHz networks can suffer if too many access points are crowding the same channel.

Diagnostic: your WiFi works at 2 AM and degrades during the day when neighbors are home. A signal-strength log over time exposes the pattern. (Tooling for this — nearby-network scanning and channel-occupancy graphs — is a planned feature in SignalDrop v1.1; for now, dedicated scanners like WiFi Explorer can survey your channel environment.)

The fix: switch your router to 5 GHz (or 6 GHz if Wi-Fi 6E-capable), or manually change channels in the router admin panel to one less crowded.

4. Roaming between BSSIDs of the same SSID

If you have mesh WiFi or multiple access points broadcasting the same network name, your Mac roams between them as you move around the house. Sometimes the handoff is graceful. Sometimes it isn't — you get a brief disconnect during the swap.

Diagnostic: disconnects correlate with you physically moving (walking from desk to kitchen, etc.). The BSSID (router MAC address) changes even though the SSID (network name) stays the same.

The fix: enable 802.11k/v/r fast-roaming features in your router admin panel if supported. Apple's "Recommended Settings for Wi-Fi" page documents which settings Macs prefer; the most important is enabling 802.11r for fast BSS transitions.

5. The dead-saved-network trap

You're at a café. Your Mac auto-connects to a saved network — maybe the café's old router, maybe a hotspot you used once last year. It shows full bars. It looks fine. But the network has no internet. It's dead.

macOS lets you escape only by forgetting the network — deleting it from your saved networks list entirely. Next time you visit and it actually works, you have to re-enter the password. So you don't forget it; you just suffer.

Diagnostic: you're connected to a known-flaky network, with full signal, but Safari shows "We can't reach this site" everywhere. Internet reachability is false; WiFi is true. Same pattern as cause #1, different culprit.

The fix: manually disconnect from the bad network (without forgetting it), force-join a different one. Or wait for SignalDrop's Pro tier, which will eventually offer automatic dead-network leave-and-rejoin via the unsandboxed build path.

6. macOS sleep/wake cycles break the WiFi subsystem

This one is technical but real. macOS's CoreWLAN framework — the API that delivers WiFi event notifications — sometimes stops delivering callbacks after the Mac sleeps and wakes. Your app still thinks it's connected, but it's not getting updates. The status display goes stale. You see "Connected to HomeWiFi" when you're actually on Café-WiFi.

This affected SignalDrop's own 1.0.1 release. Fixed in 1.0.2 by re-registering CoreWLAN event monitoring on every NSWorkspace.didWakeNotification, plus a periodic 30-second self-heal that polls currentState() regardless of whether events have fired.

The fix: install SignalDrop 1.0.2 or later. If you're seeing a stale SSID in a different tool, the tool likely has the same bug.

7. Physical environment

Distance from the router. Walls (concrete is worst, drywall is fine). Microwaves running on 2.4 GHz. USB 3.0 devices and their cables, which produce broadband interference in the 2.4 GHz range. Bluetooth headsets competing for spectrum.

Diagnostic: drops correlate with specific physical events (running the microwave, plugging in a USB 3.0 drive, walking behind a thick wall).

The fix: situational. Move the router or your Mac. Switch to 5/6 GHz. Use shielded USB cables. None of this is fun, but it's all solvable once you know the trigger.

How to figure out which one is yours

The diagnostic process is the same regardless of cause: collect data over a multi-day window, then look for patterns.

The minimum useful data per outage:

• Timestamp (so you can correlate with what you were doing)
• Duration (a 5-second blip vs a 90-second outage points at different causes)
• Whether WiFi itself dropped, or just internet (cause #1 vs all others)
• SSID and BSSID (to detect roaming, dead saved networks)
• Signal strength at time of failure (cause #3 and #7 indicators)

You can collect this manually with terminal commands (a continuous ping 8.8.8.8 with timestamps, plus airport -I samples on a cron job) — or you can install SignalDrop, which collects all of this automatically and gives you a per-network reliability scorecard.

How to prove it to your ISP without them brushing you off

ISP support chats follow a predictable script: confirm your modem is online, run a line test, conclude that everything is fine on their end, suggest you reboot your router, threaten a $90 truck-roll fee. The asymmetry: they have all the data; you have a vague memory that your call froze around 2 PM.

To break out of that, paste evidence into the chat before they ask. The format that works:

Past 7 days: 19 disconnects, 48 minutes total downtime.
3 outages today:
  9:47 AM (1m 12s) — WiFi held, internet unreachable
  11:23 AM (45s) — WiFi held, internet unreachable
  2:14 PM (2m 8s) — WiFi held, internet unreachable
Pattern: outages cluster between 2-3 PM and 8-9 PM.
Connection quality grade: D.

This format makes three things obvious: there's a pattern (their problem, not your router), the WiFi itself isn't dropping (definitively their fault), and there's a quantitative grade you're prepared to escalate.

SignalDrop's Copy Receipt for Support menu item (⇧⌘C) generates exactly this format in one click. The receipt goes straight into your clipboard, paste-ready for any ISP chat or support email.

When the fix isn't software

If after a week of logging the pattern is clear and the cause is hardware or environmental, you have your answer. New router, mesh system, different physical location for the access point, or in some cases switching ISPs. Software monitoring only takes you so far — it tells you what's happening, not how to fix it.

But the data itself is invaluable. With it, every conversation — with an ISP, with Apple, with a network installer — starts from concrete reality rather than from someone trying to gaslight you about whether the problem exists.

Roadmap for SignalDrop in this domain

SignalDrop's feature roadmap is built around making the diagnosis easier:

• v1.1: Nearby network scanner + real-time signal/noise graphs (so you can see channel crowding visually)
• v1.5: AP vendor identification + roaming notifications (so cause #4 is obvious)
• v2.0: Channel-conflict detection + 802.11 information-element decoding (so cause #3 has an automatic "switch to channel X" recommendation)

All 1.x updates included free for existing buyers. Mac App Store grandfathers prices for buyers across version bumps.