Uptime monitoring
Watch your services from the outside, too
When a server dies completely, its agent dies with it. Cloud-side checks catch the outages an agent can’t report — and tell a human about them until someone acknowledges.
In short
Opservo uptime monitoring runs HTTP, API, TCP, ping, DNS and domain checks from the cloud, tracks SSL certificate expiry, and accepts cron heartbeats, so an outage is detected even when the server and its agent are completely down. Confirmed outages alert Slack, email, webhooks, PagerDuty or OpsGenie, escalate to on-call until acknowledged, count against an SLA target, and appear on a public status page. Uptime checks are included on the Free plan.
Independent by design
Monitoring that survives the outage
Agent-based monitoring answers “why is it broken?” — but only while the agent can phone home. A full server, network or provider failure takes the agent down with it. Opservo’s uptime checks run from our cloud, independent of the agent, so a dead box never means dead monitoring.
Outside view + inside view
External checks tell you it’s down; the agent on the same server tells you why. One incident, both halves of the story.
Response-time tracking
Every check records how fast the endpoint answered, so a slowdown is visible before it becomes an outage.
Wired into everything
Failures flow into the same alerts, on-call escalation, incidents and status pages as the rest of Opservo — not a separate silo.
Seven check types
One monitor for every kind of “is it up?”
Websites, APIs, ports, hosts, DNS, the domain itself — and the cron jobs everyone forgets to watch.
HTTP(S) website
Load a URL from our cloud, assert the status code and response time — and optionally that the page contains a keyword.
Raw API
Call an endpoint with your method and headers, and verify it answers the way your integration expects.
TCP port
Confirm a port accepts connections — a database, a mail server, anything that isn’t HTTP.
ICMP ping
The simplest liveness signal: is the host reachable at all, and how fast?
DNS record
Resolve a record and check it returns the value you expect — so a bad DNS change can’t linger silently.
Domain expiry
Watch the domain registration itself via RDAP, so the domain never lapses out from under your site.
Heartbeat / cron
A dead-man’s switch: your backup job pings a URL after each run. If it goes quiet, you find out it stopped.
Until a human picks it up
Alerts that refuse to be ignored
A critical alert that dies in a muted Slack channel is worse than no alert. Unacknowledged critical alerts repeat on your interval and escalate to your on-call contact after a threshold you set — and keep going until someone acknowledges. Then the incident workflow takes over: declare, assign, status updates, post-mortem.
Show your customers
A public status page, built in
Publish a shareable status page per workspace — aggregate-only so no internal names leak, or per-server when transparency is the point. It reflects your servers and external checks together, so “is it just me?” has a URL.
Questions
Uptime monitoring, answered
What is website uptime monitoring?＋
Website uptime monitoring checks a site from outside on a fixed schedule and alerts you when it stops answering, returns an error or becomes too slow. Opservo loads the URL from its cloud every 30 seconds to 24 hours (every 60 seconds by default), checks the status code, the response time and optionally a keyword on the page, tracks the SSL certificate behind it, and alerts your channels when an outage is confirmed.
How does an uptime checker decide a site is down?＋
One failed check is not enough, because a single timeout is often a network blip. Opservo marks a monitor down after two consecutive failed checks, records the outage from the time of the first failure, and marks it up again on the first successful check. Heartbeat monitors for cron jobs work the other way round: they go down when an expected ping does not arrive within its interval plus a grace period.
Can Opservo monitor DNS records?＋
Yes. A DNS check resolves a record on every run and compares the answer with the value you expect, so a wrong or missing record after a DNS change raises an alert instead of lingering. Separate domain checks watch the domain registration itself through RDAP, so the domain cannot lapse unnoticed.
What is a downtime monitor?＋
Another name for an uptime monitor, seen from the outage side: it records when a service went down, how long it stayed down and when it came back. Opservo keeps every outage as an episode, shows each monitor’s uptime over the last 24 hours and 30 days, tracks it against an SLA target you set, and can publish the same picture on a public status page for your customers.
Do I need to install the agent to use uptime monitoring?＋
No. Uptime checks run from the Opservo cloud against your public endpoints, so they work on their own. Pairing them with the agent gives you both views of the same server — outside (is it reachable?) and inside (why not?).
What happens when a check fails?＋
An alert goes to your notification channels — Slack, email or webhook — and if it’s critical and nobody acknowledges it, it repeats and escalates to your on-call contact until someone does. Your status page reflects the outage automatically.
Does it track SSL certificates?＋
Yes. Every HTTPS monitor tracks the certificate behind it and warns you before it expires, and domain checks watch the registration itself via RDAP — so neither a cert nor a domain ever silently lapses.
Can my customers see uptime?＋
Yes — each workspace can publish a public status page, either aggregate-only (no server names leaked) or per-server, reflecting your servers and external checks together.
Know the moment anything goes dark
Free for 2 servers, no credit card. External checks live in minutes.