LastPing
LastPing is a hosted monitoring service for developers running cron jobs and AI agents, with alerts when configured work fails, stalls or stops reporting.
Serves customers online
Updated
Who it is for, and who it is not for
- Small software teams managing both
Good to know
Individual access: Free for individuals.
Questions customers ask
What alert-delivery safeguards do you have during an outage of LastPing?
We monitor LastPing itself the same way, but monitoring is a best-effort service: network partitions, cloud outages, and software bugs can cause missed alerts.
What does it currently cost an organisation to use your service?
We are currently free for individuals; a paid team tier may be introduced in the future for teams and organisations.
What does it currently cost an organisation to use your service?
We are currently free for individuals; a paid team tier may be introduced in the future for teams and organisations. Currently no organization tier.
Investigation history?
Incidents are saved for up to 90 days.
Usage limits?
Effectively unlimited account.
Are your public status pages hosted independently of your monitoring service?
Our public status pages require no extra service.
Do you offer controls to redact sensitive information from agent telemetry?
We do offer controls to redact sensitive information from agent telemetry. Prompts are not shown and saved unless explicitily is agreed by an user.
What alert-delivery safeguards do you have during an outage of LastPing?
We monitor LastPing itself the same way, but monitoring is a best-effort service: network partitions, cloud outages, and software bugs can cause missed alerts. We use robust messaging systems and infrastructure that in most cases it survives any crash.
What does it currently cost an organisation to use your service?
We currently have no organisation tier; a paid team tier may be introduced in the future for teams and organisations. No organization tier yet so while individuals can use it for free from organization account sharing would be required.
How should I trial two job monitors to compare missed-run detection, alert delays and false alarms?
To fairly compare LastPing against a second job monitor, run both monitors in parallel on the exact same scheduled jobs and inject controlled failures. Mirroring live workloads eliminates timing drift and isolates how each platform handles grace periods, network retries, and notification delivery.
Are basic uptime checks enough to tell whether login and checkout work, or do I need a different kind of monitoring?
No it is not enough, you would need custom checks with calls to the LastPing address or some kind of synthetic checks.
Support availability?
No fixed hours.
Are your public status pages hosted independently of your monitoring service?
Our public status page is hosted independently of the monitoring services.
Changes and contact
| Contact | Detail |
|---|---|
| Website | lastping.dev |