A stopped agent looks exactly like a thinking one.

LastPing is AI agent monitoring: it alerts you when your AI agents fail, stall, wait for your approval or never start, and watches the cron jobs and CI/CD pipelines around them, with HTTP uptime checks alongside. Instead of polling your jobs, it waits for them to check in. If one goes silent (an agent run that stalled, a cron that never ran, a CI pipeline that hung), LastPing opens an incident and alerts you before your users notice.

Yes. LastPing is free for individuals at app.lastping.dev, with no monitor cap and no feature gate. Sign up with Google, GitHub or email and start monitoring immediately. Everything runs on our infrastructure; no setup required. Follow the project at github.com/lastping-dev/lastping-app.

Alerts fire automatically on the very first check you create. LastPing emails the account owner by default, with no routing to configure. You can add Slack, Discord, Telegram, ntfy, Pushover, Microsoft Teams, Google Chat or a signed outbound webhook and choose which events reach which channel per check.

Yes. LastPing supports three monitor types: heartbeat (cron/scheduled jobs that ping when they finish), CI/CD signals (signed webhooks from GitHub Actions, GitLab CI, Jenkins, zero YAML, deep-link to the run on alert), and HTTP/uptime probing (LastPing polls your URL on a schedule for status code, latency, and keyword presence).

Healthchecks.io is an excellent heartbeat monitor for cron jobs. LastPing covers cron jobs the same way (your job curls a ping URL) and additionally treats CI/CD pipelines as first-class monitors: one signed webhook from GitHub Actions, GitLab CI, or Jenkins, no curl step in every workflow, catching runs that fail, hang, or never start, with failure detail on the incident. LastPing is free for individuals with no monitor cap. Full comparison: lastping.dev/vs/healthchecks/