Monitoring for your nightly backups, weekly reports, cron jobs and background tasks.

Make HTTP requests to the Ping URL at regular intervals. When the URL is not pinged on time, Status will send you an alert. You can monitor any service that can make HTTP requests or send emails.

For each of your periodic tasks, Status provides an unique URL similar to this one:
# m h dom mon dow command
  8 6 *   *   *   /home/user/ && curl -fsS -m 10 --retry 5 -o /dev/null
# using curl (10 second timeout, retry up to 5 times):
curl -m 10 --retry 5
# using wget (10 second timeout, retry up to 5 times):
wget -T 10 -t 5 -O /dev/null
# Using Python 3 standard library:
import socket
import urllib.request

    urllib.request.urlopen("", timeout=10)
except socket.error as e:
    # Log ping failure here...
    print("Ping failed: %s" % e)
# Using the requests library:
import requests

    requests.get("", timeout=10)
except requests.RequestException as e:
    # Log ping failure here...
    print("Ping failed: %s" % e)
require 'net/http'
require 'uri'

var https = require('https');
https.get('').on('error', (err) => {
    console.log('Ping failed: ' + err)
package main

import "fmt"
import "net/http"
import "time"

func main() {
    var client = &http.Client{
        Timeout: 10 * time.Second,

    _, err := client.Head("")
    if err != nil {
        fmt.Printf("%s", err)
using (var client = new System.Net.WebClient())
// the server returns appropriate CORS headers so cross-domain AJAX requests work:
var xhr = new XMLHttpRequest();'GET', '', true);
# inside a PowerShell script:
# Without an underlying script, passing the command to PowerShell directly:
powershell.exe -command &{Invoke-RestMethod}

As an alternative to HTTP requests, you can also report "liveness" by sending email messages.

You can instruct Status to look for a particular keyword in the subject line. This is handy when your backup software sends an email after every run, and uses a different subject line depending on success or failure.

A quick peek of what's inside:

My Checks page

Live-updating Dashboard

A list of your checks, one for each Cron job, daemon or scheduled task you want to monitor.

Give names and assign tags to your checks to easily recognize them later.

Tap on the integration icons to toggle them on and off.

Adjust Period and Grace time to match the periodicity and duration of your tasks.

Period/Grace Time dialog

Simple Configuration

Each check has configurable Period and Grace Time parameters. Depending on these parameters and time since the last ping, the check is in one of the following states:
New. A check that has been created, but has not received any pings yet.
Up. Time since last ping has not exceeded Period.
Late. Time since last ping has exceeded Period, but has not yet exceeded Period + Grace.
Down. Time since last ping has exceeded Period + Grace. When check goes from "Late" to "Down", Status sends you a notification.
Cron dialog

Cron Expression Support

Alternatively, you can define the expected ping dates and times using a cron expression. See Cron Syntax Cheatsheet for the supported syntax features.

Grace Time specifies how "late" a ping can be before you will be alerted. Set it to be a little above the expected duration of your cron job.

Details Page

Details and Event Log

You can add a longer, free-form description to each check. Leave notes and pointers for yourself and for your team.

You can also see the log of received pings and sent "Down" notifications.

Details Page

Public Status Badges

Status provides status badges for each of the tags you have used. Additionally, the "Status" badge shows the overall status of all checks in your account.

The badges have public, but hard-to-guess URLs. You can use them in your READMEs, dashboards or status pages.

Set up multiple ways to get notified:





Microsoft Teams

Incident Management

Incident Management

Incident Management icon
Incident Management

Incident Management


What Can I Monitor With Status?

Cron Jobs

Status monitoring is a great fit for cron jobs and cron-like systems (systemd timers, Jenkins build jobs, Windows Scheduled Tasks, wp-cron, uwsgi cron-like interface, Heroku Scheduler, ...). A failed cron job often has no immediate visible consequences, and can go unnoticed for a long time.

Specific examples:

  • Filesystem backups
  • Database backups
  • Daily, weekly, monthly report emails
  • SSL renewals
  • Business data import and sync
  • Antivirus scans
  • Dynamic DNS updates

Processes, Services, Servers

Status monitoring can be used for lightweight server monitoring: ensuring a particular system service, or the server as a whole is alive and healthy. Write a shell script that checks for a specific condition, and pings Status if successful. Run the shell script regularly.

Specific examples:

  • Check a specific docker container is running
  • Check a specific application process is running
  • Check database replication lag
  • Check system resources: free disk, free RAM, ...
  • Send simple, unconditional "I'm alive" messages from your server (or your NAS, router, Raspberry Pi, ...)