Skip to main content

free tools / cron generator

Cron every hour

Here is the line. Cron will run it, but it will not tell you the day it stops.

  1. Add one ping to the end of the job.
  2. Tell Uptimepage how often to expect it.
  3. A missed ping opens an incident and alerts you by Slack, email, PagerDuty, SMS or webhook.
alert me if this job stops

Free plan, no card. Opens the new-monitor form as a heartbeat check.

crontab -e
# .----------- minute: 0 # | .--------- hour: any value # | | .------- day of month: any value # | | | .----- month: any value # | | | | .--- day of week: any value 0 * * * * /path/to/command # At minute 0 past every hour. That is 24 runs a day.

# next runs · your local time

    # the same job, reporting in after each good run 0 * * * * /path/to/command && curl -fsS $URL # $URL is the ping URL of an Uptimepage heartbeat check

    Add the line with crontab -e. Cron reads the server's time zone, which is often UTC.

    same schedule elsewhere

    Kubernetes CronJob

    spec:
  schedule: "0 * * * *"

    GitHub Actions

    on:
  schedule:
    - cron: '0 * * * *'

    GitHub runs schedules in UTC unless you set a time zone, and can start them late when it is busy.

    what to know

    The 0 in the first field matters. Both * * * * * and * */1 * * * run every minute, a common slip when the goal was hourly.

    Most cron versions and Kubernetes also take @hourly for this schedule; GitHub Actions does not. To run at half past each hour, use 30 * * * *.

    For anything else, build it in the cron expression generator.

    more free tools: uptime SLA calculator · error budget calculator · incident message generator · DNS lookup · HTTP header checker · SSL certificate checker · SSL certificate decoder · domain expiry checker · website security checker · the whole set