<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Failover on LLM API Reliability Notes</title><link>https://llmapireliability.com/tags/failover/</link><description>Practical guides for LLM API reliability and fallback engineering.</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://llmapireliability.com/tags/failover/index.xml" rel="self" type="application/rss+xml"/><item><title>Overload Signals for LLM API Failover Runbooks</title><link>https://llmapireliability.com/posts/overload-runbook-signals-for-llm-api-failover/</link><pubDate>Fri, 12 Jun 2026 02:04:21 +0000</pubDate><guid>https://llmapireliability.com/posts/overload-runbook-signals-for-llm-api-failover/</guid><description>A practical operator runbook for deciding when LLM API overload symptoms should trigger throttling, degradation, or failover.</description></item><item><title>How to Use Response Contract Evidence to Harden LLM API Failover</title><link>https://llmapireliability.com/posts/response-contract-evidence-for-llm-api-failover/</link><pubDate>Mon, 08 Jun 2026 08:57:16 +0000</pubDate><guid>https://llmapireliability.com/posts/response-contract-evidence-for-llm-api-failover/</guid><description>A practical guide to the response-contract fields, error shapes, and cross-provider parameter differences that operators should verify before wiring up an LLM API failover path.</description></item></channel></rss>