The Ratio

Our weekly newsletter on reliability economics.

I run a benchmark that nobody asked for. 121 enterprise teams have taken it anyway. Every Tuesday I send you the one number that surprised me and the seven links that explain why it matters to me.

The newsletter is how I think out loud about what the data says.

No sponsors. No AI slop. Hit reply any time — I read everything.
Prefer RSS? reliabilityeconomics.com/blog/feed/the-ratio.xml

Issue №19September 22, 2026

The Ratio

A weekly newsletter on reliability economics


The Number

6 of 9

Six of the nine organizations classified as near-optimal reliability investment are in Financial Services — a sector that represents just 32% of the benchmark.

Six of the nine near-optimal organizations in this benchmark are in Financial Services. That sector is 32% of respondents.

The Ratio

Regulation forced Financial Services firms to price failure to the dollar, while everyone else budgets reliability by habit and guesses wrong in both directions, overspending or underspending with no logic behind either. Same as insurance underwriting: actuaries who price from loss history beat the ones pricing from gut, every time.

Financial Services is 32% of this benchmark but holds 67% of the organizations getting reliability investment right.



The Crowd Favorite

  1. Won't Get Fooled Again - Original Album Version — The Who ↗ — Dependency failures cascade the same way every time. Map them once and the next cascade is a drill, not a disaster.
  2. Life on Mars? - 2015 Remaster — David Bowie ↗ — Distributed tracing catches the first isolated service failure before it snowballs into a multi-system outage.
  3. Paranoid - 2012 - Remaster — Black Sabbath ↗ — Alert fatigue is a capacity failure. Every non-actionable page burns the engineer's response reserve for the page that actually matters.
  4. Mr. Brightside — The Killers ↗ — Synthetic monitoring runs the user's scenario before the user does. You own the failure before it becomes a support ticket.
  5. Clocks — Coldplay ↗ — Clock drift corrupts event ordering in distributed systems. NTP synchronization is the cheapest reliability target you're not enforcing.
Prevention

Reduces future firefighting


The Challenger — Vendor Landscape

On-call intelligence platforms split cleanly on the U-Curve.

Prevention side: incident.io surfaces recurring failure patterns from past incidents to prevent repetition. Rootly automates retrospective workflows so findings reach the team that can actually fix things.

Reaction side: PagerDuty dominates alert routing and escalation. Fastest path from signal to engineer. Not the path that reduces signal count.

The gap: None of these platforms reports your prevention-to-firefighting ratio. Measuring response time is solved. Measuring whether you're preventing incidents is still manual.

The Ratio

Reaction tooling solved. Prevention measurement still manual.


The Ratio is a weekly newsletter by Florian Hoeppner.

Take the assessment → reliabilityeconomics.com/benchmark
Reply to this email with your take.

The Ratio

Our weekly newsletter on reliability economics.

I run a benchmark that nobody asked for. 121 enterprise teams have taken it anyway. Every Tuesday I send you the one number that surprised me and the seven links that explain why it matters to me.

No sponsors. No AI slop. Hit reply any time — I read everything.
Prefer RSS? reliabilityeconomics.com/blog/feed/the-ratio.xml