Uptimeify vs. Splunk On-Call
Splunk On-Call, formerly VictorOps, is an established tool for on-call and alerting, with Slack buttons and apps for iOS and Android. Splunk documents no EU region for On-Call, there is no status page of its own, and roles inside the incident are missing. Uptimeify is a white-label monitoring platform with built-in incident management for your team: hosted in the EU, no US subprocessors, with a status page on the same platform.
For agencies and MSPs
- Hosted in the EU, no US subprocessors
- Your own monitoring and status page on the same platform
- Incident roles: commander, tech lead, communications, responder
- Postmortems with a cause catalog and action items with an owner
- Terraform provider for teams, schedules, escalation and routing
For DevOps teams in the Splunk world
- No EU region documented, processing in the US as well
- No monitoring of its own, Splunk products through integrations
- No status page of its own, only through third parties
- No roles such as incident commander inside the incident
- Terraform provider without a new release since May 2021
As of November 2026. Details on Splunk On-Call are based on publicly available information and may change. Prices in the source's original currency, not converted. If something is wrong, we are glad to hear about it. On-call scheduling, acknowledgement and the incident timeline are currently in beta on Uptimeify.
In short
Splunk On-Call is built for DevOps teams that want to get alerts from many sources to the right person. If you already work with Splunk Observability Cloud, you connect Synthetic and Infrastructure Monitoring through integrations, and in Slack you acknowledge, reroute, resolve or snooze alerts with a button.
For teams serving clients in the EU, gaps remain. Splunk documents no EU region for On-Call, and according to its security FAQ, personal data is processed in the US as well. There is no status page of its own, so status pages run only through third parties such as Statuspage. The official Terraform provider has not had a new release since May 2021.
Uptimeify starts right there: monitoring, on-call, escalation and status pages on one platform, with no US subprocessors for your incident data. Incident roles, postmortems with a cause catalog and a current Terraform provider are part of it.
Feature by feature
As of November 2026. Details on Splunk On-Call are based on publicly available information and may change. On-call scheduling, acknowledgement and the incident timeline are currently in beta on Uptimeify. All trademarks belong to their respective owners.
Where Uptimeify leads
Three things the big players solve differently, and that we built for your team.
Your incident data stays with European providers. Splunk documents no EU region for On-Call, and its security FAQ states that personal data is processed outside the EEA and the UK, including in the US. On Uptimeify, only European providers process your incident data: hosting with Hetzner, OVH, netcup, UpCloud and IONOS, SMS and calls through seven.io and LOX24 in Germany. The optional app push runs encrypted through Apple and Google, who do not read the content.
A status page without a third party. Splunk On-Call has no status page of its own, so you need Statuspage, StatusCast or StatusHub for that. On Uptimeify, status page rules set your client's status page to warning or outage automatically as soon as a team's incident reaches the severity you set, and back to green once it is resolved. You write the public text yourself.
Clear roles and a clean follow-up. Splunk On-Call knows additional responders but no roles such as incident commander, and its post-incident review has no dedicated field for the root cause. Uptimeify assigns commander, tech lead, communications and responder and runs postmortems with a cause from a shared catalog and action items with an owner and a due date.
Where Splunk On-Call wins
No tool wins everywhere. Three points where Splunk On-Call is the better choice.
Working right in Slack and Teams. With the Slack integration, you acknowledge, reroute, resolve or snooze alerts with a button, and there is a dedicated app for Microsoft Teams. Uptimeify sends incidents to Slack and Microsoft Teams, but you can
The Splunk ecosystem. If your team works with Splunk Observability Cloud, Synthetic Monitoring, Infrastructure Monitoring and On-Call come together at one vendor through ready-made integrations.
More channels for the alert. Splunk On-Call alerts by push, SMS, call, email and also WhatsApp. If your team wants WhatsApp as a channel, it is ready there.
Frequently asked questions
VictorOps is now called Splunk On-Call, and its docs sit in the Splunk Observability Cloud section. We found no official announcement of an end of sale or support, and the product page and docs are maintained. The official Terraform provider still carries the name victorops, and its latest release dates from 18.05.2021 (as of 09.11.2026).
Splunk publishes one figure: from $5 per user and month with annual billing, for up to ten seats. Beyond that, there is only a quote. The docs mention tiers such as Starter, Essentials, Full Stack and Enterprise without a comparison, and according to the docs the Rules Engine for condition-based routing is a Full Stack feature. As of 09.11.2026, according to Splunk's pricing page.
Yes, by hand. There is no automatic import at the moment. You create teams, schedules, overrides and escalation tiers in the dashboard, or with Terraform if you manage them with the victorops provider today. In your monitoring tools, you paste the webhook URL of the new alert source, and Zabbix, Datadog, Grafana, Prometheus, Sentry and Beszel come with ready-made presets. On-call scheduling is currently in beta.
Only European companies. Servers and check nodes run with Hetzner, OVH, netcup, UpCloud and IONOS, spread across several locations in the EU. SMS and calls are delivered by seven.io with LOX24 as failover, both based in Germany, and email goes through Lettermint in the Netherlands. To reach the lock screen, the optional app push runs through Apple and Google, encrypted, so neither reads the alert text. The subprocessor list is public, and the data processing agreement is ready to sign.
Yes, on the same platform. The status page runs under your brand and your domain, and status page rules set it to warning or outage straight from the incident and back again. Incident management itself stays internal for your team, and client logins have no access to it.
Yes. The alert call starts with "Uptimeify Alarm", reads the message three times and waits for a key. Pressing 4 acknowledges the incident and stops paging for everyone else. If you do not pick up, a second call follows after one minute, and then your escalation chain continues. Acknowledgement and the incident timeline are currently in beta.
For the technical evaluator
From Splunk On-Call to incident management made in the EU
Create your first team, connect your alert sources and link your status page. Your team knows who is on call, and your client sees the status before they call.