LastPing

Frequently looked up

Q1What is LastPing?

LastPing is a dead-man's-switch monitor for scheduled jobs, CI/CD pipelines, and HTTP endpoints. Instead of actively pinging your services, it waits for them to check in. If a job goes silent (a cron that never ran, a CI pipeline that hung, a long job that stopped making progress mid-way, an endpoint that stopped responding), LastPing opens an incident and alerts you before your users notice.

Q2Is LastPing free?

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 the infrastructure; no setup required.

Q3Does LastPing support CI/CD pipelines and HTTP uptime?

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).

Q4Can LastPing monitor GitHub Actions workflows?

Yes. Point one signed webhook at LastPing from your repository settings, ticking both the Workflow runs (workflow_run) and Workflow jobs (workflow_job) events, with zero changes to your workflow YAML. LastPing alerts when a run fails, hangs, or never starts (including scheduled workflows GitHub disables after 60 days of inactivity in a public repo, without notifying anyone when it happens), deep-links to the run, and can attach the failure log excerpt to the incident.

Q5What alert channels does LastPing support?

LastPing delivers alerts by email, Slack, Discord, Telegram, signed outbound webhooks, ntfy, Pushover, Microsoft Teams and Google Chat. Email channels use confirmed opt-in, and delivery is SSRF-guarded so alerts can never reach internal or cloud-metadata addresses.