Keep subscribers happy at busy hour without overbuilding the backhaul
Wireless capacity is expensive and shared. LibreQoS keeps every AP, tower, and backhaul fair and responsive as it fills up, so gaming and video calls hold up at 8pm, upgrades happen when they are needed, and support can tell a busy AP from a problem in the home.
Illustrative download limits, not sizing recommendations. Active circuits compete within each configured parent limit, even when their individual plan rates add up to more.
- 01Backhaul: 500 Mbps
An explicit limit on this part of the configured path.
- 02Tower: 300 Mbps
An explicit limit on this part of the configured path.
- 03Access point: 200 Mbps
An explicit limit on this part of the configured path.
- 04Competing circuits: 100 Mbps each
CAKE manages competing flows within each circuit.
Get more out of every backhaul and AP
Nest subscriber circuits beneath AP, site, and backhaul limits. When a branch fills up, congestion stays contained in that branch and is managed fairly, instead of spreading latency to everyone upstream.
- Set capacity at each shared parent
- Inspect configured and effective limits
- Keep the rest of the hierarchy in view
Keep gaming, calls, and streaming smooth at busy hour
Per-circuit CAKE separates competing flows, so one household's download does not make their video call freeze or their game lag, while the parent hierarchy holds the shared link to what it can actually deliver.
- CAKE fairness inside each circuit
- Subscriber min/max rates from your source of truth
- Queue and throughput evidence during busy hour
Know whether it's the AP, the tower, or the home before you roll a truck
Start with the affected site, compare its children, and open the subscriber circuit. RTT, retransmits, and utilization together show whether the problem is shared congestion or local to one subscriber.
- Compare RTT and retransmits with utilization
- Inspect the circuit and its upstream path
- Use Insight history to check when the pattern began
Local operator console
Check the parent, then follow its circuits
Compare configured and effective limits with live quality signals. Follow the affected branch into circuit investigation, then use Insight history when the problem has already passed.

Walkthrough
See the wireless ISP workflow in practice
These views show topology, map, and tree context that help WISPs locate congestion and support issues faster.
Plan your pilot
Put the workflow to work
Validate LibreQoS on your network
Start with one tower or a few APs. Compare busy-hour latency, retransmits, and Internet Quality Test grades before and after, and watch whether complaint calls from that area change. Then expand.

