LastPing vs Opsgenie Heartbeats — a modern, free Opsgenie heartbeat alternative
Atlassian is retiring Opsgenie, with support ending April 2027. If you rely on Opsgenie heartbeats to monitor cron jobs and background tasks, you need to migrate. LastPing is a free, fully-hosted alternative with no monitor cap, CI/CD pipeline monitoring built in, and a migration that takes one URL change.
Opsgenie EOL notice: Atlassian has announced the retirement of Opsgenie as a standalone product. Support ends April 2027. Teams using Opsgenie heartbeats should plan their migration to a maintained alternative before then.
The honest verdict
Opsgenie was a well-regarded on-call and alerting platform with a useful heartbeat monitoring feature. The retirement is an Atlassian strategic decision, not a reflection on the product itself. If you were using Opsgenie heartbeats to catch silent cron failures, the functionality worked well and you should plan a straightforward migration.
LastPing is a natural migration target. Both tools use the same GET-request heartbeat mechanism — your job pings a URL when it completes. Migrating is swapping the URL. Where LastPing goes further: it covers CI/CD pipelines as first-class monitors, is free with no monitor cap, and ships an agent-first MCP server so AI coding tools can manage monitors without opening a browser.
Feature by feature
What Opsgenie heartbeats offered, and what you get with LastPing.
| Capability | LastPing | Opsgenie Heartbeats |
|---|---|---|
| Product status | ✓ Active — under development | ✗ EOL — support ends April 2027 |
| Free tier monitor cap | ✓ No cap — unlimited monitors free | ◐ Included in Opsgenie plan (which is EOL) |
| Cron / heartbeat monitoring | ✓ Curl a ping URL; cron or simple-interval schedules, grace windows, time zones | ✓ Same GET-request mechanism — your job pinged a URL on completion |
| CI/CD pipeline monitoring | ✓ Included free — one signed webhook (GitHub Actions, GitLab CI, Jenkins), zero YAML | ✗ Heartbeat-only — no CI/CD pipeline integration |
| CI/CD failure-reason detail | ✓ Deep link to the run + optional failing-step log excerpt on the incident, free | ✗ Not applicable |
| Agent-first MCP server | ✓ AI agents can create, query, and silence monitors via MCP | ✗ |
| HTTP / uptime probing | ✓ Status code, latency, keyword checks | ✗ Heartbeat-only |
| Alert channels | ◐ Email, Telegram, Slack, Discord, signed webhook — no SMS/phone | ✓ Rich on-call alerting was a core Opsgenie strength |
| On-call scheduling | ✗ Routing rules but no on-call schedules today | ✓ Full on-call scheduling — a core Opsgenie feature |
| Teams & multi-user | ✗ Single-user today (top roadmap item) | ✓ Full team and escalation support |
| Public status pages | ✓ Public status pages + embeddable badges, free | ✗ |
Migrate from Opsgenie heartbeats in minutes
Both tools use the same GET-request mechanism. Migrating is replacing the URL your cron job pings when it finishes.
curl -X GET "https://api.opsgenie.com/v2/heartbeats/<name>/ping" \
-H "Authorization: GenieKey <api-key>"
# after — LastPing (no auth header required)
curl -fsS https://ping.lastping.dev/<id>
Create a monitor in LastPing (takes under two minutes), set the same
period and grace window you had in Opsgenie, and replace the Opsgenie
ping call with the LastPing URL. No API key header required — the
monitor ID in the URL is the credential. Signal failure by appending
/fail
to the URL before your job exits with a non-zero code.
Questions people ask
Front-loaded answers — the most important fact first.
-
Is Opsgenie heartbeat being discontinued?
Yes. Atlassian is retiring Opsgenie as a standalone product, with support ending in April 2027. If you use Opsgenie heartbeats to monitor cron jobs or background tasks, you need to migrate before that date.
-
What is the best free Opsgenie heartbeat alternative?
LastPing is a free Opsgenie heartbeat alternative with no monitor cap and no paid tier. It monitors cron jobs and scheduled tasks via a simple ping URL (the same mechanism as Opsgenie heartbeats) and additionally monitors CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins) via one signed webhook. Migration is a single URL change.
-
How do I migrate from Opsgenie heartbeats to LastPing?
Create a monitor in LastPing, then replace the Opsgenie heartbeat ping URL in your cron job with the LastPing ping URL. Both use the same GET-request mechanism — your job curls a URL when it completes, and the monitor fires an alert if it stops receiving pings. No library or code changes beyond swapping the URL.
-
When does Opsgenie support end?
Atlassian has announced the end of support for Opsgenie in April 2027. After that date, the product will no longer be maintained or supported. Teams relying on Opsgenie heartbeats for cron job monitoring should plan their migration before then.
-
Does LastPing have CI/CD pipeline monitoring that Opsgenie lacked?
Yes. Opsgenie heartbeats covered cron and background task monitoring but had no native CI/CD pipeline integration. LastPing monitors GitHub Actions, GitLab CI, and Jenkins pipelines as first-class monitors via one HMAC-signed webhook — zero YAML changes — catching runs that fail, hang, or never start, with failure detail attached to the incident. GitHub Actions guide →
Migrate from Opsgenie before April 2027.
One URL change to migrate your cron monitors. Add CI/CD pipeline coverage while you're at it — it's free and takes two minutes.