How to Identify AWDL Spikes on Mac (And Why They Kill Your Connection)

What Is AWDL? (Apple Wireless Direct Link)

AWDL is Apple's proprietary peer-to-peer wireless protocol. It first appeared with iOS 7 in 2013 and came to the Mac with OS X Yosemite in 2014, enabling cross-platform AirDrop between iOS and macOS for the first time. It powers AirDrop, AirPlay discovery, Sidecar, Universal Control, and Handoff. Basically, anything where Apple devices need to discover and communicate with each other without going through a router.

The concept makes sense: you want to AirDrop a photo to the MacBook sitting next to you. Rather than routing that file through your Wi-Fi router (or requiring an internet connection at all), AWDL creates a direct peer-to-peer link between the two devices. It's clever engineering that makes the Apple ecosystem feel seamless.

Technically, AWDL operates on a separate virtual network interface (awdl0) that shares the same physical Wi-Fi radio as your main connection. You can see this interface in Terminal by running ifconfig awdl0. It appears as a distinct network interface with its own IPv6 address, but it isn't a separate piece of hardware. This is the key detail that explains everything that follows.

The fundamental design choice: your Mac has only one Wi-Fi radio. Unlike enterprise laptops that sometimes have dual radios, every MacBook and iMac ships with a single Wi-Fi chip. To listen for nearby AWDL peers, your Mac must temporarily leave your current Wi-Fi channel and hop to the AWDL “social channels”: typically channel 6 on 2.4 GHz and channels 44 or 149 on 5 GHz (channel 149 is preferred in the US; channel 44 in the EU and other regions where UNII-3 channels may be restricted). These are fixed, well-known “social channels” that all Apple devices agree to use for peer discovery.

This channel hop happens periodically, roughly every 15–30 seconds when AWDL is “idle” but still listening, and much more frequently (multiple times per second) during an active AirDrop transfer. The hop duration varies, but each one takes your radio off your router's channel for approximately 50–100 milliseconds.

During each hop, your Mac is off your router's channel. Any packets your router tries to send during that window are missed. Any packets your Mac tries to send go nowhere. Your router doesn't know your Mac briefly disappeared. It may retry the packets, adding latency, or they may be lost entirely. From the router's perspective, your Mac just momentarily stopped responding, as if it had walked out of range and back again.

What Triggers AWDL Scanning?

AWDL doesn't run at full speed all the time. Its scanning behavior ramps up and down depending on what your Mac (and nearby devices) are doing:

• Idle scanning (15–30 second intervals): When no AWDL-dependent features are actively in use, macOS maintains a low-frequency scan to stay aware of nearby peers. This is the baseline behavior most users experience.
• Active discovery (multiple times per second): When you open the AirDrop panel in Finder, initiate an AirPlay connection, or use Sidecar, AWDL switches to high-frequency scanning to quickly discover available devices.
• Data transfer (continuous): During an actual AirDrop file transfer, AWDL maintains a near-constant presence on the social channel to sustain the peer-to-peer data link.
• Handoff awareness (periodic): When Handoff is enabled, your Mac periodically checks for activity on nearby devices. This happens even when you're not actively using Handoff, yet your Mac is always listening for the possibility.

Even the idle scanning mode is enough to cause noticeable latency spikes. The 15–30 second interval means your connection is disrupted roughly 2–4 times per minute, every minute, for as long as AWDL is active.

How AWDL Disrupts Your Wi-Fi

To understand why AWDL causes problems, consider what happens at the radio level during a single channel hop:

1. Your router broadcasts on, say, channel 36 (5 GHz). Your Mac is connected and communicating normally on this channel.
2. AWDL needs to listen on channel 149 (the 5 GHz social channel). Your Mac's radio switches from channel 36 to channel 149.
3. Your Mac listens on channel 149 for approximately 50–100ms, scanning for nearby Apple devices advertising their presence via AWDL availability windows.
4. During that switch: packets from your router arrive on channel 36, but your Mac's radio is tuned to channel 149. The packets are simply not received. They dissipate into the air unheard.
5. Your router doesn't know your Mac briefly disappeared. Depending on the router's retry logic, it may retransmit the missed packets (adding latency) or give up after a timeout (causing packet loss).
6. Your Mac switches back to channel 36 and resumes normal operation, until the next AWDL scan window, roughly 15–30 seconds later.

The result: periodic latency spikes of 50–200ms, occurring at regular intervals. On a latency graph, like Healthy Network's sparkline, this appears as a distinctive “comb” pattern: a sharp spike every 15–30 seconds against an otherwise flat baseline.

Think of it like briefly tuning your car radio to a different station. While you're on the other station, you miss whatever is playing on the original one. When you switch back, the music continues normally, but you've lost a few seconds of audio. AWDL does this to your Wi-Fi data stream, except instead of missing music, you're missing network packets.

What makes this particularly frustrating is that your Mac still shows full Wi-Fi signal strength during an AWDL hop. The Wi-Fi icon in the menu bar doesn't flicker. No notification appears. From the user's perspective, nothing is wrong. The connection is “fine.” But underneath the surface, your radio is spending 50–100ms out of every 15–30 seconds on the wrong channel. That's a small percentage of total time, but it's enough to disrupt any real-time protocol that depends on consistent, low-latency packet delivery.

The severity depends on several factors:

• How often AWDL scans: More nearby Apple devices means more frequent scanning. In an office with a dozen iPhones and MacBooks, AWDL may scan nearly continuously. Each additional peer increases the time your Mac spends on the social channel.
• Whether your router uses a DFS channel: Dynamic Frequency Selection channels (52–144 on 5 GHz) may compound the issue. If the access point detects radar and broadcasts a Channel Switch Announcement (CSA) while your Mac's radio is on the AWDL social channel, your Mac may miss the CSA frame and temporarily lose its infrastructure connection until it rescans.
• Your Wi-Fi band: 5 GHz connections are more susceptible because the AWDL social channel (149) is also on 5 GHz. When both your infrastructure connection and AWDL are on the same band, the radio contention is more direct. If your router uses channel 149 itself, the conflict is reduced, but this is rare in practice.
• Active AWDL sessions: During an AirDrop transfer, AWDL switches channels multiple times per second, turning occasional spikes into sustained disruption. A colleague sending a large file via AirDrop nearby can degrade your connection for the entire duration of their transfer.
• Your router's distance: When you're far from your router and signal is already marginal, the packet loss caused by AWDL hops is compounded. The router may already be retransmitting packets due to weak signal, and AWDL hops add additional missed frames on top of that.

The Telltale Pattern

The key diagnostic clue is regularity.

Normal Wi-Fi interference is random: spikes appear at irregular intervals with varying magnitudes. Microwave ovens cause bursts when running. Neighboring routers cause sporadic collisions. Bluetooth devices create occasional noise. Someone downloading a large file on your network causes temporary congestion. None of these produce a predictable, repeating pattern.

AWDL spikes are periodic, like a heartbeat. If you see a latency spike every 15–30 seconds with near-identical intervals between them, AWDL is almost certainly the cause. The spikes are remarkably consistent: same interval, same approximate magnitude, same sharp rise and fall. This regularity is what makes AWDL interference uniquely identifiable among all types of Wi-Fi disruption.

On a monitoring graph, the pattern looks unmistakable: a flat baseline at ~5–20ms with sharp spikes to 100–200ms at regular intervals. The spikes are narrow (50–100ms wide) and tall, standing out clearly against the stable baseline. It resembles the teeth of a comb: regular, evenly spaced, and uniform in height.

Here's how to distinguish AWDL spikes from other common interference patterns:

• Random spikes at varying intervals: Wi-Fi congestion from neighboring networks. No regular pattern. Spikes appear whenever another network transmits on the same or overlapping channel.
• Spikes every 1–5 seconds during cooking: Microwave oven interference on 2.4 GHz. Stops immediately when the microwave turns off.
• Spikes every 15–30 seconds, clockwork regularity: This is the AWDL signature. Consistent intervals regardless of time of day or network load.
• Gradual latency increase under heavy use: Bufferbloat. Latency rises proportionally with traffic volume rather than spiking at fixed intervals.

If you have multiple Apple devices nearby (an iPhone, iPad, Apple Watch, or another Mac), the scanning frequency increases because AWDL tries to maintain awareness of all nearby peers. Each device advertises its presence on the social channel, and your Mac needs to be there to hear them. With more peers, the availability windows become more frequent and the idle scan interval shrinks.

In a coffee shop or office with many Apple devices, AWDL scanning can become nearly continuous. The 15–30 second idle interval shrinks as more peers are detected, and what was an occasional spike becomes a persistent pattern of elevated, variable latency. This is why “my internet is worse at the office than at home” is a common complaint, and it's not the office Wi-Fi. It's the density of Apple devices around you.

How to Confirm AWDL Is the Cause

Step 1: Look for the Pattern

Use a continuous latency monitor and watch for regular spikes. You can use Terminal's built-in ping command or a dedicated monitoring tool like Healthy Network.

In Terminal, run:

The -i 0.5 flag pings every 0.5 seconds instead of the default 1-second interval. This resolution is important. At 1-second intervals, you can miss the short AWDL spikes entirely because the ~80ms disruption may fall between samples and go completely undetected. Half-second intervals give you enough resolution to catch them reliably.

You'll see output like this when AWDL is active:

Notice the pattern: ~12ms baseline with a single spike to ~150ms every 30 seconds. That periodic spike is the AWDL channel hop.

Watch for 2–3 minutes. If you see spikes repeating at regular ~15–30 second intervals, proceed to Step 2.

Step 2: Check the AWDL Interface

Open a new Terminal window (keep your ping running in the first one) and run:

If AWDL is active, you'll see output like this:

The important line is status: active. This confirms the AWDL virtual interface is up and your radio is periodically hopping to the social channel. The inet6 address with the fe80:: prefix is the link-local IPv6 address used for AWDL peer communication.

If it shows status: inactive, AWDL is not currently running, but it can reactivate at any time when an app or system service requests peer discovery. Opening a Finder window, for example, can trigger AWDL activation because Finder displays AirDrop in the sidebar.

Step 3: The Disable Test

This is the definitive, conclusive test. Disable AWDL temporarily and see if the spikes stop.

You'll be prompted for your admin password. Once entered, the AWDL interface is immediately disabled.

Keep your ping running in another Terminal window. If the regular spikes immediately disappear and latency drops to a flat, consistent line, AWDL was the cause. The before-and-after difference is usually dramatic: a saw-tooth pattern with regular 100–200ms spikes transforms into a flat line at 10–15ms. This is the most conclusive test you can perform.

Re-enable AWDL when you're done testing:

Watch the ping output after re-enabling. You should see the periodic spikes return within 30–60 seconds as AWDL resumes scanning. This confirms the causal relationship definitively.

Note: Disabling AWDL stops AirDrop, Handoff, Universal Control, and Sidecar. These features will resume when you re-enable AWDL or after a reboot. macOS may also re-enable AWDL automatically if an app requests peer discovery. For example, if another app opens a Finder window with AirDrop in the sidebar, or if you invoke Sidecar.

Step 4: Use Wireless Diagnostics (Advanced)

Hold Option and click the Wi-Fi icon in the menu bar, then select “Open Wireless Diagnostics.” (Note: Apple has been deprecating parts of this tool in recent macOS versions, so availability may vary depending on your macOS version.)

Go to Window → Performance. This shows real-time signal strength, noise floor, and data rate for your Wi-Fi connection. During an AWDL channel hop, you may see a brief dip in data rate and signal-to-noise ratio as your radio momentarily leaves the infrastructure channel.

You can also check Window → Scan to see which channels nearby networks are using. If your router is on a 5 GHz channel far from channel 149, the AWDL hop requires a larger frequency shift, which can slightly increase the disruption duration. This is informational, and you generally can't avoid the issue by choosing a specific channel, since AWDL always hops to the fixed social channels regardless of your infrastructure channel.

When AWDL Matters Most

Not every use case is equally affected by AWDL's periodic channel hops. Browsing the web, for example, is largely unaffected. A 100ms spike during a page load just means one resource takes slightly longer, and you'd never notice. But real-time and high-throughput applications tell a different story.

Here's where the impact is most noticeable:

Music streaming (Spotify, Apple Music) and video streaming (Netflix, YouTube) are generally not affected because they buffer several seconds ahead. A 100ms spike every 30 seconds is easily absorbed by the buffer. However, live streaming (Twitch, OBS) is a different matter. Outbound stream data is latency-sensitive, and periodic packet loss can cause visible frame drops for your viewers.

SSH sessions and remote desktop connections (VNC, Parsec, Remote Desktop) fall somewhere in between. You'll notice the periodic spike as a brief input lag, where your keystrokes arrive slightly late every 30 seconds. For general remote work this is tolerable, but for latency-sensitive tasks like remote pair programming or live demos, it can be frustrating.

How to Fix AWDL Interference

Now that you've confirmed AWDL is causing your latency spikes, here are five approaches to fix it, ordered from least disruptive to most effective. Most users find that Option 1 and Option 2 together resolve the issue sufficiently. If you need rock-solid latency, Option 3 (Ethernet) is the gold standard.

Option 1: Disable AirDrop When Not in Use

This is the simplest and most effective first step. Open System Settings → General → AirDrop & Handoff → AirDrop and set it to “No One.”

This significantly reduces AWDL scanning frequency, though it may not eliminate it entirely, since Handoff and Universal Control can also trigger AWDL activity. The awdl0 interface may still activate periodically even with AirDrop disabled, because macOS uses AWDL for several background services beyond just file transfer.

You can also disable AirDrop from Control Center: click the Control Center icon in the menu bar, click AirDrop, and select “No One.” This is faster than navigating through System Settings when you need to toggle it frequently.

Best practice: Leave AirDrop on “No One” by default and switch to “Contacts Only” when you actively need to receive a file. Once the transfer is complete, switch it back. The “Everyone” setting should be avoided entirely, as it causes maximum AWDL scanning activity and also exposes you to unsolicited file sharing from strangers.

Option 2: Disable Handoff

Handoff is the feature that lets you start an email on your iPhone and continue writing it on your Mac, or copy text on one device and paste on another via Universal Clipboard. It's genuinely useful, but it relies on AWDL to maintain constant awareness of nearby devices.

If you don't regularly use the “continue on another device” feature, disabling Handoff will further reduce AWDL scanning activity.

Open System Settings → General → AirDrop & Handoff and toggle off Handoff.

Combined with disabling AirDrop, this dramatically reduces AWDL activity. With both features off, AWDL has far fewer reasons to scan, and the periodic channel hops become rare or stop entirely. Universal Control (using a single keyboard and mouse across multiple Macs) will also stop working, since it depends on the same peer discovery mechanism.

Option 3: Use Ethernet

An Ethernet connection (via a USB-C to Ethernet adapter) bypasses Wi-Fi entirely. AWDL only affects the Wi-Fi radio. Ethernet traffic is completely unaffected by channel hopping because it uses a separate, dedicated physical interface. AWDL will continue to run on the Wi-Fi radio in the background, but your data flows through the Ethernet port untouched.

This is the definitive fix for situations where you absolutely need stable latency: important video calls, competitive gaming, live streaming, or any latency-critical work. A basic USB-C to Gigabit Ethernet adapter costs $15–$25 and eliminates AWDL interference completely. Our Ethernet vs. Wi-Fi 6E latency comparison shows just how dramatic the difference is.

When you plug in Ethernet, macOS automatically prioritizes it over Wi-Fi for internet traffic. You don't need to disable Wi-Fi. macOS routes data through the wired connection while keeping Wi-Fi active for AWDL and local services. You can verify this by checking System Settings → Network and confirming that Ethernet appears at the top of the service order.

Bonus: Ethernet also eliminates all other Wi-Fi variables: interference from neighboring networks, distance from your router, channel congestion, signal attenuation through walls, and contention from other devices sharing the same access point. It's the single most effective network upgrade you can make for connection stability.

Option 4: Terminal Kill Switch

For power users who need temporary relief during a critical call or gaming session:

Remember: this disables AirDrop, Sidecar, Universal Control, and Handoff until AWDL is re-enabled. macOS will re-enable AWDL after sleep/wake, reboot, or if an app requests peer discovery. This is not a persistent setting. It's a session-level change that resets whenever the system state changes.

You could create a simple shell script to toggle AWDL before and after important calls or gaming sessions:

Option 5: Reduce Nearby Apple Devices

AWDL scans more frequently when more Apple devices are detected nearby. Each device advertising on the social channel prompts your Mac to spend more time listening and maintaining peer awareness.

In an office environment, moving your iPhone away from your Mac (or putting it in a drawer or bag) can noticeably reduce AWDL scanning frequency. Your Apple Watch, if worn on your wrist near the keyboard, is also a constant AWDL peer that your Mac monitors continuously.

You can also disable AirDrop on your iPhone and iPad (Settings → General → AirDrop → Receiving Off) to reduce the number of devices advertising on the AWDL social channel. Even if your Mac still scans, there are fewer peers to discover, which means the scans can be shorter and less frequent.

This isn't practical for most people as a permanent solution, but it explains a common mystery: why “my connection is worse at the office than at home.” At home, you might have 2–3 Apple devices within radio range. In an open-plan office, there could be 30–50. Your Mac's AWDL scanning ramps up proportionally, and the cumulative interference becomes significant.

The Bigger Picture: Wi-Fi Coexistence on macOS

AWDL is just one of several background Wi-Fi activities that macOS performs without your knowledge. Each one is individually minor, but cumulatively they create noticeable latency variability:

• Location Services Wi-Fi scanning: macOS periodically scans nearby Wi-Fi networks to help determine your physical location (Macs lack GPS hardware and rely on Wi-Fi positioning). These scans briefly take your radio off-channel to listen on adjacent frequencies, similar to AWDL but less frequent.
• Wi-Fi roaming scans: macOS periodically checks if a stronger access point is available on a different channel. This is especially aggressive in environments with multiple access points (offices, universities, airports) where macOS sees many potential networks to connect to.
• Bonjour/mDNS multicast traffic: Device discovery for printers, AirPlay speakers, and other network services generates periodic multicast bursts that consume airtime and can cause brief latency increases. Every Apple device on your network is broadcasting these discovery packets.
• iCloud Private Relay / Limit IP Address Tracking: These privacy features route traffic through Apple's relay infrastructure, adding additional network hops and latency to every connection. See our Sequoia network drops article for a deep dive on this issue.

These activities are individually minor but cumulatively can cause noticeable latency variability. On a perfectly configured home network with a nearby router and no interference, you might measure 5ms average latency over Ethernet. Over Wi-Fi on the same network, the average might be 12ms, but with periodic spikes to 150ms or more from AWDL and other background scanning. The average looks fine. The spikes are what kill real-time applications.

The challenge: monitoring tools that only sample once every 30–60 seconds completely miss these sub-second disruptions. By the time the next sample is taken, the spike is over and the connection looks fine. A speed test that runs for 10 seconds averages over multiple AWDL hops, masking the problem entirely. Your ISP's diagnostic tool shows 200 Mbps and 15ms latency, and everyone shrugs. Meanwhile, your Zoom call cuts out every 30 seconds.

This is why continuous, high-resolution monitoring matters. Healthy Network's burst sampling sends multiple probes in quick succession, catching short-lived disruptions that periodic monitors miss. When you see a regular pattern of spikes on the sparkline, you know something systematic is happening, and you have the data to prove it to your IT department, your ISP, or yourself.

The irony of AWDL is that it exists to make Apple devices work better together, and it does. AirDrop is genuinely faster and more convenient than any cross-platform file sharing solution. Sidecar lets you use your iPad as a second display wirelessly. Universal Control is magical when it works. But these conveniences come at a cost to your infrastructure Wi-Fi connection, and Apple has never surfaced this trade-off to users.

Until Apple ships Macs with dual Wi-Fi radios (one for infrastructure and one for peer discovery), AWDL interference will remain an inherent characteristic of macOS Wi-Fi. Understanding it is the first step to managing it. Measuring it is the second.

Frequently Asked Questions