Monitoring for the things
that fail quietly.
LastPing is a free, fully-hosted resilience tool for developers and SREs who are tired of finding out a cron job, backup, or CI pipeline died days ago. It watches for expected signals — and pages you when they stop arriving. No paid tier, no lock-in, no infra to run.
What LastPing is
Most monitoring tools watch for things that happen. LastPing watches for things that stop happening — the heartbeat that never checked in, the backup that didn't phone home, the CI job that ran in silence and failed.
Absence-based detection
Each monitor has a durable deadline. When a heartbeat ping arrives, the deadline resets. When it doesn't — the detector catches the overdue deadline and opens an incident. There's no polling race, no flaky threshold. Either the signal arrived or it didn't.
This makes LastPing well-suited for scheduled work: cron jobs, backup scripts, data-pipeline runs, certificate renewals — anything that should happen on a known cadence but has no native alerting.
Three monitor types
Heartbeat / dead-man's switch — send a ping after your job succeeds; LastPing alerts you if the ping stops arriving.
CI/CD signals — receive signed webhooks from GitHub Actions, GitLab CI, and Jenkins with deep links back to the run.
Active HTTP probes — check any URL on a schedule for status code, response time, and keyword presence.
Honest alerting
Alerting in LastPing is built around incidents, not raw notifications. An incident opens when something goes wrong and closes when it resolves — no duplicate pages for the same problem. Channels (email, Slack, Discord, Telegram, webhooks) attach to monitors via a routing matrix, so each team gets exactly the alerts that matter to them.
Custom message templates let you write alert copy that's actually readable — context, runbook links, whatever your on-call team needs.
Free, and fully hosted
LastPing has no paid tier and no feature gate. The hosted version at app.lastping.dev is free for everyone. No setup, no infra required — everything runs on our infrastructure.
Follow development and file issues at github.com/tp322d/lastping-app. GitHub is the project home.
Who uses it
If you've ever been surprised by a silent failure — a job that ran without alerting, a backup that stopped, a CI check that never fired — LastPing is for you.
Teams shipping software
Wire LastPing into GitHub Actions, GitLab CI, or Jenkins in minutes. Know when a pipeline silently fails, a deploy goes quiet, or a scheduled task misses its window.
Infrastructure teams
Attach heartbeat monitors to backup scripts, certificate renewals, and database maintenance jobs. Get an incident when the job that should have run at 03:00 didn't show up by 03:05.
People who ship and operate software
Whether you run a side project or a production service, LastPing gives you the same silent-failure detection that large ops teams use — free, with no tier limit or feature gate.
How it's built
A small set of stateless Go services around a Postgres database and an SQS-compatible queue. Absence detection is durable — it survives restarts because deadlines live in the database, not in memory.
- ingest Receives heartbeat pings and CI webhook events, validates HMAC signatures, and enqueues work.
- processor Consumes the queue, updates monitor state in Postgres, and writes durable detection deadlines.
- detector Polls Postgres for overdue deadlines; transitions monitors up → late → down and opens incidents.
- prober Sends HTTP probes to user-configured URLs on a schedule; feeds results into the processor queue.
- notifier Delivers alerts via email, Slack, Discord, Telegram, and webhooks when incidents open or resolve.
- api REST API backing the console: monitors, incidents, channels, projects, and user accounts.
Follow development and file issues at github.com/tp322d/lastping-app. See the project page for more about LastPing.
The ethos
Resilience tooling should be trustworthy, accessible, and free from hidden incentives. LastPing tries to live up to that.
Free, with no catch
There is no paid plan, no enterprise tier, no "free up to N monitors." The hosted service is free, and fully hosted. That's the whole model.
Follow the project on GitHub
Development is tracked on GitHub. File issues, follow what's coming next, and reach the team at github.com/tp322d/lastping-app.
No money-grab
There is no paid plan hiding behind the free tier, no enterprise upsell, no bait-and-switch. Free means free.
Your data, and how long we keep it
LastPing stores only what it needs to monitor your jobs: your monitors' configuration, the check-in timestamps they receive, the incidents and event history those produce, your alert destinations, and your account details.
Retention. Your monitoring data is kept for as long as your account is active — there is no automatic expiry. Delete a monitor and its check-in and incident history is removed with it. To close your account and delete all of its data, email us and we'll take care of it.
Delivery safety. Email destinations use confirmed opt-in, and outbound alert delivery is SSRF-guarded, so an alert can never be used to reach internal or cloud-metadata addresses. Infrastructure runs in the EU (Frankfurt). Questions about your data? hello@lastping.dev.
Know when things go quiet.
Start monitoring the cron jobs, backups, and CI pipelines you've been hoping don't silently fail. No credit card, no tier, no upsell.