Co-channel contention
Access points that hear each other on the same channel split one channel's airtime between them, and wide channels make that more likely because there are fewer channels to go around.
On this page5 sections
Is this your problem? It presents like this
- High channel utilization across an area even where each access point has few clients.
- Many access points heard on the same channel at a usable level from one spot.
- Problems got worse after access points were added, power was raised, or channels were widened.
- Worse at peak shift, with latency tails growing before throughput drops.
- 2.4 GHz and wide 5 GHz channels suffer most.
- Family
- Airtime saturation
- Bands
- 2.4 GHz5 GHz5 GHz DFS
Why it happens
Every Wi-Fi radio defers to the radios it hears on its channel. One vendor’s radio resource documentation calls this same channel contention, from other access points and clients on the same channel. When two cells hear each other, a vendor design guide for EtherNet/IP notes that the available bandwidth is shared between the cells. A high-density design guide from another vendor puts it plainly: adding access points on the same channel with overlapping coverage does not increase capacity.
Wide channels make clean reuse harder. An 80 MHz channel is four 20 MHz channels1, so moving to 40 or 80 MHz halves or quarters the number of non-overlapping 5 GHz channels2. The industrial design guide advises against channel bonding because wider channels consume the available bandwidth without improving EtherNet/IP performance. Control traffic uses small packets; it gains little from width and loses a lot from waiting.
Power works the same way. NIST notes that more transmit power may lower the performance of devices on adjacent networks in the same band, and the design guide recommends turning power down from maximum to minimize co-channel interference. 802.11ax adds BSS coloring, which lets a radio apply a higher deferral threshold to frames from other cells. It relaxes contention; it does not remove it. The cure is more channels and less overlap, not more access points.
5 GHz Wi-Fi channels in the US, 20 MHz wide
16 of 25 channels must listen for radar and leave when they hear it. 9 carry no DFS requirement.
Channel center frequency is 5000 + 5 × channel number MHz. U-NII-2A (5.25 to 5.35 GHz) and U-NII-2C (5.47 to 5.725 GHz) carry the DFS requirement; channel 144 straddles 5.725 GHz, so part of it falls in a DFS band. The rules list no Wi-Fi band between 5.35 and 5.47 GHz. Channels above 165 are not shown. Rules differ by country; this is the US.
Source: 47 CFR 15.407.
How to confirm it
- From the affected area, list every access point you can hear on the client's channel, including your own, with signal levels.
- Count how many share each channel within range, and compare utilization with the client load each one carries.
- Check channel width and transmit power settings against the design.
- Look for recent changes, such as added access points, raised power, widened channels, or automatic channel changes.
The fix
- Narrow the channels so more independent channels fit in the band.
- Reduce transmit power so access points on the same channel hear each other less.
- Disable radios that add overlap without adding coverage you need.
- Rebuild the channel plan so access points on the same channel are as far apart as possible.
- Use 6 GHz where clients support it, to gain channels.
Prevent it at design time
- Plan channel reuse and widths at design time, and validate overlap from the client's position.
- Use 20 MHz channels for control traffic unless a measured need justifies more.
- Re-check co-channel overlap after any change that adds radios or raises power.
About this page
Built from 6 sources: 1 standards body or lab 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. "Co-channel contention." OT Wireless, published October 5, 2026. https://otwireless.com/causes/co-channel-contention/
APA 7
Rutter, B. (2026, October 5). Co-channel contention. OT Wireless. https://otwireless.com/causes/co-channel-contention/
BibTeX
@misc{rutter2026cochannelcontention,
author = {Rutter, Ben},
title = {{Co-channel contention}},
year = {2026},
howpublished = {\url{https://otwireless.com/causes/co-channel-contention/}},
organization = {OT Wireless},
}