| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Incident management and on-call | IT operations and endpoint | 2% | 12 of 65 | 33% | 15 | criticized challenger | ▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Incidents | 0% | 2% | ▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 50 → 12 of 65 |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 0 | 0 | 1 | 1 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 0 | 0 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.20 | 0 | 0 | 1 | 2 | 3 |
| Mistral Small | 1 | 0 | 2 | 0 | 3 |
| DeepSeek V4 Flash | 0 | 1 | 0 | 2 | 3 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 1 | 0 | 1 |
| Kimi K2 | 0 | 0 | 0 | 0 | 0 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 0 | 1 | 0 | 0 | 1 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 2 | 1 | 0 | 3 |
Verbatim evidence the judge attached to positive labels.
“Starts at $5 per user per month, making it a very budget-friendly option for structured on-call management.” Mistral Small · Incidents · budget prompt · first choice
“"Formerly VictorOps, Splunk On-Call offers a powerful rules engine for alert deduplication and routing."” Muse Glimmer 30B · Incidents · comparative prompt · alternative
“Enterprise compliance (FedRAMP, HIPAA) | If you need heavy regulatory certifications” DeepSeek V4 Flash · Incidents · scale prompt · alternative
“Best for DevOps-centric alerting teams already using Splunk. Strong alert routing” Muse Glimmer 30B · Incidents · scale prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“don't pick a tool that is likely to become a legacy product” DeepSeek V4 Flash · Incidents · negative prompt · hard negative
“Splunk-centric; less compelling if you don't use the Splunk stack; the product has been somewhat stagnant since the acquisition” DeepSeek V4 Flash · Incidents · comparative prompt · soft negative
“be cautious if you're not already committed to that observability ecosystem” GPT-5.4 mini · Incidents · negative prompt · soft negative
“Mixed reliability on notifications/escalations in high-volume scenarios” Grok 4.20 · Incidents · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 42 of the 48 answers that named Splunk On-Call and are not a share of its labels.
160 of the 160 domain citations in answers naming Splunk On-Call came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Splunk On-Call's own pages state, read September 28, 2026: community.splunk.com/t5/Splunk-On-Call/bd-p/it-victor-ops, help.splunk.com/en/splunk-observability-cloud/splunk-on-call/alerts, help.splunk.com/en/splunk-observability-cloud/splunk-on-call/incidents, help.splunk.com/en/splunk-observability-cloud/splunk-on-call/create-and-manage-on-call-schedules, help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/alerts. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Splunk On-Call's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Splunk On-Call, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Splunk On-Call by email, built from the raw record of the edition. It shows: