Remote-site monitoring
Know a site is down before your customers do.
Most monitoring assumes a data centre: reliable power, a wired uplink, someone down the hall. Pingmon was built for the other kind of network — repeater sites, solar-powered huts, tower gear on the end of a 5G link, hours from the nearest technician.
No card required · Your own subdomain in under a minute
Everything on the site
Not just the router
A remote site fails in more ways than a link going down. Pingmon collects the things that actually break out there — and the power system that takes the rest of them with it.
Reachability and latency
Checks as often as once a second, with the real distribution — packet loss, minimum, average, 95th percentile — instead of one averaged number that hides the problem.
Interfaces over SNMP
Throughput and errors per port, with vendor health for the hardware people actually deploy in the field — MikroTik, Netonix, cnMatrix, Ubiquiti airMAX.
Battery and solar
State of charge, load and yield through Victron VRM. At a remote site the power system is the thing most likely to fail, and the first thing worth watching.
Industrial equipment
Registers over Modbus TCP, for pumps, meters and controllers that predate anything resembling an API — charted next to the network they sit on.
Host metrics
CPU, memory, disk and load from a lightweight agent, for the servers behind the link. One command to enrol; the token is the credential, not the binary.
5G and cellular CPE
Subscriber gear reached by IMSI through the carrier's NOC, so a CPE on a dynamic address is still a device you can watch by name.
Alerting
It has to reach a person
An alert in a shared inbox at 2 a.m. is not an alert. On-call rotations decide who is responsible right now, and anything critical that goes unacknowledged climbs the chain instead of sitting unread.
- Time-block rotations for the real world, where the roster is not simply one week each — fixed blocks, rotating blocks, and a fallback for the gaps.
- Four channels — email, SMS, webhook, and push to the iOS app — chosen per rule, so a warning and a site outage do not arrive the same way.
- Acknowledge from anywhere, including the phone that woke you, which stops the escalation before it reaches the next person.
Dashboards and reports
Answers for the people who ask for numbers
The night shift needs a wall display. The monthly meeting needs a figure with a date range on it. Both come out of the same data.
Dashboards you arrange
Widgets for status, latency, throughput, power and Modbus values, dragged into a layout that matches how your team thinks about the network.
Availability and latency reports
Any window, exported to CSV or PDF, and schedulable — so the monthly summary arrives without anyone remembering to produce it.
Shared by link
A read-only dashboard URL for a wall-mounted browser or a customer, without giving anyone an account to manage.
Built for more than one organisation
Your data stays yours
Every customer gets their own subdomain, their own data and their own branding — whether that customer is another department or another company.
- Isolation at the database layer, enforced for every query rather than by remembering to filter each one.
- Two-factor authentication is mandatory for platform accounts, not an option buried in a settings page.
- Single sign-on against your own identity provider, so joiners and leavers are handled where you already handle them.
- Your colours and logo on the interface and on the sign-in page your own users see.
Put a second on it
Start a trial, point Pingmon at one site, and watch the first outage arrive as something you can measure rather than something a customer phones about.
No card required · Cancel from the billing page at any time