Guide

MikroTik router monitoring

A RouterBOARD behind a wall is the part of the network that decides whether subscribers are actually online. This guide covers what to watch on MikroTik hardware, which signals warn first, and how monitoring connects to billing rather than sitting beside it.

The five-minute watchlist

Start with what a router reports about itself: CPU load, memory use, uptime, interface state, and storage. Uptime is the most human of them — a router that rebooted last night tells you more than a slow trend line, because a reboot is an event with a time and, usually, a cause.

Interface state catches the failures that subscribers feel first: a port that is up but flapping, traffic on an interface that should be idle, or one interface carrying far more than it should. These are visible long before anyone files a ticket.

Watch capacity, not just health

A healthy router can still be the bottleneck. Compare throughput against the link it serves and watch the trend, not the peak: saturation at the same hour every evening is a pricing and shaping conversation; saturation that grows week over week is a capacity one.

Track address table size and DHCP pool usage as well. Both fail in ways that look like 'the internet is down' from the subscriber's side while every individual process on the router is still reporting green.

Configuration backups and change history

The second part of monitoring is knowing what the router was configured to do. A scheduled configuration backup means a replaced device is a hardware swap instead of an afternoon of reconstruction, and a bad change is a diff instead of a mystery.

Keep the backups somewhere the router itself cannot wipe them, and treat a router whose configuration has changed without a matching change record as an incident, not a curiosity.

Monitoring connected to billing

Router monitoring earns more when it shares data with billing. An outage credited back to affected subscribers needs to know who was affected; a subscriber who is 'active' in the billing record but absent from the router's sessions has a problem that neither team can see alone.

Start with the two links that are cheapest to build: session presence per subscriber, and uptime per device feeding an outage record. From there, monitoring stops being a dashboard and becomes part of the money.

Keep reading

Resources

Ready to put this into practice?

This guide covers the approach — the platform is where you run it day to day.

Get started

Walk through the platform with our team on your own setup.
Start a conversation

All resources

Browse every guide and playbook we have published.
Browse guides