Does Switching Models Lose Context?
its_vayishu · x · 2026-07-17
The author released ContinuityBench, designed to measure whether a fallback model actually receives the full conversational context during a multi-vendor LLM failover, rather than just the last message.
Core Experiments
- Conducted 750 controlled failovers, repeated across 5 rounds
- Used real multi-vendor switches: OpenAI → Anthropic
- Concurrency set to 100
Results
- Naive stateless failover: Context retention rate of 0.00%
- Failover with history forwarding: Context retention rate of 99.20%, with a 95% CI of 98.27%–99.63%
- Minimal extra latency: Average of +59ms, and a median of -450ms (primarily due to normal API fluctuations rather than the forwarding logic itself)
Discovered Issues
During testing, the author discovered a real-world system bug: if 100 concurrent requests are abruptly routed to a rate-limited fallback provider without exponential backoff, it triggers a "self-inflicted DDoS," ultimately locking up the fallback channel entirely.
The code, benchmark harness, and methodology have been open-sourced, and a paper is forthcoming.
Related event: LLM Failover Requires Explicit Context Forwarding(2 posts)→
More from Infra
- Resin lets an agent build standalone LLM inference engines; vLLM and SGLang optimize DeepSeek kernels differently — AccBalanced · 2026-10-27
- Local benchmark: Flint matches Qwen3.6 quality at 50/52 while running 3.6x faster on M4 Pro — RichardSocher · 2026-10-27
- Anthropic S-1: CSP marketplace revenue jumped from 11% to 48% in three years — AccBalanced · 2026-10-27
- Alchemy adds effect/Workflow support across Durable Objects, Workflows and Lambda Durable Functions — samgoodwin89 · 2026-10-27
- Alchemy's Lambda Web Functions run plain Node web servers on Lambda, no OpenNext needed — samgoodwin89 · 2026-10-27
- Alchemy Cuts Cloudflare Bindings CPU Time by Up to 166× Via Profiling — samgoodwin89 · 2026-10-27