MikroTik routers have limited processing power, memory, and storage. Running billing software on the router uses some of those resources, which can slow down logins and traffic.

21 Nov,2026, 8:43
Running billing software on a router that also handles customer traffic can slow things down because it adds more work for the router. On a powerful router with only a few customers, you might not notice. But on a smaller router, or one serving lots of customers, logins can take longer, Winbox can feel sluggish, and clients may get slower speeds.
What counts as a billing system on a router?
User manager
User Manager is a RADIUS service that comes as a separate RouterOS package. It checks users and stores their information on the router. MikroTik says it’s available on most router types, but keep an eye on storage space since many routers don’t have much to spare.
Local users
If you run a hotspot, user accounts may be stored right on the router. A PPPoE server can also store usernames and passwords for home users. The router checks each connection against those local lists.
Scripts and schedules
Some routers use scripts to manage user accounts. They might disable accounts for people who haven’t paid, add new users, or send messages. These scripts use the same processor as everything else running on the router.
External billing
External billing systems may query the router regularly to check who’s connected, how much data they’ve used, or what settings the router has. Each check may take only a little time, but frequent queries can add up.
All of these billing methods use the same processor, memory, and storage as your routing services. Routing, firewalling, NAT, QoS, hotspot logins, and active PPPoE sessions all need those resources too. When billing runs on the same router, it can take resources away from other jobs.
How billing can affect performance
Billing software won’t always slow down a router, but it can, depending on what the router is doing. Here are a few reasons why:
Shared resources
Some billing tasks take a lot of processing power. Adding a large number of users, searching a long user list, closing sessions, or running reports all add work for the same processor that handles customer traffic.
One MikroTik community forum user ran User Manager on a router that was also acting as a PPPoE concentrator. When they ran tasks in User Manager, CPU usage hit 100% and customers couldn’t connect. Another user said moving User Manager to a separate device fixed similar problems.
A single core can become a bottleneck
Another forum user had a router with 36 cores, but User Manager operations heavily loaded just one core while the other 35 sat mostly idle. Having lots of cores won’t necessarily make this kind of task run faster, and a busy core can slow down other processes.
Large lists can use a lot of memory
Opening a large user list in Winbox can make things noticeably slower and use plenty of memory. That can affect the router and may be noticeable to customers too.
Limited storage
Many routers have very little space for software and data. Over time, the database that stores user details and usage information can grow and fill it up.
Just from the same community, one user said their small router eventually took hours to boot after years of accumulating data. That left all their customers offline for hours. Many routers also use small flash memory that isn’t designed for frequent writes, so it’s not ideal for a database that gets updated constantly.
Limits of local user lists
Based on what people report on forums, a router’s local list is usually fine for around 100 PPPoE users. Above that, it may be worth using a billing system like User Manager or an external RADIUS server. For hotspots with more than about 200 local users, many people recommend RADIUS.
These aren’t official limits, and performance can vary between router models. In general, though, local lists tend to work best with smaller numbers of users.
What can happen after an update
Some forum users have noticed that CPU usage stays higher for a while after a RouterOS update, or sometimes doesn’t settle back down at all. It’s hard to know exactly why, but it suggests the router software and billing setup may affect each other. An update could have an impact on both.
When billing and routing fail together
If billing and routing are running on the same router, a problem with one can affect the other. For example, if a billing process uses too much CPU, customers may lose internet access. And if the router reboots, billing goes offline too.
When billing and routing run on separate systems, they can fail independently. That means one system may keep working even if the other has a problem.
If you have a lot of entries for a small router, it’s worth investigating further. Try opening the user list in Winbox and see how long it takes to load. While billing is running, ping the router’s local IP from a customer device and check whether the response slows down.
Also keep track of customer reports about slow logins or failed connections. Note whether those issues happen around the same time as scheduled scripts. It’s useful to record how long the router takes to boot and how often it reboots, too.
Solutions
The general recommendation is to separate routing from billing and RADIUS. The router only needs to check whether a customer can connect and get a quick response. Everything else, such as storing data, charging customers, sending reminders, and generating reports, should run on another system.
That could be a separate machine or a virtual server you manage. You could also use a cloud-hosted billing service, so you don’t have to buy hardware, maintain a database, or update servers.
There are a few things to keep in mind. If the router can’t reach the billing server, new logins might fail, depending on how things are configured. Existing sessions may keep working. Choose a service that responds quickly, and set the router to wait a reasonable amount of time for a RADIUS response so customers aren’t left waiting. If possible, secure the connection with a private tunnel, such as WireGuard. Make sure your data is backed up, and find out what happens to it if you stop using the service. Before going live, test the setup with a few test users.
Minimizing the impact
Try to limit how much work the router has to do. Make sure it has enough processing power and memory for your customer base, and keep the user list short by deleting old data. If you need to run demanding tasks, schedule them for quieter times. Avoid opening very long user lists in Winbox during peak hours, and make sure there’s enough free storage. Be careful with updates, test them on a spare router first, and keep an eye on CPU usage while you make changes.
Separating billing from routing can help keep the router running smoothly. It also makes it easier to reboot or replace the router, since billing runs elsewhere and can be expanded without upgrading the router. Still, check performance on your own setup. If the data shows that billing is slowing down traffic, consider moving it to a separate system.
Popular Posts