MSP uptime monitoring software with client status pages and reports
UptimePilot gives a managed service provider one account for every client: a group per customer with ping, TCP port, HTTPS, SSL, domain and backup heartbeat checks, confirmed from two regions before anyone is paged. Each client can get a private status page and a monthly uptime report with your logo. Business covers 1,000 monitors and 25 technicians for $124 a month billed yearly.
Why an RMM agent is not enough for client uptime
Your RMM watches each endpoint from the inside. It knows the disk on the file server is at 92% and that a Windows service stopped. What it cannot tell you is whether the client's customers can reach the website, whether the VPN gateway answers from the internet, or whether the office lost its connection entirely, because when the site goes dark the agent goes quiet with it. A silent agent and a healthy agent look alike for longer than anyone wants.
External uptime monitoring fills that gap. Checks run from outside the client network, the way a remote worker or a customer connects, so a dead ISP line, an expired certificate on the RDP gateway or a firewall rule that closed port 443 shows up as an outage within about a minute.
The second gap is proof. Clients on a monthly agreement rarely see the incidents you prevented. A short report that shows 99.98% uptime for their critical services, with the two incidents you handled, is the easiest renewal conversation you will have all year.
What MSPs monitor for each client
Every check type is included on every plan, so you build the same template for each customer and adjust it.
- Internet line and firewall: a ping check on the client's public IP or firewall WAN address catches a dead ISP circuit, a power cut at the office or a hung edge device.
- Remote access: TCP port checks on 443 for SSL VPN, 3389 for an RD gateway or 1194 for OpenVPN confirm that remote staff can actually get in, not just that the box has power.
- Email and line of business apps: port 25 or 587 for an on premise mail relay, HTTPS and keyword checks for the client portal, the booking system or the hosted ERP login page.
- Websites and web apps: HTTP(S) checks with status code, response time and keyword assertions, so a page that loads but shows a database error counts as down. See website monitoring.
- Certificates and domains: ssl certificate monitoring warns weeks before a certificate on the VPN, mail server or website expires, and domain expiry checks catch the renewal the client forgot to pay.
- Backups and scheduled jobs: a heartbeat URL is called at the end of every backup, sync or scheduled task. If the call does not arrive on time, you get an alert, which also covers servers that are not reachable from the internet. Details on cron job monitoring.
External uptime monitoring vs RMM and status aggregators
MSPs usually run three kinds of monitoring side by side. They answer different questions, so the honest answer is that most providers need more than one.
| External uptime monitor (UptimePilot) | RMM agent monitoring | Third party status aggregator | |
|---|---|---|---|
| Where checks run | From two regions outside the client network | On each endpoint, inside the network | Reads public status pages of cloud vendors |
| Catches a dead ISP line or office power cut | Yes, within about a minute | Only as a missing agent heartbeat | No |
| Catches an expired VPN or website certificate | Yes, weeks ahead | Sometimes, if scripted | No |
| Disk, CPU, patches and services on endpoints | No | Yes, this is its strength | No |
| Microsoft 365 or AWS incident affecting the client | Only if you monitor their endpoints | No | Yes, this is its strength |
| Client facing status page and uptime report | Yes, branded per client | Usually internal dashboards only | Some offer internal pages |
Keep the RMM for patching and endpoint health. Add an outside-in monitor for availability, certificates, backups and client facing proof. If you already pay for a vendor status aggregator, the two complement each other.
-
01
Create a group for each client
A group holds one customer's monitors, alert rules, status page and report. Technicians see the groups their role allows, so a junior tech can acknowledge alerts for three clients without editing the rest of the account.
-
02
Apply your standard check template
Add the WAN ping, the VPN and RDP ports, the mail relay, the website and the backup heartbeats you monitor for every client. On Business and Enterprise the REST API creates the same set for each new customer from your onboarding script, so a new contract is covered on day one.
-
03
Route alerts to the technician on call
Send alerts to Slack, Microsoft Teams, SMS, email or a webhook. Most PSA tools accept tickets from an email inbox, so an alert can open a ticket in the right client board while the on call technician gets the SMS. Escalation moves the alert to the next person if nobody acknowledges it within the minutes you set.
-
04
Send each client a status page and a monthly report
Give larger clients a private, password protected status page for their staff, on a domain such as status.clientname.com. At the end of the month, each client gets an uptime report with your logo: uptime percent per service, response time and the incident log with durations.
Which MSPs use UptimePilot
- IT providers with 10 to 150 small business clients who sell monitoring inside a per user or per device agreement and want proof the client can see.
- MSPs that host line of business apps, remote desktops or client websites and are judged on availability more than on endpoint metrics.
- Providers with SLA commitments that need monthly uptime numbers and incident durations per client, not a single account wide figure.
- Teams moving off a free or per seat uptime tool because every technician needs a login and every client needs separation.
MSPs serving police departments, courts or their software vendors often face CJIS audits as well, where a dedicated CJIS compliance software for policies and evidence sits next to the availability records you keep here.
What uptime monitoring costs for an MSP
Pricing is per team, with technicians included, not per client or per seat. Full details on uptime monitoring pricing.
- Team, $99 a month or $49 a month billed yearly: 200 monitors, 30 second checks, 50 heartbeat monitors, 5 status pages with custom domains, 10 members, monthly SLA PDF.
- Business, $249 a month or $124 a month billed yearly: 1,000 monitors, 250 heartbeat monitors, 20 password protected white label status pages, 25 members, white-label client reports, REST API, 2 years of history.
- Enterprise, $599 a month or $299 a month billed yearly: 3,000 monitors, 1,000 heartbeat monitors, 50 status pages, 100 members, SSO (SAML) and audit log.
A typical example: 40 clients with about 12 monitors each is 480 monitors, which fits Business. That works out to about $3.10 per client per month billed yearly, with reports and status pages included. Most providers resell monitoring for far more than that inside their agreement.
01
Do MSPs need uptime monitoring if they have an RMM?
Yes, in most cases. An RMM agent reports on endpoint health from inside the network, so when the office loses its internet line or power, the agent simply stops reporting. An external uptime monitor checks from outside, catches dead lines, closed ports and expired certificates within about a minute, and produces client facing uptime reports.
02
How much does uptime monitoring cost for an MSP?
On UptimePilot, Business costs $124 a month billed yearly for 1,000 monitors, 25 technicians, 20 white label status pages and branded client reports. An MSP with 40 clients and about 12 monitors per client pays roughly $3.10 per client per month. There is no per seat or per client fee.
03
Can I give each client their own status page?
Yes. Team includes 5 status pages with custom domains, Business 20 and Enterprise 50. On Business and Enterprise, pages can be password protected for the client's staff only and carry no UptimePilot branding, as described on the white label status page page.
04
Can UptimePilot monitor servers behind a firewall?
External checks need a public address, so they cover the firewall, VPN gateway, published services and websites. For servers that are not reachable from the internet, a scheduled task on the server calls a heartbeat URL every few minutes or after each backup. If the call stops arriving, you get an alert.
05
Can I monitor client backup jobs?
Yes. Each backup or scheduled task gets a heartbeat URL that the job calls when it finishes. You set the expected schedule and a grace period, and UptimePilot alerts you when a run is missed or late. Business includes 250 heartbeat monitors and Enterprise 1,000.
06
Can alerts create tickets in my PSA?
Alerts go out by email, SMS, Slack, Microsoft Teams and webhook. Most PSA platforms can create tickets from an inbound email address, so routing a client group's email alerts to that inbox opens a ticket automatically. Webhooks suit PSAs and automation tools that accept inbound HTTP requests.
Cover every client network from one account
Create a group per client, apply your check template and send the first branded uptime report at the end of the month.