OT Wireless
Search/Menu

Search the field guide, causes, requirements, and glossary

Off-channel scanning gaps

A radio that leaves its channel to scan cannot carry traffic on it, so scanning by the client or by the access point opens short, repeating holes in the data stream.

Ben RutterIndustrial network engineer
  • Updated
  • Reviewed
  • 3 min read
  • 6 sources
On this page5 sections
  1. How it presents
  2. Why it happens
  3. How to confirm it
  4. The fix
  5. Prevent it at design time

Is this your problem? It presents like this

  • Short gaps or latency spikes, usually under a second, with no disconnect in any log.
  • Cyclic traffic shows late or missing packets at a steady rhythm, even while the device sits still.
  • The gaps get longer as the client's signal weakens and it starts hunting for a roam target.
  • When the access point is the one scanning, every client on that radio sees the same gaps at the same moments.
  • Devices that are intolerant of loss sometimes roam away or disconnect after one of these gaps.
Bands
2.4 GHz5 GHz5 GHz DFS6 GHz
Not sure?
Rank the likely causes from your symptoms

Why it happens

A Wi-Fi radio listens on one channel at a time. To find a roam target, the client has to visit other channels, and while it is away it carries nothing on its own. An early measurement study found the probe phase made up more than 90%1 of handoff delay in every access point and client pairing it tested. That was 802.11b hardware in 2003, so read the share as a direction, not a figure for today’s radios.

Clients scan the whole band unless the network helps. Apple devices check all available channels in 2.4 and 5 GHz plus the 6 GHz preferred scanning channels2, and without 802.11k neighbor reports that can add several seconds. Windows uses neighbor reports to shorten the list of channels it scans. Linux’s wpa_supplicant runs periodic background scans, more often once the signal falls below its threshold.

Vehicle software can expose the same knob. One AMR maker’s newer software replaces its older Wi-Fi watchdogs with a background scan frequency setting that sets how aggressively the robot looks for an access point with a stronger signal. The guide does not say whether the robot still scans while its own signal is strong. Ask your vehicle vendor whether the setting exists, what it defaults to, and what it costs in gaps.

The access point scans too. One vendor documents its access points leaving channel for about 80 ms every 3 to 20 seconds3 to feed radio management and monitoring, with 0.05% to 1.5% packet loss as the cost. Its default defers a scan only if it has seen traffic at user priority 4, 5, or 6 within the last 100 ms. Unmarked control traffic gets no protection.

The vendor calls the impact imperceptible for most clients, and for an office laptop it is. It also notes that some sensitive clients will roam away or disconnect after 80 ms without the access point. To a cyclic I/O connection with a short timeout, a scan is an outage that no log records.

How to confirm it

  1. Run a continuous short-interval ping, or capture the cyclic traffic, and log the timestamp of every late or missing packet.
  2. Check whether the gaps repeat at a regular interval and whether they hit one client or every client on the access point.
  3. With a second capture radio on other channels, look for probe requests from the client while it should be on its own channel.
  4. Check the access point's off-channel scanning settings for radio management, rogue detection, and spectrum monitoring, and whether scanning defers for prioritized traffic.
  5. Check the client's background scan settings and whether 802.11k neighbor reports are enabled on the SSID.

The fix

  • Enable 802.11k neighbor reports so clients scan a short list of channels instead of every channel.
  • Defer or disable access point off-channel scanning on radios that serve time-sensitive clients, and move monitoring to dedicated sensor radios if you need it.
  • Make sure time-sensitive traffic carries a priority marking that the access point's scan-defer feature honors.
  • Tune or disable client background scanning where the driver allows it, so scans start only when the signal falls below a threshold.

Prevent it at design time

  • Put scan gaps in the timing budget. Do not assume either radio is always on channel.
  • Ask client vendors how their scanning behaves while associated and whether it uses neighbor reports.
  • Decide at design time which radios scan and which only serve clients.

Related causes

Terms on this page

About this page

Built from 6 sources: 1 research paper or thesis and 5 vendor documents. Researched and drafted with AI assistance, then reviewed and approved by Ben Rutter on . How pages are made

First published
Last updated
Change history (1)
  • First published
Cite this page

Plain

Ben Rutter. "Off-channel scanning gaps." OT Wireless, published October 5, 2026. https://otwireless.com/causes/roam-scan-gaps/

APA 7

Rutter, B. (2026, October 5). Off-channel scanning gaps. OT Wireless. https://otwireless.com/causes/roam-scan-gaps/

BibTeX

@misc{rutter2026roamscangaps,
  author = {Rutter, Ben},
  title = {{Off-channel scanning gaps}},
  year = {2026},
  howpublished = {\url{https://otwireless.com/causes/roam-scan-gaps/}},
  organization = {OT Wireless},
}