Reliability Economics

Archives
Log in
Subscribe
September 1, 2026

AI SRE agents meet production—and production wins

The Ratio #16

Issue 16September 1, 2026

The Ratio

A weekly newsletter on reliability economics

 

The Number

8.88 median ratio

Mid-size organizations (10,000–49,999 employees) carry the highest median reliability ratio of any size band in the benchmark — higher than enterprises with 100,000+ employees.

The 10,000–49,999 employee band (N=16) has the highest median reliability ratio in the benchmark at 8.88. That means for every dollar spent on prevention, $8.88 goes to cleaning up failures. Organizations with 100,000+ employees (N=24) sit at 5.63. The smallest tracked band, 1,000–9,999 employees (N=15), has a median of 4.48. Mid-size organizations spend less on prevention relative to their failure costs than any other group, including the largest enterprises.

Neutral

Mid-size companies are supposed to be the sweet spot. Startup speed plus enterprise money. The data says otherwise. They carry more failure cost per prevention dollar than anyone else in the benchmark. This is the reliability equivalent of a mid-size manufacturer that outgrew its single quality inspector three shifts ago but hasn't hired a second one, every defect now reaches the customer. Complexity scaled. The team didn't. The budget definitely didn't.

Mid-size organizations (10,000–49,999 employees) are more reliability-imbalanced than enterprises twice their size.
Did this land?
More like thisSwitch it up
 

This Week in Reliability

AI SRE Agents Hit Reality

The AI SRE agent wave that dominated vendor pitches is now colliding with actual deployment constraints—security boundaries, trust ladders, and the gap between 'automate incidents' and 'automate investigations.' Teams are learning the hard way that agentic automation without context, guardrails, and human verification creates new categories of operational risk.

 

Deep Reads

Suggest First, Act Second: GreytHR's Senior Director of Engineering on Climbing the Trust Ladder

StackGen  ·  Primary evidence—deployment methodology

GreytHR's engineering leadership describes their phased approach to AI agent adoption: starting with suggestions and analysis before graduating to autonomous actions. The trust ladder model requires agents to prove value at each level before gaining permission to act.

Neutral

This is the reliability economics reality check the AI SRE space needed. Autonomous agents that skip the suggestion phase don't just risk bad changes—they eliminate the organizational learning loop that lets teams distinguish prevention from expensive automation theater. The trust ladder isn't friction; it's how you avoid spending six figures on an agent that optimizes the wrong metric.

Trust isn't binary—it's a ladder agents climb one rung at a time.

Troubleshooting, Metrics, and Alerting in the AI Era: What's Changed for SREs

StackGen  ·  Core workflow impact

The article examines how AI changes the SRE workflow across troubleshooting, metrics interpretation, and alert triage. It argues that AI excels at pattern matching in metrics and logs but still requires human judgment for context-dependent decisions and novel failure modes.

Firefighting

The promise of AI SRE was 'automate the toil,' but the reality is 'automate the easy 60% and surface harder questions faster.' That's still valuable—it moves MTTR left—but it doesn't change your prevention budget, and it definitely doesn't eliminate the 3 AM pages from the novel failures your metrics didn't anticipate. Budget accordingly: you're buying investigation acceleration, not incident elimination.

AI speeds up known patterns; you still own the novel failures.

PagerDuty SRE Agent vs. Resolve AI: Which Do You Need?

Resolve AI  ·  Vendor positioning split

Resolve AI distinguishes between PagerDuty's SRE Agent (which automates incident workflow and escalation) and its own investigation-focused agent that analyzes root cause and suggests fixes.

Firefighting

The agent market is fragmenting into 'run the process' vs. 'run the investigation,' and most orgs will need both—which means two vendors, two integration surfaces, and twice the context-sharing risk.

Process automation ≠ investigation automation; budget for both or neither works.

State of SRE Report: 2026 Edition - Full version

Dynatrace  ·  Survey evidence—expectations gap

Dynatrace's 2026 SRE survey data shows AI technologies in ITOps are meeting expectations for reliability and developer productivity but falling short on cost reduction and faster incident detection/resolution.

Neutral

When your AI investment delivers on productivity but misses on MTTR and cost, you've automated the easy stuff and left the expensive problems untouched—classic prevention-vs-reaction mismatch.

AI met dev velocity goals, missed the incident budget.

RunWhen Home

RunWhen  ·  Market maturity signal

RunWhen is positioning itself to help experienced engineers transition into 'AI SRE consultants' and paid community contributors, signaling a new professional category around agentic SRE tooling.

Neutral

When a vendor starts hiring for 'AI SRE consultants,' that's a market signal that the tooling isn't self-service yet—enterprises need human translators to make agents work in production.

New job title = automation that still needs humans.

Omnipresent availability risks in cloud software

Lorin Hochstein (Surfing Complexity)  ·  Systemic risk context gap

Lorin Hochstein catalogs recurring availability risk patterns in cloud SaaS writeups: database saturation, cascading retries, configuration drift, and dependency failures that appear across vendors and platforms.

Prevention

AI agents can't prevent risks that show up everywhere if the knowledge graph doesn't encode 'everywhere'—and most don't. These omnipresent failure modes are the test case for whether your agent architecture learns from the industry or just your last three incidents.

Agents trained on your incidents miss the industry's shared failure modes.

Reclaim SRE- Let's put Engineering back into Site Reliability Engineering

ReclaimSRE  ·  Practitioner counter-narrative

ReclaimSRE is a community initiative arguing that SRE has drifted from its engineering roots and calling for a return to first-principles reliability work rather than tool-driven incident response.

Prevention

This is the backlash: after two years of 'AI will do SRE for you,' practitioners are saying 'we never stopped needing actual engineering.' Agents are great—until they optimize a system you don't understand.

Automation without engineering understanding just moves the failure faster.
Did these land?
More like thisSwitch it up
 

The Crowd Favorite

  1. Creep — Radiohead — Every manual change that bypasses IaC is configuration drift in silence. The gap between declared and actual state is the incident.
  2. Sultans of Swing — Dire Straits — Median-load provisioning is zero-margin provisioning. You sized for an empty bar and the crowd arrives at peak.
  3. Black Hole Sun — Soundgarden — A dependency without a circuit breaker is an event horizon. Every downstream caller joins the failure and nothing returns.
  4. Enjoy the Silence — Depeche Mode — Silence from your monitoring pipeline is not health. It means the monitor failed. Instrument your instrumentation.
  5. Get Lucky (feat. Pharrell Williams and Nile Rodgers) — Daft Punk, Pharrell Williams, Nile Rodgers — Near-misses not filed as near-misses vanish from your data. The next identical root cause lands as a surprise in the postmortem.

Prevention

Reduces future firefighting
The playlist — keep or kill?
Keep the crownDethrone it
 

The Challenger — Comment of the Week

"We track MTTD. We track MTTR. Nobody has ever asked me what it would have cost to not have the incident. The SLO grades my failures. It doesn't fund preventing them."

— r/sre, thread: "What's actually missing from your postmortem template?"

This person named the gap nobody wants to name. Failure cost shows up in postmortems: engineer-hours, customer churn, lost revenue. All visible. Prevention cost sits in roadmaps that engineering leads pitch and finance teams quietly kill, because the incident that didn't happen has no receipt.

At 8.88 median ratio, that asymmetry has a number now.

The fix is not a richer postmortem template. It's pricing near-misses before they become line items.

Neutral

The cost nobody budgets for
Should this replace the favorite?
Promote itNot ready

The Ratio is a weekly newsletter by Florian Hoeppner.
Early edition, you are one of the first.

Forwarded this? Get The Ratio in your inbox every week.

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

How this newsletter gets better: Every link is tracked and every vote is counted. Sections that get a down vote get replaced. Topics that get an up vote stay. No personal data is stored — just click and vote counts per section. Your feedback shapes the next edition.

Don't miss what's next. Subscribe to Reliability Economics:
← Newer AI SRE isn't replacing toil—it's exposing maturity gaps Older → The AI agent ops tax nobody budgeted for
Powered by Buttondown, the easiest way to start and grow your newsletter.