Trace a fiber complaint from the PON to the subscriber
Combine shared-capacity control with circuit-level evidence so support can investigate access congestion, upstream changes, and subscriber-specific symptoms.
Illustrative download limits, not sizing recommendations. Active circuits compete within each configured parent limit, even when their individual plan rates add up to more.
- 01Shared uplink: 2 Gbps
An explicit limit on this part of the configured path.
- 02OLT / PON parent: 1 Gbps
An explicit limit on this part of the configured path.
- 03Competing circuits: 300 Mbps each
An explicit limit on this part of the configured path.
- 04Flow queues within each circuit
CAKE manages competing flows within each circuit.
Control shared PON and uplink capacity
Represent shared fiber capacity in the hierarchy and nest subscriber circuits under the appropriate parent.
- Explicit limits above the subscriber
- Topology matched to your integration
- Throughput and queue context together
Preserve per-subscriber fairness
Keep per-flow fairness inside each circuit while enforcing the subscriber plan and the shared parent envelope.
- CAKE queue management
- Per-circuit minimum and maximum rates
- Evidence of queue pressure under load
Separate the scope of a support issue
Compare the affected subscriber with the parent branch and neighboring circuits. Correlate transport symptoms with your optical and home-network tools.
- RTT, retransmits, and Quality of Outcome (QoO)
- Local circuit investigation and Insight history
- Evidence for the next check, rather than an automatic optical diagnosis
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 how fiber operators move from symptom to subscriber context
These views show subscriber drill-down, timeline context, and heatmap patterns that help teams separate local issues from upstream trouble.
Plan your pilot
Put the workflow to work
Validate LibreQoS on your network
Start with a limited pilot, compare the same load conditions, and confirm the affected branch and circuit behavior before expanding.

