The main Splunk On-Call (VictorOps) alternatives in 2026 are AlertOps, PagerDuty, incident.io, Jira Service Management, Grafana Cloud IRM and Rootly. Splunk On-Call still runs and has no published end-of-life date, but teams switch when they want faster product development, AI noise reduction, two-way ITSM sync or on-call that covers IT operations beyond the engineering team.
Key takeaways
- Splunk lists On-Call from $5 per user per month on annual billing for up to 10 seats (Splunk pricing FAQ).
- Splunk has published no end-of-life date, so a move off Splunk On-Call runs on your schedule, not a vendor deadline.
- Look for on-call that is not an add-on, correlation that cuts noise before it pages anyone and two-way sync with your service desk.
- AlertOps Enterprise includes OpsIQ, two-way ServiceNow and Jira integration and a migration run by the Solution Engineering team at $28 per user per month on annual billing (AlertOps pricing).
Splunk On-Call started life as VictorOps, became part of Splunk and now sits inside Cisco. It still pages people reliably, and many teams have no urgent reason to leave. This guide is for the teams that do: what to look for in a replacement, six alternatives worth testing and how to switch without a gap in coverage.
Is Splunk On-Call being discontinued?
No end-of-life date has been published, and the product still runs. Splunk still lists it on its pricing pages, starting at $5 per user per month on annual billing for up to 10 seats (Splunk pricing FAQ). The question teams raise is about direction rather than shutdown. After two changes of ownership, many customers describe a product that is maintained rather than moving forward, while their own incident programs ask for more reporting, more automation and tighter service desk links.
That makes this a different decision from Opsgenie, which has a fixed support end date. With Splunk On-Call, you choose the timeline, run both tools in parallel for as long as you need and cut over once the new setup has earned trust.
What Splunk On-Call still does well
Credit where it is due. VictorOps built a good on-call product. The incident timeline threads alerts, chat and actions into one running record, routing keys send alerts to the right team, and alert rules can rewrite or enrich payloads before anyone is paged. For teams whose observability lives in Splunk, the path from a Splunk search to a page is short and familiar. Any replacement needs to match that daily experience, as well as the feature list.
Why teams look for Splunk On-Call alternatives
- Roadmap pace: Teams want AI correlation, automated postmortems and newer workflow features that they are not seeing added.
- Reporting: Leadership asks for MTTR, escalation and responder workload reporting that the tool struggles to produce.
- Service desk sync: ServiceNow and Jira shops want two-way sync of assignment, notes and closure rather than a one-way webhook.
- Wider rotations: IT operations, NOC staff and vendors join on-call, and they need phone-first paging and inbound call routing.
None of these points means Splunk On-Call stopped working. They mean the gap between what the incident program needs and what the tool delivers keeps growing, and that gap is cheaper to close on a calm schedule than during an outage review.
What to look for in a replacement
Start with the jobs Splunk On-Call does for you today, then add what is missing. On-call should be part of the platform, not a separate purchase. Correlation should group related alerts before they page anyone. Escalation should reach people by phone, SMS, email and app until someone acknowledges. Integration with your monitoring tools, Splunk included, should take minutes, and sync with your service desk should run both ways. Finally, check who runs the migration and whether you can test routing side by side before you switch.
Questions to ask every vendor on your shortlist
- Is on-call part of the plan you are quoting, or a separate product?
- Which plan includes alert correlation, and how does it decide which alerts belong together?
- Does the ServiceNow or Jira integration sync assignment, notes, status and closure in both directions?
- Can inbound phone calls reach whoever is on call, and on which plan?
- Who runs the migration, and can we test routing side by side with Splunk On-Call still live?
Splunk On-Call alternatives at a glance
| Tool | Best for | Starting paid list price |
|---|---|---|
| AlertOps | Teams that want on-call, escalation and OpsIQ in one platform | Standard $8 per user per month, annual billing; Enterprise $28 |
| PagerDuty | Large engineering organizations | Professional $21 per user per month, annual billing |
| incident.io | Slack-first engineering teams | Team $15 per user per month plus $10 for on-call |
| Jira Service Management | Atlassian shops | Standard $21.50 per agent per month |
| Grafana Cloud IRM | Teams on Grafana Cloud | Pro $19 platform fee, then from $20 per active user |
| Rootly | Teams focused on chat-based response and retrospectives | $20 per user for Incident Response plus $20 for On-Call |
1. AlertOps
AlertOps is an incident orchestration platform with on-call at its core. It has a pre-built Splunk integration among more than 200 integrations, so the alerts you send to Splunk On-Call today can go to AlertOps instead. AlertOps Enterprise includes OpsIQ, which correlates related alerts and cuts noise by up to 68%, and Agent Chronicle, which drafts the postmortem with up to 80% less prep time (AlertOps platform data). Two-way ServiceNow and Jira integrations, Heartbeat Monitoring and 24/7 live call routing round out the platform. For a ServiceNow-specific view, read migrating off Splunk On-Call while keeping ServiceNow.
2. PagerDuty
PagerDuty is the most established on-call platform, with more than 750 integrations (PagerDuty pricing). Professional costs $21 per user per month on annual billing, with AIOps, Live Call Routing and status pages as add-ons and ServiceNow integration reserved for the PD Reliability Platform, priced from $2,800 to $48,000 a year.
3. incident.io
incident.io runs incidents in Slack from declaration to postmortem. Team costs $15 per user per month on annual billing and Pro costs $25, with on-call added at $10 or $20 per user (incident.io pricing). It suits engineering teams that already live in Slack.
4. Jira Service Management
JSM includes alerts and on-call on every plan, with Standard listed at $21.50 per agent per month and heartbeat monitoring in Premium (Atlassian pricing). It fits teams that already run their service desk in Jira.
5. Grafana Cloud IRM
Grafana Cloud IRM bundles on-call with Grafana observability. Pro is a $19 monthly platform fee covering 3 users, then from $20 per active IRM user (Grafana pricing). It makes sense when alerts already start in Grafana.
6. Rootly
Rootly runs incidents in Slack, Microsoft Teams or Google Chat and has strong retrospective features. Incident Response and On-Call are separate products at $20 per user per month each (Rootly pricing).
See your Splunk alerts routed, correlated and escalated in AlertOps. Book a demo
Keeping Splunk while replacing Splunk On-Call
Leaving Splunk On-Call does not mean leaving Splunk. Most teams keep Splunk for search, logs and observability and change only the layer that pages people. Splunk alerts that fire today into Splunk On-Call can be pointed at the AlertOps Splunk integration instead, so the detection logic your engineers built stays exactly where it is. AlertOps then correlates related alerts, applies routing by service and owner and escalates across phone, SMS, email and app.
That split also keeps the cost conversation simple. Your Splunk contract stays as it is, and the on-call line moves to a platform priced per user. AlertOps Standard costs $8 per user per month on annual billing for up to 10 users, Premium $18 and Enterprise $28, so a 25-person rotation on Enterprise lists at $8,400 a year with OpsIQ, two-way ITSM integration and migration included (AlertOps pricing).
How Splunk On-Call concepts map to AlertOps
| Splunk On-Call | AlertOps |
|---|---|
| Routing keys | Inbound integrations, topics and escalation policies |
| Alert rules that rewrite payloads | Field mapping, custom fields and Workflows |
| Teams and rotations | Groups, Rotating Schedules and Override Shifts |
| Escalation policies | Escalation Policies for role order, Response Plays for whole-group alerts |
| Incident timeline | Alert history plus an Agent Chronicle postmortem |

How the switch works
Moving off Splunk On-Call to AlertOps is an assisted engagement run by the Solution Engineering team, and migration support comes with AlertOps Enterprise. The team copies your schedules, escalation rules and integrations first. Real alerts then flow to both platforms while Splunk On-Call stays live, so you can confirm every page reaches the right person in the right order. Because no vendor deadline is forcing the timing, that parallel run can last as long as it takes. Once routing matches, you switch over and retire Splunk On-Call on your own date.
Two habits make the move smoother. Rebuild routing around services and owners rather than copying every old key one for one, since migrations are the best chance to remove rules nobody uses. And invite one responder from each team into the parallel run, because the people who carry the pager will spot a wrong route faster than any test plan.
Plan the cutover for a quiet week rather than a release window or quarter end. Keep Splunk On-Call active, read-only, for a few days after the switch, so responders can check old incident history while new pages flow through AlertOps.
Compare features in detail in AlertOps vs Splunk On-Call, or book a demo.
FAQ
Is Splunk On-Call (VictorOps) being discontinued?
Splunk has published no end-of-life date, and the product still runs. Teams that switch do so because of product direction, not a shutdown.
How much does Splunk On-Call cost?
Splunk lists Splunk On-Call from $5 per user per month on annual billing for up to 10 seats. Larger teams need a quote.
What is the best Splunk On-Call alternative?
AlertOps suits IT operations, NOC and MSP teams and ServiceNow or Jira shops. PagerDuty suits large engineering organizations, incident.io and Rootly suit Slack-first teams, JSM suits Atlassian shops and Grafana Cloud IRM suits Grafana users.
Can AlertOps receive alerts from Splunk?
Yes. AlertOps has a pre-built Splunk integration, so the alerts you send to Splunk On-Call today can route, correlate and escalate in AlertOps.
Will I lose my Splunk On-Call schedules when I switch?
No. The AlertOps Solution Engineering team rebuilds your schedules, escalation rules and integrations, then tests them side by side before you cut over.
Do I need to leave Splunk to replace Splunk On-Call?
No. Most teams keep Splunk for search, logs and observability and point Splunk alerts at their new on-call platform instead.
Which Splunk On-Call alternative includes on-call without an add-on?
AlertOps, Jira Service Management and Grafana Cloud IRM include on-call in their plans. incident.io and Rootly sell on-call separately.
How long does a Splunk On-Call migration take?
There is no deadline forcing the timing, so the parallel run can last as long as your team needs. The Solution Engineering team scopes the timeline on the first call.
Sources
- Splunk: Splunk On-Call pricing FAQ
- PagerDuty: Plans and pricing
- incident.io: Pricing
- Atlassian: Service Collection pricing
- Grafana: Pricing
- Rootly: Pricing