CronMaster

CronMaster solved a problem we did not know we had. Our daily database backup cron job had been silently failing for three weeks before we noticed. After setting up CronMaster, we now get immediate alerts for any missed or failed job. Setup took literally five minutes per job -- just add a curl to the end of each cron command.

Great monitoring service for scheduled jobs. The dashboard gives us a clear overview of all our cron jobs across multiple servers. The calendar view is surprisingly useful for understanding the scheduling landscape and identifying potential resource contention.

We monitor about 200 cron jobs with CronMaster and it has caught failures that would have otherwise gone unnoticed for days. The Slack integration is well-designed with clear, actionable alert messages. The duration monitoring feature helped us identify a data processing job that was gradually getting slower.

Simple, effective, and reliable -- exactly what cron monitoring should be. The HTTP ping approach means it works with literally everything: bash scripts, Python jobs, Laravel schedulers, Kubernetes CronJobs, and even GitHub Actions.

Good monitoring service for basic cron jobs. The ping-based approach is elegant for simple use cases. However, for complex multi-step jobs where I need more granular monitoring, I found the platform somewhat limiting.

CronMaster has become essential infrastructure for our SRE team. We monitor all critical background jobs -- billing runs, data syncs, cache warming, cleanup tasks -- and the 99.99% uptime SLA means we trust the monitoring itself.

Very useful service at a fair price point. We migrated from a homegrown monitoring solution and CronMaster provides a much cleaner experience. The cron expression editor and schedule visualizer are thoughtful touches.

Clean and focused product. CronMaster does cron monitoring well and does not try to be everything. The onboarding experience is one of the best I have seen -- create an account, get a ping URL, add it to your cron job, done.