LastPing.dev Reviews and Details

Questions & Answers

1. What makes LastPing.dev unique?

   LastPing is a dead-man's-switch for jobs that can fail silently, including AI agents. Most monitoring watches for errors. LastPing watches for signals that stop arriving: a cron job that never checked in, a backup that didn't finish, a CI run that hung, an agent that stopped making progress. It is built agent-first. A hosted MCP server with 50 tools lets an assistant like Claude, ChatGPT or Cursor create its own monitors, wire the ping and read incidents. Agent runs report started, progress, blocked and failed, and traced runs show spans, tokens and estimated cost over OpenTelemetry. The same engine covers cron, CI/CD (GitHub Actions, GitLab CI, Jenkins) and HTTP uptime. An official Terraform provider covers monitoring as code.

2. Why should a person choose LastPing.dev over its competitors?

   • Free for individuals: no credit card, no monitor cap, no feature gate.
   • One tool for every kind of silent failure: cron and heartbeats, CI/CD webhooks, HTTP probes and AI agent runs share one incident model.
   • Agents can set it up themselves: the MCP server and the Terraform provider mean an assistant or a pipeline can configure monitoring, not just a person clicking through a UI.
   • Honest alerting: one incident per problem, not a storm of notifications. Nine destinations: email, Slack, Discord, Telegram, ntfy, Pushover, Microsoft Teams, Google Chat and a signed webhook. Incidents close on their own when the job checks back in.
   • It monitors itself in public: LastPing's own ingest, API, MCP server and login are on a public status page anyone can open.

3. How would you describe the primary audience of LastPing.dev?

   Developers, DevOps engineers and SREs who run scheduled or long-running work: cron jobs, backups, CI pipelines, and more and more AI agents. They want to know when something quietly stopped, not days later. It suits side projects through to production teams, and especially people building with AI coding assistants and agent frameworks who want their agents' runs watched.

4. Which are the primary technologies used for building LastPing.dev?

   Go, PostgreSQL, React with TypeScript, AWS, Terraform, OpenTelemetry and the Model Context Protocol (MCP).

5. What's the story behind LastPing.dev?

   LastPing is built and operated by engineer. He had been on the receiving end of a job that stopped running three weeks before anyone noticed. Most tools alert on things that happen; the failures that hurt most are the ones where nothing happens at all. LastPing started as a dead-man's-switch for cron and backups. As AI agents began running real work, it grew to watch agent runs too, because a stopped agent looks exactly like a thinking one. Agents can also set up their own monitoring through MCP. The CLI, the MCP server and the Terraform provider are open source.