Blog

Topic

#failover

5 articles

Timeline of the SpaceX–Cursor deal and OpenAI's response: 21 April option announced, 14 August acquisition completed, 28 August notice given, 12 November proposed shutoff

Cursor loses OpenAI models on November 12: the change-of-control clause behind the date, and the five questions to ask whoever holds your key

Leo Kaka
Matrix of six LLM API products offered as OpenRouter alternatives — Cloudflare AI Gateway, AWS Bedrock, Google Vertex, Groq, LiteLLM and Portkey — against four production columns: cross-vendor failover, a spend cap below the account, the Anthropic Messages API, and a zero-data-retention control, each cell marked available, gated or absent according to the vendor's own documentation

OpenRouter alternatives for production workloads: what Cloudflare, Bedrock, Vertex, Groq, LiteLLM and Portkey actually document

Leo Kaka
Matrix of failover trigger conditions across seven LLM gateways: 5xx, timeouts and 429 are covered everywhere, by default or opt-in; 404 is opt-in or unstated in most; the row for a 200 whose provider state changed is empty in every column, with Portkey's guardrail path as the one partial exception noted in the text

Automatic failover in LiteLLM, Portkey and OpenRouter: what actually triggers it, and the 429 no gateway tracks

Leo Kaka
GitHub's own growth charts from the August 17 post-mortem: merged pull requests, commits and new repositories per month, 2023–2026 (The GitHub Blog)

Retry storms: 9K to 100K RPS, and four rules that stop them

Leo Kaka
Cover: your provider's billing system is part of your failure domain

Tier 3 to Tier 1 mid-flight: the outage no 5xx will catch

Leo Kaka