<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Operate Blog</title>
<link>https://operatex.dev/blog</link>
<atom:link href="https://operatex.dev/rss.xml" rel="self" type="application/rss+xml" />
<description>Field notes on AI SRE, root-cause analysis, and running self-hosted AI in production.</description>
<language>en-us</language>
<lastBuildDate>Sun, 19 Jul 2026 18:53:10 GMT</lastBuildDate>
<item>
<title>Stuck state: the failure mode behind both July 2 postmortems</title>
<link>https://operatex.dev/blog/stuck-state-july-2-postmortem-analysis</link>
<guid isPermaLink="true">https://operatex.dev/blog/stuck-state-july-2-postmortem-analysis</guid>
<pubDate>Sun, 19 Jul 2026 06:49:46 GMT</pubDate>
<category>SRE &amp; Platform Engineering</category>
<description>Railway and CircleCI both published July 2, 2026 postmortems with the same hidden failure mode: state captured during instability that never corrected itself.</description>
</item>
<item>
<title>Reduce MTTR by attacking the 80 percent: diagnosis, not repair</title>
<link>https://operatex.dev/blog/reduce-mttr-diagnosis-first-playbook</link>
<guid isPermaLink="true">https://operatex.dev/blog/reduce-mttr-diagnosis-first-playbook</guid>
<pubDate>Sat, 18 Jul 2026 17:11:06 GMT</pubDate>
<category>SRE &amp; Engineering Efficiency</category>
<description>About 80 percent of MTTR is spent finding the cause, not fixing it. A diagnosis-first playbook for reducing MTTR across code, database, infra, logs, and CI.</description>
</item>
<item>
<title>Beating On-Call Alert Fatigue: Triage by Evidence, Not by Threshold-Tuning</title>
<link>https://operatex.dev/blog/on-call-alert-fatigue-solutions-triage-evidence</link>
<guid isPermaLink="true">https://operatex.dev/blog/on-call-alert-fatigue-solutions-triage-evidence</guid>
<pubDate>Thu, 16 Jul 2026 19:41:11 GMT</pubDate>
<category>SRE &amp; Incident Management</category>
<description>On-call alert fatigue is a triage problem, not a threshold problem. A practical guide to cutting page volume by investigating alerts to root cause across the whole stack.</description>
</item>
<item>
<title>Replay-Verified Is Not Production-Safe: Where the Agentic Database&apos;s Autonomy Ladder Breaks</title>
<link>https://operatex.dev/blog/agentic-database-autonomy-verification-risks</link>
<guid isPermaLink="true">https://operatex.dev/blog/agentic-database-autonomy-verification-risks</guid>
<pubDate>Thu, 16 Jul 2026 00:15:24 GMT</pubDate>
<category>Engineering Strategy</category>
<description>A response to &apos;Agentic databases aren&apos;t agentic&apos;: replaying traffic on a fork proves answer-equivalence, not production safety. Why the reviewable diff, not the autonomy boundary, is the unit of trust.</description>
</item>
<item>
<title>Automating Root Cause Analysis Without Giving AI Write Access to Production</title>
<link>https://operatex.dev/blog/automated-root-cause-analysis-safety-guide</link>
<guid isPermaLink="true">https://operatex.dev/blog/automated-root-cause-analysis-safety-guide</guid>
<pubDate>Wed, 15 Jul 2026 08:07:43 GMT</pubDate>
<category>Engineering Leadership</category>
<description>A practical, vendor-neutral guide to automated root cause analysis across the whole stack, and why the safe default is patch-file-only with no write access to production.</description>
</item>
<item>
<title>Knight Capital&apos;s 97 Unread Emails: A $460M Lesson for the AI-Agent Era</title>
<link>https://operatex.dev/blog/knight-capital-97-unread-emails-ai-agent-era</link>
<guid isPermaLink="true">https://operatex.dev/blog/knight-capital-97-unread-emails-ai-agent-era</guid>
<pubDate>Wed, 15 Jul 2026 02:47:38 GMT</pubDate>
<category>Postmortems</category>
<description>Knight Capital lost $460M in 45 minutes. The SEC order reads like a checklist for teams deploying AI agents against production: unreviewed changes, unread signals, unverified fixes.</description>
</item>
<item>
<title>Idle in Transaction in Postgres: What It Means, How to Find It, and Why Autovacuum Can&apos;t Save You</title>
<link>https://operatex.dev/blog/idle-in-transaction-postgres</link>
<guid isPermaLink="true">https://operatex.dev/blog/idle-in-transaction-postgres</guid>
<pubDate>Wed, 15 Jul 2026 02:28:00 GMT</pubDate>
<category>Postgres</category>
<description>What idle in transaction means in Postgres, why it silently blocks autovacuum while dashboards stay green, the 60-second diagnosis SQL, and the one-line timeout that prevents it.</description>
</item>
<item>
<title>The flaky test runbook: detect, quarantine, diagnose, verify</title>
<link>https://operatex.dev/blog/flaky-test-incident-runbook</link>
<guid isPermaLink="true">https://operatex.dev/blog/flaky-test-incident-runbook</guid>
<pubDate>Tue, 14 Jul 2026 19:04:58 GMT</pubDate>
<category>Engineering Operations</category>
<description>A practical runbook that treats flaky tests as incidents: detection thresholds, a five-cause taxonomy, quarantine exit criteria, and the math of verifying a fix.</description>
</item>
<item>
<title>The 21% Problem: Why Second Opinions are Critical for Root Cause Analysis</title>
<link>https://operatex.dev/blog/root-cause-analysis-second-opinion-21-percent-problem</link>
<guid isPermaLink="true">https://operatex.dev/blog/root-cause-analysis-second-opinion-21-percent-problem</guid>
<pubDate>Tue, 14 Jul 2026 00:21:50 GMT</pubDate>
<category>Engineering Leadership</category>
<description>When Mayo Clinic re-examined referred diagnoses, 21% changed completely. Root cause analysis has the same failure mode and none of the safeguards.</description>
</item>
<item>
<title>Every Component Is Green and the System Is Down</title>
<link>https://operatex.dev/blog/dashboards-green-but-system-down-failure-class</link>
<guid isPermaLink="true">https://operatex.dev/blog/dashboards-green-but-system-down-failure-class</guid>
<pubDate>Mon, 13 Jul 2026 04:52:38 GMT</pubDate>
<category>Engineering &amp; SRE</category>
<description>Pod healthy, service healthy, endpoint healthy - and the request times out. Four real incidents where every dashboard was green, and a cross-layer protocol for the failure class between components.</description>
</item>
<item>
<title>When Recovery Doesn’t Recover: Railway, CircleCI, and Stuck State</title>
<link>https://operatex.dev/blog/stuck-state-postmortem-railway-circleci-outage</link>
<guid isPermaLink="true">https://operatex.dev/blog/stuck-state-postmortem-railway-circleci-outage</guid>
<pubDate>Sun, 12 Jul 2026 14:50:55 GMT</pubDate>
<category>Engineering &amp; SRE</category>
<description>Railway and CircleCI both went down on July 2, 2026. The interesting failures came after recovery: connections and workflows that silently kept bad state.</description>
</item>
<item>
<title>Recovery Is Not Convergence: Anatomy of an Outage That Outlived Its Root Cause</title>
<link>https://operatex.dev/blog/railway-outage-stale-connections-network-recovery</link>
<guid isPermaLink="true">https://operatex.dev/blog/railway-outage-stale-connections-network-recovery</guid>
<pubDate>Sat, 11 Jul 2026 23:01:53 GMT</pubDate>
<category>Incident Analysis</category>
<description>Railway&apos;s July 2026 outage report shows three systems that captured bad state during 20 minutes of instability and held it silently. Here&apos;s the failure class.</description>
</item>
<item>
<title>Every On-Call Model Has an Expiry Headcount: Lessons from Monzo’s Public Record</title>
<link>https://operatex.dev/blog/monzo-on-call-rotation-models-scaling</link>
<guid isPermaLink="true">https://operatex.dev/blog/monzo-on-call-rotation-models-scaling</guid>
<pubDate>Thu, 09 Jul 2026 20:33:21 GMT</pubDate>
<category>Engineering Management</category>
<description>Monzo published three on-call models at three company sizes - with pay figures and honest failure notes. A teardown of the scaling cliffs every org hits.</description>
</item>
<item>
<title>Automating Root Cause Analysis Without Giving AI Write Access to Production</title>
<link>https://operatex.dev/blog/automated-root-cause-analysis-no-ai-write-access</link>
<guid isPermaLink="true">https://operatex.dev/blog/automated-root-cause-analysis-no-ai-write-access</guid>
<pubDate>Thu, 09 Jul 2026 08:49:05 GMT</pubDate>
<category>Engineering</category>
<description>Manual RCA eats 30-40% of engineering time. Here&apos;s how to automate the investigation across your whole stack without giving AI write access to production.</description>
</item>
<item>
<title>Automated Root Cause Analysis in 2026: A Vendor-Neutral, Whole-Stack Guide for Engineering Leaders</title>
<link>https://operatex.dev/blog/automated-root-cause-analysis-2026-vendor-neutral-guide</link>
<guid isPermaLink="true">https://operatex.dev/blog/automated-root-cause-analysis-2026-vendor-neutral-guide</guid>
<pubDate>Thu, 09 Jul 2026 08:32:46 GMT</pubDate>
<category>Engineering</category>
<description>A vendor-neutral guide to automated root cause analysis across the whole stack, and why the safe default is patch-file-only with no write access to production.</description>
</item>
<item>
<title>The Buyer&apos;s Guide to Automated Root Cause Analysis: What the AI Answers Leave Out</title>
<link>https://operatex.dev/blog/the-buyers-guide-to-automated-root-cause-analysis-what-the-ai-answers-leave-out-7gmv</link>
<guid isPermaLink="true">https://operatex.dev/blog/the-buyers-guide-to-automated-root-cause-analysis-what-the-ai-answers-leave-out-7gmv</guid>
<pubDate>Wed, 08 Jul 2026 14:52:23 GMT</pubDate>
<category>Engineering Leadership</category>
<description>A vendor-neutral buyer&apos;s guide to automated root cause analysis: the features to look for, whole-stack coverage, and why the safe default is patch-file-only, no write access.</description>
</item>
<item>
<title>The Monitoring Pilot Never Flies: Aviation&apos;s Rule for Verifying AI Diagnoses</title>
<link>https://operatex.dev/blog/verifying-ai-root-cause-analysis-aviation-cross-check</link>
<guid isPermaLink="true">https://operatex.dev/blog/verifying-ai-root-cause-analysis-aviation-cross-check</guid>
<pubDate>Mon, 06 Jul 2026 09:12:12 GMT</pubDate>
<category>Engineering Leadership</category>
<description>Airbus builds redundant flight computers with different chips, teams, and languages. Aviation&apos;s independence principle is the standard AI root-cause analysis should be held to.</description>
</item>
<item>
<title>They Added Capacity and It Did Not Help: What WorkOS&apos;s Connection-Pool Starvation Says About Hold-and-Wait Failures</title>
<link>https://operatex.dev/blog/workos-database-connection-pool-exhaustion-analysis</link>
<guid isPermaLink="true">https://operatex.dev/blog/workos-database-connection-pool-exhaustion-analysis</guid>
<pubDate>Sat, 04 Jul 2026 05:23:06 GMT</pubDate>
<category>Postmortem Analysis</category>
<description>WorkOS added capacity and nothing improved. Hold-and-wait connection-pool starvation, why it self-sustains, and the audit to run on your own critical path.</description>
</item>
<item>
<title>When to Hire an SRE (According to People Not Selling You One)</title>
<link>https://operatex.dev/blog/when-to-hire-an-sre-framework</link>
<guid isPermaLink="true">https://operatex.dev/blog/when-to-hire-an-sre-framework</guid>
<pubDate>Sat, 04 Jul 2026 00:33:34 GMT</pubDate>
<category>Engineering Leadership</category>
<description>Everyone ranking for &apos;when to hire an SRE&apos; is selling the answer. A disinterested framework: the real signals, what must exist before the hire, and the alternatives to try first.</description>
</item>
<item>
<title>Toil Went Up, Not Down: The AI-Ops Paradox in the Survey Data</title>
<link>https://operatex.dev/blog/sre-toil-ai-paradox-2026</link>
<guid isPermaLink="true">https://operatex.dev/blog/sre-toil-ai-paradox-2026</guid>
<pubDate>Fri, 03 Jul 2026 18:55:32 GMT</pubDate>
<category>Engineering Leadership</category>
<description>Survey toil fell for years, then reversed as AI adoption went mainstream. The mechanism: verification burden, new ops surfaces, and AI aimed at the wrong loop.</description>
</item>
<item>
<title>Zero-Downtime Database Migrations: The Playbook and the Failure Modes Nobody Writes Down</title>
<link>https://operatex.dev/blog/zero-downtime-database-migration-guide</link>
<guid isPermaLink="true">https://operatex.dev/blog/zero-downtime-database-migration-guide</guid>
<pubDate>Thu, 02 Jul 2026 09:57:00 GMT</pubDate>
<category>Engineering Operations</category>
<description>The expand-contract playbook plus what guides skip: foreign keys, stored procedures, backup mismatches, and how to verify a live migration is safe step by step.</description>
</item>
<item>
<title>AI-Assisted Infra Changes Need a Paper Trail, Not a Chat Log</title>
<link>https://operatex.dev/blog/ai-infrastructure-changes-audit-trail-documentation</link>
<guid isPermaLink="true">https://operatex.dev/blog/ai-infrastructure-changes-audit-trail-documentation</guid>
<pubDate>Wed, 01 Jul 2026 22:19:25 GMT</pubDate>
<category>Engineering Strategy</category>
<description>AI-assisted terraform and pipeline changes ship fast, but the reasoning dies with the chat session. A practical convention for keeping the why in your repo.</description>
</item>
<item>
<title>Retries Are Eating Your Signal: Flaky Tests Are System Bugs Wearing a Costume</title>
<link>https://operatex.dev/blog/flaky-tests-system-nondeterminism-not-noise</link>
<guid isPermaLink="true">https://operatex.dev/blog/flaky-tests-system-nondeterminism-not-noise</guid>
<pubDate>Sat, 27 Jun 2026 02:29:41 GMT</pubDate>
<category>Reliability Engineering</category>
<description>Google found 84% of CI pass-to-fail transitions are flakes. Retrying hides the race conditions and shared state that later cause production incidents.</description>
</item>
<item>
<title>Nobody Will Cut the Requests: A Blame-Safe Playbook for Rightsizing Kubernetes at 25 Percent Utilization</title>
<link>https://operatex.dev/blog/rightsizing-kubernetes-requests-guide</link>
<guid isPermaLink="true">https://operatex.dev/blog/rightsizing-kubernetes-requests-guide</guid>
<pubDate>Thu, 25 Jun 2026 02:14:44 GMT</pubDate>
<category>Engineering Management</category>
<description>Your cluster runs at 25 percent because nobody wants to own the next latency blip. A rollout playbook for cutting padded Kubernetes requests safely.</description>
</item>
<item>
<title>The Delhi Data Center Fire Is a Blast-Radius Audit You Haven&apos;t Run Yet</title>
<link>https://operatex.dev/blog/delhi-data-center-fire-blast-radius-lessons</link>
<guid isPermaLink="true">https://operatex.dev/blog/delhi-data-center-fire-blast-radius-lessons</guid>
<pubDate>Wed, 24 Jun 2026 03:11:21 GMT</pubDate>
<category>Incident Response</category>
<description>A fire in one Delhi data center destroyed decades of customer data and degraded Google Cloud for weeks. Eight audit questions to ask about your own blast radius.</description>
</item>
<item>
<title>The Pipeline Returned 200 OK and Did Nothing: The Agent Failure Class Your Monitoring Reports as Healthy</title>
<link>https://operatex.dev/blog/silent-failures-ai-agent-pipelines-200-ok</link>
<guid isPermaLink="true">https://operatex.dev/blog/silent-failures-ai-agent-pipelines-200-ok</guid>
<pubDate>Mon, 22 Jun 2026 23:22:30 GMT</pubDate>
<category>Engineering &amp; SRE</category>
<description>Agent pipelines fail while every dashboard stays green because 200 OK measures transport, not work. Five shapes of silent failure and how to detect each.</description>
</item>
<item>
<title>Schema Drift Is an Incident Waiting for a Deploy</title>
<link>https://operatex.dev/blog/database-schema-drift-operational-guide</link>
<guid isPermaLink="true">https://operatex.dev/blog/database-schema-drift-operational-guide</guid>
<pubDate>Mon, 22 Jun 2026 17:18:36 GMT</pubDate>
<category>Database Operations</category>
<description>Schema drift turns deploys, failovers, and restores into incidents. How drift happens, what Snowflake&apos;s 13-hour outage shows, and how to detect and triage it.</description>
</item>
<item>
<title>Your Average MTTR Is a Fiction: What 1.8 Million Outages Say About the Tail</title>
<link>https://operatex.dev/blog/mttr-median-vs-mean-outage-data-study</link>
<guid isPermaLink="true">https://operatex.dev/blog/mttr-median-vs-mean-outage-data-study</guid>
<pubDate>Mon, 22 Jun 2026 05:18:16 GMT</pubDate>
<category>Engineering Management</category>
<description>Fresh data from 1.8 million outages: median resolution 1.9 minutes, mean 21.9. The gap explains why your MTTR dashboard misleads, and what to report instead.</description>
</item>
<item>
<title>Knight Capital&apos;s 97 Unread Emails: A $460M Lesson for the AI-Agent Era</title>
<link>https://operatex.dev/blog/knight-capital-incident-lessons-ai-agents</link>
<guid isPermaLink="true">https://operatex.dev/blog/knight-capital-incident-lessons-ai-agents</guid>
<pubDate>Sun, 21 Jun 2026 22:35:44 GMT</pubDate>
<category>Engineering Leadership</category>
<description>Knight Capital lost $460M in 45 minutes. The SEC order reads like a checklist for teams deploying AI agents against production: unreviewed changes, unread signals, unverified fixes.</description>
</item>
<item>
<title>Your Observability Bill Is a Hedge Against Bad Investigations</title>
<link>https://operatex.dev/blog/observability-costs-investigation-hedge</link>
<guid isPermaLink="true">https://operatex.dev/blog/observability-costs-investigation-hedge</guid>
<pubDate>Sun, 21 Jun 2026 20:40:02 GMT</pubDate>
<category>Engineering Management</category>
<description>Every cost guide says collect less telemetry. The real lever is why you store it: an investigation model that can only query pre-collected data. Fix that instead.</description>
</item>
<item>
<title>How to Reduce MTTR: Fix the 80% of the Clock Nobody Instruments</title>
<link>https://operatex.dev/blog/how-to-reduce-mttr-diagnosis-bottleneck</link>
<guid isPermaLink="true">https://operatex.dev/blog/how-to-reduce-mttr-diagnosis-bottleneck</guid>
<pubDate>Fri, 19 Jun 2026 15:15:57 GMT</pubDate>
<category>Engineering Leadership</category>
<description>Most MTTR guides optimize detection. The clock is lost in diagnosis. A phase-by-phase breakdown of where incident time goes and how to shrink the 80%.</description>
</item>
<item>
<title>Is It Us or Is It AWS? Triage for the First Fifteen Minutes of an Upstream Outage</title>
<link>https://operatex.dev/blog/third-party-outage-triage-protocol-aws-july-2026</link>
<guid isPermaLink="true">https://operatex.dev/blog/third-party-outage-triage-protocol-aws-july-2026</guid>
<pubDate>Fri, 19 Jun 2026 09:23:09 GMT</pubDate>
<category>Incident Response</category>
<description>AWS&apos;s July 16 CloudFront outage took 59 minutes to reach the status page. A triage protocol for deciding, in the first fifteen minutes, whether an incident is yours or upstream.</description>
</item>
<item>
<title>The Andon Cord Almost Never Stops the Line: What Software Got Wrong About Toyota&apos;s Most Borrowed Idea</title>
<link>https://operatex.dev/blog/andon-cord-software-development-myth</link>
<guid isPermaLink="true">https://operatex.dev/blog/andon-cord-software-development-myth</guid>
<pubDate>Thu, 18 Jun 2026 16:35:54 GMT</pubDate>
<category>Engineering Operations</category>
<description>Toyota&apos;s andon cord rarely stopped the line—it summoned help in seconds. What the real mechanics teach ops teams about escalation, freezes, and cheap signals.</description>
</item>
</channel>
</rss>