How to Detect Wi-Fi Channel Interference on a WISP Network

A customer calls in: their connection is “slow” or “laggy,” especially in the evening. The link shows up in your monitoring. Ping still works. CPU and memory on the radio look fine. Nothing paged you. This is the classic shape of an interference problem, not a hardware failure — and it's exactly the gap most legacy desktop dashboards leave open, because they track signal and link state but not the spectrum itself.

Co-channel interference happens when two of your own sector APs at the same (or a nearby) site are assigned the same or overlapping 20MHz channel. Both radios hear each other's traffic as noise, CCQ drops on both, and it gets worse the more clients each one carries.

Adjacent-channel / external interference comes from anything else transmitting in or near your band — a competitor's gear, a consumer router near a client site, or non-Wi-Fi noise. This shows up as a rising noise floor on specific channels without a clean one-to-one match to another AP of yours.

The traditional fix is a handheld or software-defined spectrum analyzer at the site, scanning the 5GHz band for noise floor and occupancy per channel. It works, but it means a truck roll and a tech on a ladder — reactive, not preventive, and it tells you nothing about the other 40 sites you're not standing at.

A monitoring platform that already tracks every radio's assigned channel, noise floor and CCQ can do the correlation for you continuously. TowerLens's Spectrum tab buckets every radio by frequency fleet-wide, flags any site where two or more sector APs land on the same channel, and shows the channel plan per site at a glance — so you catch the conflict when you deploy a third AP at a site, not three weeks later when the complaints start.

Pair that with the per-AP client roster to see which specific CPEs are actually struggling (low CCQ, high retry rate) versus riding the same channel without issue — not every co-channel conflict is equally bad in practice, and the roster tells you who to prioritize.

• Re-plan the site's channel assignment so same-site APs don't overlap — a 2-channel-per-site pool is usually tighter than it needs to be; 3+ clean channels per site is the real target where spectrum allows.
• Check polarity/antenna isolation on sector antennas pointed at each other.
• For external interference, narrow the channel width (e.g. 20MHz instead of 40MHz) to dodge a noisy neighbor rather than fighting it head-on.
• Re-scan after any change — interference sources move (new neighbor gear, seasonal foliage, new construction).