A fair-usage policy (FUP) defines how an ISP changes service after a stated volume of data. A plan can keep internet access available while reducing the maximum speed. Calling it “unlimited” without displaying that reduction invites a dispute. Put the threshold, reduced speeds and reset date alongside the headline offer.
This is an operator design guide, not a feature announcement. ISPAgents automatic usage-based step-down planning is planned, not shipped. The MikroTik integration is a guided pilot; discuss the exact access path before committing to an offer.
Write the subscriber promise first
Use a concrete example rather than “excessive use may be restricted”. Decide whether the allowance counts downloads, uploads or both; whether it is shared across sessions; and whether the cycle follows the calendar or the customer's renewal date. State units and the time zone. Publish a way to check usage and dispute an incorrect reading that your team can actually deliver.
Illustrative subscriber wording — adapt the numbers to your offer:
This plan includes internet access throughout your paid monthly cycle. Speeds are up to 20 Mbit/s download and 5 Mbit/s upload until your combined upload and download usage reaches 300 GB. From 300 GB, speeds are up to 5 Mbit/s download and 2 Mbit/s upload; from 500 GB, up to 2 Mbit/s download and 1 Mbit/s upload. Access continues without a usage surcharge. The allowance and normal speed reset on the first day of each month at 00:00 UTC. Here, 1 GB is 1,000,000,000 bytes. Contact support for your usage record or to challenge an error.
These example limits are design choices, not recommended prices, capacity guarantees or legally approved contract wording. If your offer charges for extra data, does not count uploads, or has a different renewal date, change the promise before using it.
Choose tiers that survive a support call
This example counts both directions across all sessions for one subscription. Speeds below are ceilings, not guaranteed throughput. Size them against your access and upstream capacity and the applications customers need after reduction.
| Cycle usage, decimal GB | Download / upload ceiling | Example RADIUS value |
|---|---|---|
| Below 300 GB | 20 / 5 Mbit/s | 5M/20M |
| At least 300, below 500 GB | 5 / 2 Mbit/s | 2M/5M |
| At least 500 GB | 2 / 1 Mbit/s | 1M/2M |
| New paid cycle | Return to the first tier | 5M/20M |
Within a cycle, retain the highest usage tier reached. A reconnect, late packet or router restart must not restore the original allowance. Permit a documented correction or upgrade through an explicit operator decision. Keep usage restriction separate from unpaid-service suspension: a cycle reset must not reactivate a suspended account.
At the boundary, establish a fresh cycle ledger while preserving the previous one. Record which cycle owns late accounting records. For a session spanning midnight, take a boundary reading or document how an interval crossing the boundary is apportioned; do not silently assign the whole session to the new month. Reapply the eligible speed to an already-connected session, too.
From accounting to an enforced speed
The design is a short chain:
Accounting → validated cycle usage → retained tier
→ saved authorisation profile → CoA or reconnect
→ queue/throughput verification → support evidence
- Collect RADIUS Start, Interim-Update and Stop records. Keep a stable subscription mapping and distinguish NAS, session and restart identity. Add valid counter deltas, not every cumulative interim value. Deduplicate retries and quarantine stale or inconsistent readings. If accounting stops arriving, show the gap; do not pretend usage is zero.
- Reconstruct each direction as
octets + gigawords × 4294967296. A 32-bit octet counter alone wraps at 4 GiB, not 4 decimal GB. For example, 2 gigawords plus 100 octets means 8,589,934,692 bytes. Validate upload/download orientation on your access service before selling a download-only allowance. See RFC 2869 accounting extensions. - Store the target tier in the authorisation source used by the next login. Then request the live change. This order prevents a reconnect from bringing back the old speed.
- For a supported session, send a targeted CoA with the new
Mikrotik-Rate-Limit. RouterOS expresses rates as router receive/transmit, so2M/5Mmeans subscriber upload/download of 2/5 Mbit/s. MikroTik lists this attribute among those changeable by CoA in its RADIUS reference. - Match the intended session and record ACK, NAK or timeout. An ACK is protocol evidence; inspect the effective queue and test throughput separately. For an unsupported or rejected live change, arrange a controlled disconnect/reconnect after saving the profile and warning about interruption. Avoid repeatedly disconnecting the customer. See RFC 5176 dynamic authorisation.
Qualify the precise RouterOS version and PPPoE or HotSpot path in a lab. Restrict incoming dynamic-authorisation traffic to the trusted RADIUS sender and verify the configured listener port at both ends. Do not expose it broadly or put shared secrets in scripts, tickets or examples. This article sends no commands to a router.
Sanitised illustration, not a runnable configuration
The identity, address and log format below are invented. They are not captured ISPAgents output. Attribute selection must match the NAS and session being qualified.
NAS-IP-Address = 192.0.2.10
Acct-Session-Id = "example-session-042"
Mikrotik-Rate-Limit = "2M/5M"
2026-10-16T12:00:00Z service=example-042 cycle=2026-10 usage_bytes=300000000000 tier=1
2026-10-16T12:00:01Z service=example-042 desired_rate=2M/5M auth_profile=saved
2026-10-16T12:00:02Z session=example-session-042 coa=ACK verification=pending
2026-10-16T12:01:00Z session=example-session-042 queue=2M/5M lab_throughput=checked
Mistakes that make a fair policy feel unfair
- Stepping down and back up within a cycle. Recomputing from the current session alone erases earlier use. Preserve the cycle ledger and tier across sessions.
- Ignoring counter wrap or summing cumulative readings. Either can produce a false threshold crossing. Reconstruct wide counters and apply deduplicated deltas; investigate regressions rather than subtracting them from the customer's usage.
- Letting FastTrack bypass shaping. MikroTik documents that FastTrack bypasses simple queues and global queue trees. Exclude shaped traffic from FastTrack and retest existing and new flows, including IPv6 where offered. Check CPU capacity after changing the forwarding path. See RouterOS packet flow.
- Confusing desired speed with observed speed. A saved profile is not a successful live change. Keep the request result and the verification result separate.
- Promising an exact cutoff from delayed accounting. Explain the measurement interval and allow for usage between reports. Choose a reporting cadence your NAS and accounting service can handle.
- Using FUP to explain every slowdown. Check congestion, Wi-Fi, signal and upstream faults before attributing a complaint to a tier.
Explain it to an angry caller
Start with the lost experience, then give evidence and a reset time:
“I understand why the slower connection is frustrating. Your plan stays connected, but its speed changes after the published allowance. Our record shows 312 GB this cycle, against the first 300 GB threshold, so the current ceiling is 5 Mbit/s down and 2 Mbit/s up. The normal tier returns on 1 November at 00:00 UTC if the service remains paid. I can go through the usage record with you. If it is wrong, we will investigate and correct it.”
Do not blame the customer or promise that a reboot will reset usage. If the recorded policy does not explain the measured speed, open a fault investigation. Do not promise an upgrade, refund or exception that support cannot authorise.
Before publishing the offer
Verify the wording against the actual plan; test both thresholds, duplicate records, a reconnect, a counter wrap, a cycle boundary with an active session, and a CoA failure. Record what happens when accounting is delayed. Keep a rollback procedure, the previous profile, a support script and a responsible operator. Review the customer-facing wording locally before selling it.
Questions operators ask
Does unlimited mean unlimited full-speed data?
Define the offer explicitly. In this example access continues, but speed reduces at published thresholds. Do not imply unchanging full speed.
Is CoA the same as disconnecting a customer?
No. A CoA can request a supported policy change on a live session. A Disconnect ends the session; the next authentication must read the saved target profile.
Does ISPAgents automate these steps today?
Automatic fair-usage step-down planning is planned. ISPAgents RADIUS and MikroTik foundations are guided pilot scope, subject to qualification of the exact access path. The diagram and logs above describe a design to validate, not a shipped automation workflow.
For related evaluation context, read the FreeRADIUS versus managed RADIUS guided-pilot guide and MikroTik integration guided-pilot scope.