Something goes wrong.
ServerVisor catches it first.
A cert expires quietly. A cron job stops running. A process eats memory. ServerVisor is built to catch all of it — before your users do.
Monitors
ServerVisor checks your sites, endpoints, and ports on a continuous schedule — from multiple locations — and opens an incident the moment something fails. You find out before your users do.
Checks run as fast as every minute.
SSL certificate and domain expiration checks come free with every HTTP monitor — no setup required. If your infrastructure goes beyond HTTP — databases, game servers, internal services — TCP and ICMP checks cover those too. API monitors let you set custom headers, request bodies, and JSON path assertions to verify an endpoint returns exactly the right response.
Node Insights
A lightweight agent running on each server sends a daily snapshot of the facts that matter to you: disk space, memory usage, OS version, PHP version, whether last night's backup succeeded — whatever you care about. ServerVisor stores each snapshot and diffs it against the last one.
When something changes — a PHP version you didn't expect, a config file that got modified, a disk filling up — you get an alert. When something goes quiet — a server that should be reporting but hasn't in three days — you get an alert for that too.
You define the facts. The agent sends them. ServerVisor handles the rest.
Heartbeat Monitors
Not every failure makes noise. A cron job stops running, your site stays up, and nobody finds out until the backup is gone or the nightly report didn't run.
Heartbeat monitors flip the check. Instead of ServerVisor reaching out to your server, your job reaches out to ServerVisor. Add a single HTTP request to the end of your script — we'll show you examples. If the ping stops arriving within the expected window, we alert you. Silence is the signal.
Dead man's switch for your scheduled tasks. One line of code.
Alerts that go where you work
An alert that goes to an inbox nobody checks isn't an alert. ServerVisor sends to email, SMS, Slack, Microsoft Teams, Google Chat, push notifications, and webhooks — and you control exactly which monitors notify which people through which channels.
Notification groups let you route critical monitors to your on-call rotation while sending SSL warnings and domain expiration notices to a Slack channel that gets reviewed in the morning. Not everything needs to wake someone up at 3am.
The mobile app
When a push notification lands, you need to know what's happening in seconds. The ServerVisor app for iOS and Android gives you a single-glance status summary, your full monitor list with live status badges, and open incidents with response time history. You can pause a monitor or acknowledge an incident from your phone.
Built to be transparent
Every check result is yours. On Business plans, the REST API — the same one the web dashboard uses — lets you pull monitor status, incident history, check results, and notification logs into your own systems. Webhooks deliver real-time payloads the moment an incident opens or closes.
Pricing is public and simple. Uptime Monitoring is billed by the number of monitors on your plan. Node Insights is $0.50 per server per month, with no tiers and no minimums.
Start monitoring your infrastructure
Uptime, SSL, domain, heartbeat, and Node Insights — all in one place.
Why is ServerVisor making requests to my server?
If you're seeing ServerVisor in your access logs, you are most likely a ServerVisor customer — all domains are verified before monitoring begins, so the monitor was set up by someone with verified access to your site. If that sounds like you, you can sign in to manage or remove any active monitors.
Requests originate from our monitoring infrastructure and are low-frequency — at most once per minute per monitor, and often much less depending on the account's plan. We do not scrape, index, or store your content.
How to stop ServerVisor from checking your server
If you have dashboard access, you can remove any monitor directly from within your account. If you don't have dashboard access and believe the monitoring is unauthorized, contact us with your server's hostname and we will locate the monitor and have it removed.
We take opt-out requests seriously. If you've received monitoring traffic that you believe is abusive, please let us know and we will investigate and act quickly.
What our monitoring does and doesn't do
- HTTP and HTTPS monitors send a GET request to the monitored URL and check for a successful response code.
- HTTPS monitors automatically check SSL certificate validity and expiry. Domain monitors check registration expiry dates.
- TCP monitors verify that a port is accepting connections. ICMP monitors verify host reachability. Neither reads or stores any content.
- API monitors send the request body and headers you configure and check the response against the assertions you define.
- Heartbeat monitors receive pings from your own scripts — ServerVisor makes no outbound request to your server for these.
- Node Insights agents run on your server and send snapshots outbound to ServerVisor — ServerVisor does not connect inbound to your server for this.
- We do not crawl links, index pages, store response bodies, or process your content in any way.
- We do not bypass authentication or attempt to access restricted areas.
- Our requests are identifiable in access logs so they are easy to filter or block if needed.
Have a question not answered here? Reach us via our contact form.