Uptime monitoring for MSPs

Watch the public side of every customer: websites, portals, mail and VPN hosts, certificates, DNS and the backup jobs you run. Alerts go into the tools your service desk already uses.

  • Hosted in Germany
  • PagerDuty, webhooks, API
  • Free plan for 3 sites
For MSPs

The outside view of every customer

Your RMM watches the inside. This watches what the customer's own customers see.

Public endpoints

HTTP checks for websites and portals, ping for public hosts such as firewalls and VPN gateways, and TCP checks for mail and other public ports. Every minute, or every 30 seconds for up to 10 HTTP or ping checks, confirmed from a second region.

Backup and job heartbeats

Add a ping URL to the end of a backup script. When it stops arriving, an incident opens. PowerShell, shell and crontab snippets included.

Certificates and DNS

Certificate warnings for every customer portal, and an alert when a hostname's DNS target or addresses change.

Into your service desk

PagerDuty, webhooks, Microsoft Teams, Slack, email and SMS through your own provider account.

Automate onboarding

Create sites and checks through the REST API when you sign a customer.

Allow-list friendly

Every request names us in its user agent, and the probe addresses are published.

Reports per customer

Group monitors per customer, and report availability against an SLA target with the error budget used.

EU hosting

The application and your check results are hosted in Germany. Every provider is named in the DPA.

What it costs

An MSP with 120 public endpoints across its customers pays the banded rate: 120 sites cost €149.00 a month, excl. VAT, with every feature and unlimited team members. See the pricing page for every size from 1 to 500 sites.

A typical setup

  • A monitor group per customer, with their website, portal, webmail and VPN hostnames.
  • Ping checks on public firewall and gateway addresses, and TCP checks on public mail and VPN ports.
  • A heartbeat at the end of each backup job.
  • A routing rule that sends critical events to PagerDuty or a webhook into your ticketing tool.
  • A monthly SLA report per customer group.

What it does not do

  • We only check public addresses. Private and internal addresses are refused, and there is no agent inside a network.
  • No server metrics such as CPU, memory or disk.
  • No on-call schedules or escalation policies. Use PagerDuty for those.
  • Status pages cannot use a customer's own domain, and there is no white label.

See all features, compare us with Hyperping, UptimeRobot, Pingdom or Better Stack, or read how we help agencies and e-commerce.

Questions

Questions people ask

Can I monitor servers inside a customer network?

No. We only check public addresses, from our probe regions. There is no agent to install inside a network.

Can alerts create tickets in my PSA tool?

Send alerts to a webhook that your PSA or ticketing tool accepts, or to PagerDuty. Routing rules decide which events go where.

Can I keep customers apart?

Yes. Use a monitor group per customer in one team, or a separate team per customer. One person can own up to 10 teams, each with its own billing.

Which addresses do your probes use?

Every request carries our user agent, and the probe IP addresses are published on our bot page, so customers can allow-list them.

Start now

Add your first customer today.

Start free: seven days with every check type on 5 sites, then the Free plan: 3 sites with every check type and every alert channel. No card. Your first check runs in about two minutes.