About pingfatigue.com
An independent vendor-neutral reference on alert fatigue for DevOps, SRE, and SecOps teams. Calculator, Alert Fatigue Index, tool comparison, and 25+ primary-source citations. No vendor relationships, no sponsored content, no quote forms.
Why this site exists
Alert fatigue is one of the best-documented operational pathologies in modern engineering, with primary-source data across SRE (Google SRE Book, DORA), incident management (incident.io 2024 State of On-Call, Catchpoint 2024 SRE Report, PagerDuty 2023 Global Incident Management), knowledge-worker interruption research (Gloria Mark UC Irvine, Microsoft Work Trend Index, Slack Workforce Index), and 30 years of peer-reviewed healthcare alarm-fatigue literature. None of that data was aggregated in one vendor-neutral place. Vendor blogs covered fragments, framed by their own product roadmaps. Practitioner essays covered the philosophy but skipped the math. The Alert Fatigue Index on the home page is the first single benchmark table to compress healthy, median, and noisy thresholds across pages per engineer per week, false-positive ratio, MTTA, sleep disruption, attrition intent, correlation adoption, and cost per engineer per year, sourced from primary documents and re-verified monthly.
The calculator is the other gap. Vendor calculators model marginal product savings; they cannot model the cost of being on-call before you adopt their product. The pingfatigue calculator combines direct alert-handling time (page count multiplied by MTTA plus the Gloria Mark 23-minute refocus penalty), after-hours premium for night and weekend pages, and the SHRM 1 to 1.5x annual salary replacement formula when attrition intent converts to a senior SRE leaving. The math is shown step by step on /on-call-cost so anyone can re-run the numbers against their own team composition and salary anchors.
The healthcare cross-reference is deliberate. ICU alarm fatigue has 30 years of peer-reviewed research, regulatory mandates (Joint Commission NPSG.06.01.01), and documented patient-harm cases. DevOps shares the same cognitive mechanism with one tenth the research depth. /healthcare-parallel applies what worked in healthcare to alerting practice.
Who builds this
pingfatigue.com is built and maintained by Oliver Wakefield-Smith at Digital Signet, an independent reference-content studio. The site is part of a portfolio of cost-reference and operational-reference properties focused on engineering economics and infrastructure decision support.
Sister sites in the engineering operations cluster:
Broader incident taxonomy across breach, outage, ransomware.
Revenue impact of the downtime that noisy alerts could have prevented.
PagerDuty tier pricing breakdown.
Observability stack economics: Datadog, Grafana, New Relic.
Quantifying the other invisible engineering tax.
Platform team cost context.
Editorial position
This is a reference site, not a reseller, not a managed-services lead-generation funnel, not a paid placement marketplace. Vendor rows on /tools are ordered by category fit and verified feature parity; affiliate links are explicitly labelled [A] and do not affect the underlying scoring methodology. Where a vendor genuinely fits more than one category (PagerDuty for breadth, incident.io for Slack-native UX, Rootly for runbook-centric workflow) the page says so explicitly.
Where a number is contested between sources (the median page count per engineer, the after-hours premium multiplier, the senior SRE replacement cost range), the source variance is shown explicitly with the assumption stated. Where a vendor publishes opaque enterprise pricing (Splunk On-Call custom MSAs, BigPanda quote-only enterprise tiers) the page flags "quote-only" rather than invent a point estimate.
What this site covers
Move the sliders to calculate cost per engineer per year. Plus the 7-metric Alert Fatigue Index aggregating incident.io, Catchpoint, DORA, Google SRE, and PagerDuty primary sources.
Plain-language definition, 4-type taxonomy across DevOps, SRE, SOC, and healthcare, and the 7 root causes that produce alert fatigue in operational systems.
The true cost per engineer per year. Direct alert-handling time, context-switching penalty, after-hours premium, and SHRM-formula replacement cost when a senior SRE quits.
How alert fatigue degrades MTTA and MTTR. DORA 2024 tier benchmarks, error-budget burn math, and interventions ranked by observed lift.
14-step playbook to cut false-positive rate from the 70 percent industry median toward below 20 percent. Check each step to track estimated noise reduction.
Why SLO-based burn-rate alerting eliminates symptom-cause noise. 5-step migration plan using the Google SRE Workbook multi-window multi-burn-rate formula.
How alert correlation, grouping, and deduplication reduce ticket count 60 to 90 percent. Neutral comparison of PagerDuty, Opsgenie, BigPanda, Moogsoft, incident.io, FireHydrant, Rootly.
Runbook template, on-call rotation patterns (follow-the-sun, primary and secondary, week-on), PagerDuty schedule examples, post-mortem template. Free to copy.
Six on-call platforms scored on alert-fatigue-reduction criteria with verified pricing: PagerDuty, incident.io, Opsgenie, FireHydrant, Rootly, Splunk On-Call.
The knowledge-worker side of the same cognitive mechanism. Slack, email, and Microsoft Teams interruption cost using Gloria Mark 23-minute refocus penalty.
30 years of peer-reviewed ICU alarm fatigue research applied to DevOps alerting. Joint Commission NPSG.06.01.01, ECRI top hazards, Cvach 2012 review.
25+ primary sources across SRE (Google SRE Book, DORA), incident management (incident.io, Catchpoint, PagerDuty), SOC (Ponemon, Mandiant), and healthcare alarm fatigue.
Documented incidents where alert overload contributed to missed detections, extended outages, and preventable harm: Target 2013, Therac-25, ICU sentinel events, Cloudflare 2019.
Editorial principles
Every benchmark, percentage, and cost band on this site traces back to a primary source: a peer-reviewed paper, a published industry survey, a vendor's own pricing or documentation page, or an aggregated public dataset. Where a number is derived (cost models, ROI estimates) the formula is shown alongside the result.
There are no sponsored slots in the tool comparison, no premium positioning, no pay-to-rank. Vendor rows on /tools are ordered by category fit and verified feature parity, not by any commercial relationship.
Outbound links to alerting vendors (PagerDuty, incident.io, Opsgenie, FireHydrant, Rootly, Splunk On-Call) and to primary sources are plain unaffiliated URLs unless explicitly labelled [A] in the tool comparison. This site is a reference, not a lead-generation funnel.
Pricing and benchmark figures are re-verified against each primary source on the first business week of each month. The last verified label currently reads May 2026.
The verification date is held in one constant (LAST_VERIFIED_DATE) imported by every page. Footer text, schema dateModified, and visible headings all read from that single source so cosmetic refreshes are not possible.
The /tools page scores six vendors on alert-fatigue-reduction criteria: correlation depth, SLO support, routing, runbooks, schedule design, and verified price. Scores are derived from the published methodology and reapplied each verification cycle.
Methodology in brief
Alert volume and false-positive benchmarks come from the incident.io 2024 State of On-Call survey, Catchpoint 2024 SRE Report, and PagerDuty 2023 Global Incident Management Study. SRE doctrine and SLO-based alerting come from the Google SRE Book Chapter 6 and the SRE Workbook Chapter 5. MTTR tier definitions come from the DORA 2024 Accelerate State of DevOps Report. Knowledge-worker interruption research comes from Gloria Mark (UC Irvine, 2004 and 2023), Microsoft Work Trend Index, Slack Workforce Index 2023, and RescueTime productivity data. Healthcare alarm fatigue research draws on the Joint Commission, ECRI Institute, AHRQ PSNet, and the Cvach 2012 integrative review.
For full source provenance, calculation framework, in-scope and out-of-scope coverage, refresh cadence, limitations, and the corrections process, see the methodology page.
Contact and corrections
Spotted a stale benchmark, a missing primary source, or a vendor change we have not caught yet? Email [email protected] with the page URL and the source you would like cited. Substantive corrections are typically actioned within five business days.
Disclosures
- >Affiliate links on /tools are clearly labelled [A]. The site receives a commission on qualified referrals from those labelled rows. Affiliate status does not affect tool scoring or category fit; scores are derived from the published methodology and reapplied each verification cycle.
- >No paid placements, no sponsored content, no email-gated downloads, no quote forms, no sales redirects.
- >Not affiliated with PagerDuty, incident.io, Opsgenie, Atlassian, FireHydrant, Rootly, Splunk, Datadog, BigPanda, Moogsoft, or any other listed vendor.
- >Calculator outputs and cost estimates are anchors, not forecasts; production economics depend on team composition, regional salary variance, vendor-negotiated contracts, and incident severity distribution not covered here.
Updated May 2026