Two on-call tools are shutting down. The dates, and what to decide before April 2027

Last updated 14 November 2026

By Mumen Tayyem, founder of Jabee

Published 14 November 2026. Every date below is from the vendor's own published pages, read on that day.

Two widely deployed on-call tools are going away inside the same window, and the deadlines are the kind that delete data rather than the kind that slip. If either one pages your team today, the dates are worth having on a wall. If you are mid-migration, the second half of this piece is about the question migrations skip: whether the alerts themselves still need to work the way they did.

When does Opsgenie shut down?

Atlassian ends Opsgenie support on 5 April 2027. On that date access is shut off, the REST APIs stop responding, and unmigrated data is deleted. Sales to new customers already ended on 4 June 2025. Atlassian's stated path is a migration to Jira Service Management, after which Opsgenie stays available in parallel for 120 days and then shuts itself off, which can be earlier than April 2027 if you migrate early.

Those are the three numbers to plan around: 5 April 2027 for the hard stop, data deletion on the same date, and a 120-day parallel window that starts whenever your migration does.

What happened to Grafana OnCall?

Grafana OnCall OSS went into maintenance mode on 11 March 2025 and the repository was archived on 24 March 2026 — read-only, with only severe CVEs patched. The Cloud Connection that provided mobile push, SMS and phone calls to self-hosted installs stopped working the same day. The code is AGPLv3 and a self-hosted install keeps running for as long as you are willing to operate an unmaintained pager, which is a sentence that answers itself for most teams. Grafana's successor is its cloud IRM product.

What to check before you pick a replacement

The replacement market is loud right now, and almost everything written about these two shutdowns is written by a vendor hoping to be the destination. Four checks that cut through most of it:

The question migrations skip: the channel

A migration copies the old delivery assumption: alerts arrive in a dedicated app that everyone must install, keep logged in, and exempt from Do Not Disturb. That assumption is the main thing the app-based tools sell, and for a team running rotations and escalation policies it is the right buy.

But a lot of teams on these tools never ran a rotation. The job was "the server alert must reach the two of us, reliably, on the phone we actually look at". For that job, the shutdown is a chance to simplify rather than re-buy: the app people already have open is WhatsApp, and an alert can arrive there over Meta's official Cloud API without a WhatsApp Business Account, a registered number, or an approved template of your own, because the number and the template can be the provider's.

What that route looks like, concretely: a curl from anything that can make an HTTP request, a Grafana or Alertmanager contact point, a heartbeat check for the cron job that stops running, and the alert lands as a WhatsApp message on a verified phone, with delivery confirmed. The first three are free, which is enough to watch one arrive before deciding anything.

Honesty about where that is the wrong answer: it is a notifier, not a pager. There are no rotations, no escalation after a missed acknowledgement, and alerts go to one verified handset per business — to reach a whole team each person verifies, or you connect a number of your own. If you ran schedules and escalation chains in the tool you are leaving, you need another pager, and the checks above are how to pick one. If what you ran was "message me and my co-founder when it breaks", you may not need a pager at all.

Questions

When does Opsgenie stop working? Atlassian ends support on 5 April 2027. Access is shut off, the REST APIs stop responding, and unmigrated data is deleted on that date. If you migrate to Jira Service Management earlier, Opsgenie remains available in parallel for 120 days after the migration and then shuts itself off.

Is Grafana OnCall still maintained? No. The open source project entered maintenance mode on 11 March 2025 and the repository was archived, read-only, on 24 March 2026. The Cloud Connection that gave self-hosted installs mobile push, SMS and phone calls stopped working the same day. Self-hosted installs keep running but receive no fixes beyond severe CVEs.

Will my Opsgenie data be migrated automatically? No. Atlassian offers a migration path to Jira Service Management, but it is something you run, and any data not migrated by 5 April 2027 is deleted. Exporting schedules, escalation policies and alert history early costs nothing and removes the deadline risk.

Can WhatsApp replace an on-call app for alerts? For alert delivery to a small team, yes: an alerts API over Meta's official Cloud API can message verified phones with no WhatsApp Business Account, number or template of your own. It is a notifier, not a pager — no rotations or escalation — so teams that relied on schedules and escalation chains still need an on-call tool.

What is a heartbeat check, and why does it matter in a migration? A heartbeat check alerts when an expected ping stops arriving — the cron job that silently stopped, the backup that never ran. Push-only alerting structurally cannot see those failures. If your current tool watches heartbeats, confirm the replacement does too, or those jobs become unmonitored the day you switch.

Sources

Written by Mumen Tayyem, founder of Jabee, in Dubai. Jabee sends WhatsApp alerts over Meta's official Cloud API with no number, account or template of your own: $29 a month for 500 alerts, and the first three are free.