Smokeping for multi ISP Mikrotik

3rd party tools
1

Hey everyone,

I wanted to share a project I’ve been working on — an automated Smokeping Master + Slave setup that’s perfect for multi-ISP or load-balanced environments. It lets you monitor all your ISPs simultaneously, giving you a clear view of latency, jitter, and packet loss per link.

Each slave container has its own static IP and is routed through a specific ISP using strict PBR (policy-based routing) — so you get clean, isolated monitoring per connection, not a mix of routes.

It’s built around Docker with MacVLAN for proper network isolation and simple static IP assignment. You’ll need to host it on a separate device that supports Docker, since I haven’t tested it yet using MikroTik’s container feature (though that might be an interesting next step).

The setup is designed to be easy — one script handles everything: deploy, reload, stop, or remove.

If you find it useful or want to tinker with it, feel free to jump in — the project is open-source and open for contributions. And if it helps you, please consider :star: starring the repo to support it!

GitHub: https://github.com/Kintoyyy/smokeping-multi-docker

Here's a live demo: https://test-smokeping.kintoyyy.com/smokeping/?target=DNS.Google1

image
image1004×689 55.1 KB

{C62A1AD1-1CE0-4FB9-9041-90D91839C751}
{C62A1AD1-1CE0-4FB9-9041-90D91839C751}1920×1139 267 KB

{44EEED08-635D-4029-BC73-FBC80BFFD330}
{44EEED08-635D-4029-BC73-FBC80BFFD330}1920×891 247 KB

2

Hi,

Try to convince us that that post is not an advertisment spam.
Where the Mikrotik is involved except: " haven’t tested it yet using MikroTik’s container"

3

Hi,

This isn’t an advertisement :slight_smile: it’s a technical contribution meant to help other network admins and MikroTik users who have multi-ISP setups. The project was built specifically to complement setups where MikroTik handles the routing and load balancing, while Smokeping provides visibility per WAN link.

I mentioned Docker because it’s the current method I used for hosting and running the smokeping, but the next step (and part of why I posted here) is to explore integrating it directly within MikroTik’s container system. The post is to share the tool and approach and not to promote any product or service.

1 Like