Skip to main content

See who is using the network, and slow a line when it should be.

A few heavy users shouldn't slow everyone else, and you shouldn't learn about them from the complaints.

Try the live demo

Works with

  • PPPoE and hotspot customers
  • RADIUS accounting
  • MikroTik RouterOS rate limits

Most of the traffic comes from a few lines

Heavy users are rarely a surprise. The surprise is how late you hear about them. By the time customers complain that evenings are slow, the biggest lines have been running hot for weeks, and the evidence is a router graph that nobody tied to a name.

A fair-use rule is easy to write down and hard to apply. Someone has to know how much each customer has used since the cycle began, notice who has passed the limit, slow them down, and remember to undo it when the cycle starts again. Done by hand, it happens when somebody has time.

P8 ISP adds up each subscriber's usage from RADIUS accounting, compares it with the policy you set, and slows the line when the limit is passed. When the window resets, the slowdown is lifted. You can see every subscriber's state on one screen.

Usage & fair use: what it does

  • Usage for every subscriber

    Bytes in and out are added up from RADIUS accounting, for PPPoE and hotspot customers alike. See the current month by default, sort by the heaviest, and filter by minimum gigabytes. Usage that can't be matched to a subscriber is shown separately rather than spread around.

    See PPPoE lines →
  • A limit you define once

    A policy is a volume, a window in days, a start date and, if you want enforcement, a download and upload speed in Mbps. Each subscriber gets one policy, assigned from their page. It is set per subscriber, not per plan.

    See how plans are sold →
  • Slowed, not cut off

    Over the limit, the line moves to the speeds on the policy. The plan's own speed is never rewritten, so when the slowdown ends the customer returns to whatever the plan is now. Nothing is blocked, and a suspended or expired line stays exactly as it was.

    See what happens at expiry →
  • Checked every few minutes

    A scheduled check re-evaluates everyone on a policy, applies what's needed, and retries what fails. The enforcement screen shows each subscriber as within the limit, over it, throttle required, throttled, restore required or failed, so a stuck line is visible.

    See how outages are tracked →

Usage & fair use: how it works

  1. Write a policy

    Set the volume, the window in days, the start date, and the speeds a customer drops to once they pass the limit.

  2. Assign it to subscribers

    Open a subscriber and choose their policy. Their usage is compared with it from the next check.

  3. Watch it work

    Customers who pass the limit are slowed within a check or two. When the window resets, or you change the policy, the slowdown is lifted.

Enforcement is off by default and is switched on for your deployment. Measuring usage and writing policies work without it.

Usage & fair use: common questions

Does the customer get a message when they're slowed?

No. The fair-use checks send nothing of their own. The customer sees a slower connection and nothing else, so write the message yourself if you want them told.

When does a customer get full speed back?

When the window resets, or when you raise the limit, deactivate the policy or take it off the subscriber. A PPPoE customer reconnects briefly to pick the change up. A hotspot customer isn't cut off mid-use, so it takes effect the next time they log in.

Is the limit per plan?

No. Each subscriber has their own policy, and several subscribers can share the same one. Plans keep their own speeds.

What if a policy has no speeds?

The subscriber is shown as over the limit, but nothing is slowed. A policy needs a download and an upload speed to be enforced.

Does it count upload and download?

Both, added together.

Can it disconnect someone who passes the limit?

No. It slows them, nothing more. Suspension and expiry are separate, and fair use never changes them.

Set a limit once, and let the checks do the rest.

Try the live demo, or create an account and write a policy.