Fiber ISPs

Make fiber feel as fast as it tests, and resolve "slow internet" calls faster

Fiber subscribers expect gigabit to feel instant, even when the PON or uplink is busy. LibreQoS keeps shared fiber capacity fair and responsive, and gives support the evidence to tell network congestion from a subscriber-side issue in minutes.

Give the shared bottleneck its own limit

Illustrative download limits, not sizing recommendations. Active circuits compete within each configured parent limit, even when their individual plan rates add up to more.

  1. 01Shared uplink: 2 Gbps

    An explicit limit on this part of the configured path.

  2. 02OLT / PON parent: 1 Gbps

    An explicit limit on this part of the configured path.

  3. 03Competing circuits: 300 Mbps each

    An explicit limit on this part of the configured path.

  4. 04Flow queues within each circuit

    CAKE manages competing flows within each circuit.

Keep busy PONs and uplinks responsive

Represent each PON and uplink in the hierarchy so shared capacity has an explicit limit. When demand peaks, latency stays controlled instead of building up in queues that subscribers feel as lag.

  • Explicit limits above the subscriber
  • Topology matched to your integration
  • Throughput and queue context together

Deliver the plan subscribers pay for, gaming and video calls included

Enforce each plan and keep per-flow fairness inside the circuit, so a large download or backup in one home does not make that same home's calls and games stutter.

  • CAKE queue management
  • Per-circuit minimum and maximum rates
  • Evidence of queue pressure under load

Is it the network or the home? Answer before the truck roll

Compare the affected subscriber with the parent branch and neighboring circuits. If neighbors are fine and the branch is quiet, the next check is the home network or optics, and you have the evidence to say so.

  • 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.

LibreQoS Network Tree: configured and effective limits, live throughput, RTT, QoO, and child node queue metrics
Actual LibreQoS Network Tree. This product view illustrates the workflow; the capacity example above is separate. · Open full-size product view ↗

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.

Insight timeline
Insight timeline
LibreQoS executive heatmap
LibreQoS executive heatmap

Plan your pilot

Put the workflow to work

Deploy

Validate LibreQoS on your network

Start with a single OLT or PON group. Compare busy-hour latency, retransmits, and Internet Quality Test grades before and after, and track how quickly support closes "slow internet" tickets. Then expand.