Measure current usage
We record traffic for a few days with Torch, Traffic Flow or NetFlow to see which users and services consume the link.
Start here
Free Audits 5Urgent help
Emergency 4Ongoing support
Managed IT 5Projects
Servers & Hosting 6 Network & Virtualization 9 DevOps 5 Security & Recovery 5 Hardware & Licensing 2Find out where your servers, security, backups and performance stand, at no cost.
Server down, network out, site hacked or data lost? Call us now.
Monthly network and server support with response times written into the contract.
Setup, configuration, management and migration of Linux and Windows servers, panels and mail.
Network design and cabling, MikroTik, VoIP, branch links, virtualization and private cloud.
Networking & communications
Virtualization & cloud
Containers, Kubernetes, automated delivery, infrastructure as code and observability.
Server hardening, firewalls, backup and DR, ransomware recovery and incident forensics.
Advice, supply and installation of servers and network gear, plus genuine enterprise licenses.
Start here
Urgent help
Ongoing support
Projects
One large download or an automatic Windows update is enough to break up a video meeting and every VoIP call in the office. For bandwidth management we classify traffic, give business services priority and cap everything else. Usage reports then show where your internet capacity really goes.
Bandwidth management for business is the practice of classifying office internet traffic, giving business services priority and capping everything else, with usage reports that show where capacity goes. It helps companies whose connection is fine in the morning and crawls after lunch, whose video meetings break up, whose monthly quota runs out early, or who can't tell which machine uses the most. PikoSystem first records traffic for a few days with Torch, Traffic Flow or NetFlow, then builds QoS with mangle rules and queue trees on MikroTik so VoIP and meetings go first. Speed caps or quotas are set per user, group, VLAN and guest Wi-Fi, and per-user accounting can run through a hotspot or RADIUS. You receive a baseline usage report, a priority and limit table, a backed-up queue configuration and a usage dashboard.
We record traffic for a few days with Torch, Traffic Flow or NetFlow to see which users and services consume the link.
Traffic is classified with mangle rules and queue trees. VoIP, video meetings and business apps get high priority; downloads and updates get low priority.
Each user, group or VLAN gets a speed cap or monthly quota. Guest Wi-Fi has its own limit.
Where needed, users sign in through a hotspot or RADIUS so usage is recorded per person.
We set up a dashboard or scheduled usage reports by user and service with ntopng or PRTG.
Simple queues are easy for a handful of users or subnets, but they are evaluated in order and CPU load climbs as the list grows. Queue trees work on packets marked by mangle rules and form a parent-child hierarchy, so you can cap the whole link and, beneath it, give VoIP priority 1 and downloads priority 8.
For fair sharing, a PCQ queue classified by dst-address for download and src-address for upload splits capacity evenly per IP without a rule per user. RouterOS 7 also adds cake and fq-codel queues, which reduce latency on a saturated link.
The most common is setting max-limit at or above the link's real speed. The actual queue then forms in the ISP modem and router priorities do nothing. The cap should sit slightly below measured capacity.
Another is limiting only download. When a cloud backup or file upload fills the upstream, VoIP suffers and even downloads slow down. Classifying by port 443 no longer works either, since nearly everything is HTTPS, so address lists by destination are needed. And with FastTrack enabled, much of the traffic never reaches the queues at all.
RouterOS 7 dropped IP Accounting, so Traffic Flow is the main tool. It exports NetFlow v9 or IPFIX records to a collector such as ntopng. Torch shows only live traffic and is no use for a monthly report.
Per-IP reports make sense only when each machine has a fixed address or reserved DHCP lease. Reports by person require hotspot or RADIUS sign-in. Decide data retention up front and tell staff that usage is recorded.
Tools like NetLimiter run on individual Windows machines and control only that machine. Staff phones, guest laptops and cameras stay outside the policy, and anyone with admin rights can close the program.
Control at the network edge covers every device. FortiGate uses Application Control signatures to identify apps and apply traffic shaping per application. pfSense does similar work with limiters and ALTQ, and for most offices MikroTik mangle rules with queue trees are enough.
We get router access and record traffic for a few days without changing anything.
We review the usage data with you and agree on priorities and limits.
Queues and limits go live, and we watch the network for a few days to adjust the numbers.
You receive the configuration, documentation and dashboard access.
When limits are based on real usage, most people notice no difference, and meetings and calls become more stable. We review the limits a few days after rollout and adjust them if needed.
Yes. FortiGate, pfSense and most business firewalls support traffic shaping. We start with the equipment you already have and only suggest a replacement if it lacks the feature.
Yes. If users sign in with personal accounts, usage is recorded by name. Otherwise, reports are built per IP address or device.
Related searches
Quote
A few lines on where things stand and what you want is enough. An engineer calls you back, not a sales rep.