MikroTik bandwidth control works best when plan speed lives in the billing system and the router receives policy through RADIUS. This prevents support teams from editing queues manually for every plan change, expiry, or FUP event.
Use RADIUS attributes for plan speed
For PPPoE networks, the common pattern is to return MikroTik-Rate-Limit from RADIUS. This lets each subscriber receive the correct upload and download speed based on the active plan stored in the ISP billing platform.
Keep burst settings consistent
Burst rate, burst threshold, burst time, and priority should be standardized by plan category. Inconsistent queue values create support complaints because two subscribers on the same plan can experience different performance.
Apply FUP through policy changes
When a subscriber crosses the fair usage limit, the billing platform should change the returned speed policy and send CoA for live sessions. This is cleaner than creating separate manual queues on routers.
Monitor sessions and failures
Queue management is only reliable when paired with online session monitoring, accounting data, NAS health checks, and RADIUS failure logs. These signals help teams separate plan policy issues from router or link congestion.
NowaCRM connects plan speed, FUP rules, RADIUS authorization, MikroTik-friendly attributes, CoA, and online session reporting so bandwidth control stays tied to subscriber billing state.