Features
Built for the way a WISP actually breaks
Towers on batteries, backhauls with backups, radios powered from a router port. WISPMap understands the network you run, so it can tell you what went wrong instead of just what went quiet.
The live map
Sites and links coloured by health, updated every few seconds. Links show the traffic they carry, drawn in the direction it flows, and whether they're active, standing by or not ready to take over. Sites in a maintenance window show 🔧, and sites running on battery show 🔋. The Signal button colours wireless links by their signal instead.
Outages and routing
Root cause
WISPMap works out which sites sit behind which links. When one fails, you get one incident that names it and counts the sites cut off, not an alert for every router.
Incidents
Each outage gets its own page with a timeline: when it started, what changed, who acknowledged it, notes from the team, and when it ended.
BGP and multiple POPs
Every upstream session, the routes it sends and which POP each tower's traffic leaves through. You hear when an upstream drops, sends far fewer routes, or traffic moves to another POP.
OSPF and failover
Neighbours, costs and the routes each link carries, read from your routers. You hear when traffic fails over, when it returns, and when a backup isn't ready.
Power
Site power
Battery state from the voltage a chosen router reads: mains, battery, low and critical, with time remaining. How long each battery lasts, and a warning when one wears out.
Router health
Voltage, board and CPU temperature, power supplies and fans, wherever the router has the sensors. Charts keep each period's lowest voltage and highest temperature.
PoE
Power, current and voltage per PoE-out port. A fault alert names the port, and when a powered radio goes down WISPMap says which router port feeds it.
Wireless, subscribers and security
Wireless
Signal, SNR, CCQ and rates for every client of your access points and PtP links. You hear when a link falls 6 dB below its own normal level or its SNR gets too low.
Subscribers
Customers online on each router and tower, counted from PPPoE, hotspot or DHCP. Customers never count towards your plan.
Security check
Every router checked against MikroTik's hardening advice: exploited RouterOS versions, clear-text logins, the default admin user, settings malware switches on, and updates on its channel, each with the fix.
Alerts and your team
Alerts
Email, to each person or a shared mailbox, with escalation if nobody acknowledges and reminders while it's open. Change any rule's threshold or delay.
Maintenance windows
Plan work on a site or device, once or weekly in your own time zone. Alerts stay quiet inside the window, and the map shows it.
History
Latency and loss, CPU and memory, traffic and errors per interface, voltage, temperature and PoE, wireless signal and clients, and subscribers online, from the last hour to the last month.
Inventory
Sites, devices and links, imported from a spreadsheet or added by hand. Link suggestions come from your routers' neighbour lists.
Team and security
Owner, admin, technician and viewer roles. Two-factor sign-in with an authenticator app, and an audit log of who changed what.
On your phone
Every page works on a phone: the map, incidents and acknowledging an alert from wherever you are.
Wireless
Each access point's page lists its clients, weakest signal first: signal, SNR, CCQ, rates and how long each has been connected, from the older wireless package, RouterOS 7 wifi or 60 GHz. Links between towers show what each end hears against the level that's normal for that link, so a dish knocked out of alignment stands out, even while its signal still looks acceptable on paper.
Your customers' radios show up from the access point's own table. They are never added as devices and never count towards your plan.
Battery runtime and health
Every power cut is measured from the voltage the site's router reads: how fast the battery drained and how long it would have lasted. From those cuts WISPMap shows how long each tower's battery lasts, so you know which towers make it through a long power cut and which don't.
When a battery starts draining much faster than it did a few months ago, you get a warning while there's still time to replace it, not a dark tower at 2 am.
Devices
WISPMap is MikroTik-first. The collector reads RouterOS over its API with a read-only user: system resources, interfaces and traffic, OSPF and BGP, neighbours, health sensors, PoE, wireless clients and subscriber counts. Any other device with an IP address, such as a radio, switch or UPS, can be monitored by ping, with latency and loss history and alerts.
What the collector reads, and how it keeps your network safe →
Upstreams and POPs
For networks with more than one point of presence: the dashboard lists every upstream session per POP, with its state, the routes it sends and how many of your routers leave through it. Each router's page shows its BGP peers and the POP its traffic leaves through, found by following its default route over your links.
When an upstream drops, you get one alert that says so and where the traffic went. If no POP is left, WISPMap tells you that customers are offline even though every router still answers.
How WISPMap compares with The Dude, UISP, LibreNMS and Zabbix →
See it on a real network
The demo is a simulated WISP with 20 towers, running live. Outages, failovers and power cuts happen while you watch.