Can I report an outage that monitoring did not catch?

Yes. Open an incident by hand, choose whether it covers a device and everything behind it, a router, a location or the whole network, and notify the affected customers at once. It appears on the status page and can be compensated like any other incident.

Where do alerts get sent?

Alerts can be delivered to Discord, Slack, email or a generic webhook. You can configure rules per device or globally for events like a router going offline or coming back online.

Will I get spammed during a flapping link?

No. Alert rules use a minimum offline duration (flap damping) before firing and a per rule cooldown to throttle repeats, so you hear about real outages, not every transient blip.

Can I see which customers are affected by an outage?

Yes. On routers connected over the RouterOS API, ISPbox tracks PPPoE and DHCP session status, so you can see which subscribers are offline, not just which routers.

ISPbox

01 Feature Spotlight

Real-Time Monitoring for ISP and WISP Networks

Spot degradations early, react to outages faster, and keep your team aligned with a live view of network health.

Continuous uptime checks for critical network points
Early visibility into outages before they escalate
Operational context for support and field teams

Create Account View Pricing

app.ispbox.net

Real-time ISP network monitoring dashboard

// In the product

Inside network monitoring

Real screens from the product - the same views your team works in every day.

Router and session status at a glance

Built-in ping and PPPoE/DHCP session monitoring - see which routers are down and which clients are offline before the phone rings.

app.ispbox.net

Monitoring dashboard with router status, client sessions and recent alerts

Incidents open and resolve themselves

A device that stays down past the grace period becomes an incident with real service impact; when it recovers, the incident resolves and clients can be notified.

app.ispbox.net

Network incidents list with open outages and affected services

Bring your own NMS if you have one

Built-in monitoring works on its own; LibreNMS and Zabbix hook in optionally and power the same incident automation.

app.ispbox.net

Monitoring settings with built-in checks and LibreNMS and Zabbix integrations

→ Under the hood

How ISPbox monitors your network

ISPbox watches your network so you do not have to refresh dashboards. Routers are pinged every minute, subscriber sessions are tracked on API connected routers, and alert rules push the right notifications to your team the moment something goes down, with flap damping so you only hear about outages that matter.

Router uptime, checked every minute

A dedicated monitoring service pings each router on a one minute cycle and records status, latency and consecutive failures. Routers show as online, offline or unknown on a live dashboard with counts and a last seen time, so you can spot a tower or backhaul going dark right away.

Subscriber session visibility

On routers connected over the RouterOS API, ISPbox polls PPPoE and DHCP sessions every few minutes and tracks which subscribers are connected or offline. That turns a vague "is it just me" into a clear view of who is actually affected by an incident.

Alerts that do not spam you

Build alert rules per device or across all routers and clients for events like went offline, went online or status changed. A minimum offline duration (flap damping) stops transient blips from paging you, and a per rule cooldown throttles repeats. Notifications go to Discord, Slack, email or a generic webhook, and every alert is logged with its outcome.

Outages the system did not detect

Not every outage comes from a device going down in monitoring. Staff can open an incident by hand and choose who is affected: everything behind a map device, everyone on a router, everyone at a location, or the whole network. The number of affected customers is shown before you open it, and "notify now" sends the email and SMS right away.

Every incident, automatic or manual, shows on your public status page without device names, and when it is resolved you can give the affected customers free days or hours in one step: prepaid customers get time on their expiry date, monthly customers get a credit on the next invoice.

Works with Network Maps, Path Monitoring (SmokePing Alternative), MikroTik Integration, Ticketing

02 Why this feature matters

Built for high-speed ISP operations

Detect Issues Earlier

Catch performance drops and outages quickly, reducing prolonged downtime and reactive firefighting.

Respond With Context

Use a centralized operational view to prioritize incidents and guide support actions in real time.

Improve SLA Performance

Track uptime trends consistently to support reliability targets and service quality commitments.

Scale Monitoring Operations

Keep visibility clear as your network footprint grows across nodes, links, and customer zones.

03 Use cases

Where ISP teams put this to work

Monitor core and edge infrastructure uptime continuously.
Surface outage signals quickly for NOC and support teams.
Review recurring instability patterns and weak points.
Support faster incident triage with a shared operations view.

// Related

What ISP and WISP teams search for

isp network monitoring software wisp monitoring tool isp outage monitoring network uptime monitoring for isp real time network monitoring wisp

04 FAQ

Frequently asked questions

Can I report an outage that monitoring did not catch?: Yes. Open an incident by hand, choose whether it covers a device and everything behind it, a router, a location or the whole network, and notify the affected customers at once. It appears on the status page and can be compensated like any other incident.
How often does ISPbox check my routers?: Routers are pinged every minute by a dedicated monitoring service that records status, latency and consecutive failures. Subscriber sessions on API connected routers are polled every few minutes.
Where do alerts get sent?: Alerts can be delivered to Discord, Slack, email or a generic webhook. You can configure rules per device or globally for events like a router going offline or coming back online.
Will I get spammed during a flapping link?: No. Alert rules use a minimum offline duration (flap damping) before firing and a per rule cooldown to throttle repeats, so you hear about real outages, not every transient blip.
Can I see which customers are affected by an outage?: Yes. On routers connected over the RouterOS API, ISPbox tracks PPPoE and DHCP session status, so you can see which subscribers are offline, not just which routers.