See LastPing in action.
LastPing watches your cron jobs, CI pipelines, and HTTP endpoints for silence. This walkthrough shows the full detection story — a monitor drifts from up to late to down, an incident opens, an alert fires to Discord, then the job recovers and the incident closes. The UI language below is the actual LastPing console.
Animated console walkthrough
- cert-renew is down — silent for 3h (missed its check-in window)
- Incident #INC-042 opened automatically
- ✉ Alert sent to Discord #ops-alerts
- nightly-backup and api.example.com are up throughout
- When cert-renew checks in → incident closes, recovery alert fires
What you're seeing.
LastPing doesn't poll your services to see if they're up. It waits for them to check in. Miss the window and LastPing opens an incident and alerts you — before your users notice.
Up → late: the grace window
Each monitor has an expected check-in interval and a grace period. cert-renew was expected every hour. When it doesn't ping in the grace window, status flips to late. No alert yet — this is the grace period.
Down: incident opens, alert fires
Past the grace period, status flips to down. LastPing opens one incident and fires one alert — not a storm. The Discord message carries the monitor name, silence duration, and a link to the incident.
Recovery: incident closes automatically
When the job checks back in, the incident closes and a recovery alert fires. No manual reset. The history is written to the event log for post-mortems.
Your real console is one sign-up away.
The demo above uses canned data. The real thing hooks into your cron jobs, CI pipelines, and HTTP endpoints in under a minute — no agent, no library, just a curl call at the end of your job.