LastPing
Monitoring for AI agents, cron jobs and CI/CD
curl -fsSL https://raw.githubusercontent.com/tp322d/lastping-app/main/install.sh | shhttps://mcp.lastping.dev/Details
- Target Audience
- DevelopersDevOps EngineersAI Developers
- Pricing
- Free
Discovery signals
How AI and people discover LastPing on PeerPush
Sep 28, 2026
About LastPing
LastPing is dead-man's-switch monitoring that makes sure your background processes are actually running. It watches cron jobs, backups, CI/CD pipelines, and AI agents from a single console, and the moment a monitored process goes silent it fires an alert with failure details for every incident — so you catch silent failures before they become outages. LastPing is built AI-agent-first. Connect your agent through the MCP server and it can create its own monitors and alerts — then LastPing watches for the ways agents actually fail: the run that dies mid-task, the one that hangs and never checks in, and the one that reports success without doing the work. A silent success is still a failure. Your agents monitor themselves, and you hear about it the moment something's off. There's also an open-source Go CLI for wiring checks into scripts and pipelines in one line. Free for individuals — no credit card, no trial clock.
Product Video
Watch a video demo of LastPing.
Screenshots
Reviews (5)
Average 5.0 out of 5
Based on 5 reviews
Comments (4)
The dead-man’s-switch framing is compelling, especially for agents that can hang or report success too early. MCP-created monitors plus the open-source Go CLI make this useful for both automated and traditional pipelines.
The distinction between “agent reported success” and “job actually checked in” is excellent. I’d love to see a ready-made pattern for long-running agents: heartbeat interval, grace window, and what context gets attached to an alert.
A dead-man's switch for cron jobs, backups, CI, and agents is the right alert model: silence is the failure, not a green dashboard you forget to check. One console for processes that must keep running is easy to justify.
Built it for my own infra first. A dead agent and a thinking agent look identical - no exit code, no error, it just goes quiet. LastPing watches for the signal that never arrives.