# Lateping > Lateping is heartbeat monitoring for cron jobs and scheduled tasks. A job calls its check's URL when it finishes; if the call doesn't arrive by the deadline (a period or a cron expression in a timezone, plus a grace period), Lateping sends an alert by email, Slack, Discord or a signed webhook. Key facts: - Ping URL: `https://lateping.com/p/` records a successful run. `/p//start` records a start (for run times); `/p//fail` records a failure and alerts within a minute. `/p//` (0 to 255) records a success for 0 and a failure for anything else, with the code shown on the alert, for example `cmd; curl -fsS -m 10 --retry 5 -o /dev/null https://lateping.com/p//$?`. Any HTTP method works. Responses: 200 recorded, 404 unknown check, 500 our error (retry). - Recommended call, after the job's work: `curl -fsS -m 10 --retry 5 -o /dev/null https://lateping.com/p/` - Unusual run times (Pro and above): a run that sent `/start` and then reports success far faster or slower than its last 20 timed runs sends an alert, for example "finished in 2s, usually 6m". It tells you when a job finishes suspiciously fast, with nothing to set up, needs 10 timed runs first, and can be switched off per check. Webhook event: `check.unusual`. - Lateping's own downtime never becomes a customer's alert: deadlines that fell inside an outage move back by its length, and alerts are held if a large share of checks go late at once. - Plans (USD, tax added at checkout): Free, 10 checks, email alerts, 7-day history. Pro, $12/month or $120/year: 50 checks, Slack, Discord and webhook alerts, run analytics, API, 1-year history. Team, $39/month or $390/year: 300 checks, priority support. Founding, $90/year for the first 50 buyers: Pro limits, price locked. - Sign-in: emailed link, passkey, or Google or GitHub; optional two-factor. No passwords. - Privacy: no IP addresses stored, only a country code per ping. No tracking cookies. - GitHub Action: `lateping/ping@v1` (https://github.com/lateping/ping, MIT). - Sign up: https://app.lateping.com/signup. Support: support@lateping.com. ## Guides - [GitHub Actions scheduled workflow not running](https://lateping.com/guides/github-actions): GitHub disables scheduled workflows after 60 days without activity, and delays or drops runs under load. How to check, and how to get an email next time. - [Monitor Cloudflare Workers Cron Triggers](https://lateping.com/guides/cloudflare-workers): Ping a URL from your scheduled() handler and get an email when a Cloudflare Cron Trigger is late, stops firing, or throws. - [Find out when a crontab job fails silently](https://lateping.com/guides/crontab): Add one curl after a crontab command and get an email when the job fails, never runs, or the server is down. - [Monitor Vercel Cron Jobs](https://lateping.com/guides/vercel-cron): Ping a URL from the function a Vercel Cron Job calls and get an email when the job is late, never runs, or throws. - [Monitor pg_cron jobs in Postgres](https://lateping.com/guides/pg-cron): Send a ping from inside Postgres with pg_net when a pg_cron job commits, and get an email when it fails or stops running. - [Monitor Kubernetes CronJobs](https://lateping.com/guides/kubernetes-cronjobs): Ping a URL from a Kubernetes CronJob's container and get an email when the job fails, is skipped, or never starts. - [Monitor systemd timers](https://lateping.com/guides/systemd-timers): Ping a URL from a systemd service when its timer runs it, and get an email when the run fails, is skipped, or the timer isn't running at all. - [Get alerted when a backup job stops running](https://lateping.com/guides/backup-jobs): Ping a URL from a backup script only when the dump and upload both worked, and get an email when a backup fails, comes out empty, or doesn't run. - [Monitor the Laravel scheduler](https://lateping.com/guides/laravel-scheduler): Use Laravel's pingOnSuccess and pingOnFailure for each scheduled task, plus a heartbeat that catches a scheduler that stopped running. - [A dead man's switch for cron jobs](https://lateping.com/guides/dead-mans-switch): A dead man's switch alerts when a job stops checking in, catching jobs that never run. How it works, and how to set one up in five minutes. - [How to know if a cron job failed](https://lateping.com/guides/how-to-know-a-cron-job-failed): cron ignores exit codes and its mail rarely arrives. Check the logs, make the script fail loudly, then ping a URL to catch jobs that never run. - [Cron job didn't run because the computer was off (anacron)](https://lateping.com/guides/anacron): Cron skips jobs while a machine is off. Anacron runs them late, once a day. Add a heartbeat so you know when a daily job was missed. - [How to get an alert with the exit code when a cron job fails](https://lateping.com/guides/cron-job-exit-code): Append the job's exit code to a ping URL: cron's $? tells Lateping which code failed, and a non-zero code alerts you within a minute. - [Cron job running twice at the same time (overlapping runs)](https://lateping.com/guides/cron-job-overlapping): A cron job that takes longer than its interval starts a second copy. Use flock to skip the overlap, and send its exit code so a skipped run shows up. - [Cron job hangs and never finishes (kill it with timeout)](https://lateping.com/guides/cron-job-timeout): A hung cron job blocks every later run. Wrap it in timeout(1) so it is stopped after a set time, and send exit code 124 so the timeout shows up. - [Cron job runs at the wrong time (timezone and daylight saving)](https://lateping.com/guides/cron-job-timezone): cron uses the server's timezone, and daylight saving can skip or repeat a run. Check the zone, set CRON_TZ, and match the check's timezone. - [How to retry a failed cron job](https://lateping.com/guides/cron-job-retry): cron never retries a failed job. Wrap the command in a short retry loop, and alert only if the last attempt fails. ## Docs - [Ping URL reference](https://lateping.com/guides#ping-urls): the three ping URLs, responses, and timing a run. - [Pricing](https://lateping.com/pricing): plans, limits and billing questions. - [Full text of every guide](https://lateping.com/llms-full.txt): this file's guides as Markdown, in one document. ## Optional - [Privacy policy](https://lateping.com/legal/privacy) - [Terms of service](https://lateping.com/legal/terms) - [Refund policy](https://lateping.com/legal/refunds) - [Public issue tracker and security policy](https://github.com/lateping/lateping)