Monitoring for developers and operations teams
Uptime checks catch the loud failures. The ones that hurt most are quiet: a cron job that stopped after a server move, logs that fill a disk over a week, an MX record changed during a migration. Uptimecheck puts those checks in the same account as your uptime monitors.
Cron jobs on their real schedule
Add the ping URL to the end of your backup, import or billing job. Give the monitor the job’s crontab schedule in your time zone, daylight saving included, and a grace period. Call /start when the job begins to record its run time, and get an alert when it runs past the maximum run time. Report a failure with /fail or the exit code, and POST the job’s output to see it with the failure and in the alert.
Read how to monitor cron jobs for patterns that avoid false alarms, and cron expressions explained for the schedule itself.
Server resources from a small agent
Install the server agent with a one-line command on Linux, macOS (Intel and Apple silicon) or Windows. It reports CPU, memory, disk and network every minute, lists every disk, and alerts when a value stays above your limit for a few minutes, after a reboot, or when reports stop. Releases are signed, and automatic updates are optional.
DNS change history
Get alerted the moment a record changes, with the change history kept. Useful for audits, rollbacks and spotting a hijacked domain. See detecting hijacked DNS records.
Flows for API sequences
A flow monitor calls your API step by step: log in, create a resource, read it back. Save a value from one step, such as a token or an id, and use it in the next. Secrets are encrypted and never shown again, and the first step that fails stops the flow.
Automate everything
The REST API on Professional and Business covers monitors, maintenance windows and status updates, documented with an OpenAPI document at app.uptimecheck.com/docs/api. Create monitors from your deploy step and start a maintenance window before a release. Keys are read-only or read and write. An MCP server lets Claude and other AI assistants do the same with an API key: ask whether everything is up, or pause the shop while you deploy.
Alerts go wherever your team works: email, Slack, Microsoft Teams, Discord, Google Chat, Mattermost, Telegram, PagerDuty, ntfy, Pushover and push notifications on your phone. Webhooks send JSON to any URL, signed so the receiver can verify it.
A setup in an afternoon
- Add a cron job monitor to each scheduled job, starting with backups.
- Install the server agent on the machines that matter and set CPU, memory and disk limits.
- Add DNS monitors for your main domains: NS, A, MX and TXT.
- Route alerts to the team channel, and a push alert only for what must wake someone.
- Move the setup into code with the API once it works.
The result is monitoring that catches the quiet failures as reliably as the loud ones, in the same tool and the same alert channel. When something goes wrong at night, the person on call sees the disk, the missed job and the failing check side by side.
No agents to babysit for most checks
Uptime, API, flow, SSL, domain and DNS checks run from Uptimecheck itself, and cron jobs only send a request from your job, so there is nothing to install for most of your monitoring. Only server monitoring needs the agent on the machine it measures.
The REST API and MCP server are included on Professional and Business. Plans start at €9 per month billed yearly or €12 billed monthly, excl. VAT, with a 14-day free trial and no credit card. See the pricing page, or look around the live demo first.