How it works

Three pings tell the whole story.

Create a monitor, add one line to your job and let Cronitorex correlate the pings into a timeline. When a ping is late or missing, the alert reaches you within 60 seconds.

Start free → Read the docs

invoice-sync run and complete, every 5 minutes

From zero to monitored in three steps

Create a monitor

Pick a name like db-backup and tell Cronitorex how often the job should run. That schedule becomes the contract your job has to keep.

Add a ping to your job

Send run when the job starts and complete or fail when it ends. Anything that can make an HTTP request can send a ping.

Get alerts that matter

Cronitorex builds a timeline from your pings, detects missed and failed runs and alerts you by email, Telegram, Discord, Slack or webhook.

The same job, wrapped four ways

Pick whatever fits your stack. Every variant talks to the same API with the same three states: run, complete, fail.

0 2 * * * curl -fsS "https://api.cronitorex.com/ping/db-backup?api_key=$CRX_KEY&status=run" >/dev/null; /usr/local/bin/backup.sh && curl -fsS "https://api.cronitorex.com/ping/db-backup?api_key=$CRX_KEY&status=complete" >/dev/null || curl -fsS "https://api.cronitorex.com/ping/db-backup?api_key=$CRX_KEY&status=fail" >/dev/null

#!/usr/bin/env bash
set -euo pipefail

ping() {
  curl -fsS "https://api.cronitorex.com/ping/db-backup?status=$1" \
    -H "Authorization: Bearer $CRONITOREX_API_KEY" >/dev/null
}

ping run
if /usr/local/bin/backup.sh; then
  ping complete
else
  ping fail
fi

import os, requests

API = "https://api.cronitorex.com/ping/db-backup"
HEADERS = {"Authorization": "Bearer " + os.environ["CRONITOREX_API_KEY"]}

requests.get(API, params={"status": "run"}, headers=HEADERS)
try:
    run_backup()
    requests.get(API, params={"status": "complete"}, headers=HEADERS)
except Exception:
    requests.get(API, params={"status": "fail"}, headers=HEADERS)
    raise

curl -fsS "https://api.cronitorex.com/ping/db-backup?status=run" \
  -H "Authorization: Bearer $CRONITOREX_API_KEY"

/usr/local/bin/backup.sh

curl -fsS "https://api.cronitorex.com/ping/db-backup?status=complete" \
  -H "Authorization: Bearer $CRONITOREX_API_KEY"

When the ping does not arrive

Silence is a signal too. Cronitorex expects the next run within the interval you set, plus a grace period that absorbs normal jitter.

report-daily grace period open

Late, inside the grace period

The run ping has not arrived yet, but the grace period is still open. The run is marked late and no alert is sent.

db-backup missed run, alert sent

Missed

The grace period passed without a ping. Cronitorex raises a missed alert: the job did not run at all.

invoice-sync exit 1, alert sent

Failed or timed out

A fail ping, or a run ping with no ending before the time limit, marks the run as failed and alerts immediately.

One request, end to end

your job

ping

Cronitorex

alert channels

A ping is a single HTTPS request. Correlation, detection and alerting happen on the Cronitorex side.

Start monitoring in 60 seconds

Start free → Read the docs