Healthchecks.io
Healthchecks.io
Listens for pings from scheduled jobs and sends an alert when an expected ping arrives late.
Pricing checked
Tools that watch websites, services, and scheduled jobs, then alert you when a check fails or arrives late.
Healthchecks.io
Listens for pings from scheduled jobs and sends an alert when an expected ping arrives late.
Pricing checked
UptimeRobot
Checks websites and network endpoints on a schedule, then sends alerts when a check fails.
Pricing checked
Uptime monitoring sounds like one thing. It's really two. The first is knowing whether your website or service is reachable right now. A tool checks it from outside, every minute or few, and tells you when it fails. The second is knowing whether a scheduled job ran. A backup, a data sync, a nightly report. Here the tool waits for a ping from your job, and alerts you when the ping doesn't arrive.
Mix them up and you'll buy the wrong tool. A website probe can't tell you your backup silently stopped. A job monitor can't tell you your homepage is down.
Endpoint monitors request a URL, port or address on a schedule. Common check types are HTTP status, keyword on a page, ping and open port. If a check fails, they send an alert to email, chat or a pager service. Many also host a public status page.
UptimeRobot is an example in this category. Its record lists HTTP, keyword, ping and port monitoring plus status pages.
Job monitors flip the direction. Your cron job calls a unique URL when it finishes. If the call doesn't arrive within the expected time plus a grace period, you get an alert. That catches the failures nobody sees: a server that rebooted, a script that crashed, a disk that filled.
Healthchecks.io is an example here. Its record lists cron schedule support, grace periods, ping logs and start and failure signals.
Check intervals and monitor counts differ by plan. Always confirm them on the vendor's page, since they change.
Many small teams use one of each: an endpoint monitor for the public site and a job monitor for everything scheduled. Free plans often cover that. Start there and upgrade only when you hit a real limit.
Each record in this category links to its sources and shows the date its pricing was last verified.
Website monitoring is outside-in. A service requests your page every minute or so from somewhere on the internet, and if the answer is wrong or slow, it tells you. Job monitoring is inside-out. Your scheduled task reports success, and if that report is missing, you get an alert.
Both are called uptime monitoring, and that's the confusion. A site monitor won't notice that your nightly export stopped. A job monitor won't notice that the checkout page returns an error. Decide which failure hurts more, or plan to cover both.
The two products in this category map to the two jobs, and the comparison page puts them side by side.
Look at how often it checks and what the free plan allows. A five-minute interval is fine for a brochure site and slow for a shop. Look at what counts as a failure. Status codes are the minimum. Keyword checks catch pages that load but show an error.
Then think about alerts. Email is easy to miss. Chat and pager integrations are better for things that can't wait. Test an alert on day one so you know it actually reaches you.
Finally, ask who looks at the results. A monitor nobody reads is just a bill.
False alarms train people to ignore alerts. If a single failed check triggers a page at 3 a.m., you'll soon mute the channel. Use retries or confirmation from more than one location when the tool allows it.
The reverse problem is checking the wrong thing. A monitor that only fetches the homepage will say you're fine while login, search or payments are broken. Point checks at the pages that matter.
And don't forget the monitor itself. Put an alert on the alert path, such as a weekly test, so a silent failure doesn't hide for months.
Each product page lists features, integrations and plans, with sources and dates. We keep the category small until each record has been checked carefully. If you spot something stale, tell us.
Start with what failing would cost you. A hobby blog can live with a few hours down. An online shop can't. A nightly backup that silently stops might not hurt until the day you need it, and that's the worst time to find out.
Then pick the type of check that matches the risk. External checks watch what visitors see. Heartbeat checks watch what your own jobs do. Many setups need one of each, and the two tools we cover are free to start with.
Keep alerts few and loud. Ten channels that all buzz at once get muted. One or two that always reach a human get answered.
Add your main page, one deeper page that touches your database, and one job heartbeat for your backup. That's three monitors, and it covers most small projects.
Check each alert path once. Then review the list quarterly and drop what you no longer run.
How often do checks run on the free plan? Where do alerts go, and can you add a second route? What happens to your history after 30 or 90 days? How easy is it to leave, and can you export your monitors? A tool that answers these plainly is usually run by people who care.