Skip to main content
CRON CADENCE: */5 * * * * UTCSOURCE: OFFICIAL STATUSPAGE V2 JSON FEEDS
Agent Outages

AI Infrastructure Outage Telemetry, Compound SLA Cascade & Agent Failover Bench

Single-turn chat tolerates brief API jitter; 8-hop autonomous tool loops multiply every upstream blip. Monitor 5-minute polled Statuspage v2 feeds and model serial availability erosion side by side below.

TELEMETRY ARCHITECTUREPOLL: 300s INTERVAL
FAIL-SAFE RULETimeout → Unknown
PIPELINE MODELSerial R = p^n

Polled AI Provider Status Matrix

Last probe: 2026-11-01 10:21:48 UTC · Cadence: every 5m

OPERATIONAL5
INCIDENT / DEG1
UNKNOWN0
OpenAIModel Inference & Tool-Calling API

All Systems Operational

OperationalStatus
AnthropicClaude API & MCP Host Endpoints

All Systems Operational

OperationalStatus
CloudflareWorkers Runtime, AI Gateway & Edge DNS

Partial System Outage

Non-nominal: Arica, Chile - (ARI) [major_outage], Algiers, Algeria - (ALG) [degraded_performance], Annaba, Algeria - (AAE) [major_outage], Baku, Azerbaijan - (GYD) [degraded_performance]

Partial OutageStatus
GitHubActions Runners, Copilot & Code Tooling

All Systems Operational

OperationalStatus
PineconeVector Memory & Retrieval Indexes

All Systems Operational

OperationalStatus
GroqLow-Latency LPU Inference & Tool-Use API

All Systems Operational

OperationalStatus
Data source & lag notice: Rows poll every 5 minutes from each provider's public Statuspage v2 JSON endpoint and may lag behind live HTTP 429/5xx bursts. Plain-text names identify services without logos or endorsement. Unreachable feeds map strictly to Unknown, never Operational.

Compound SLA Cascade Visualizer

Unhedged multi-agent tool chains fail whenever any serial dependency drops (R = p^n). Adjust hop depth to inspect availability decay.

8 serial hops
CASCADE DECAY CURVE (99.5% BASE)99.0% SLA FLOOR
n=1 hop99.5%n=5 hops97.5%n=8 *96.1%n=10 hops95.1%n=15 hops92.8%

Composite SLA

96.07%

Downtime / Mo

28.7h

Fails / 10k

393

Open Full Multi-Agent Error-Budget Calculator
Fiber-optic patch cables plugged into a core network switch inside an availability zone
INGRESS / EGRESS SWITCH BAYTTFT CAP: 4000ms

Why Status Green Still Drops Multi-Agent Runs

Public status pages reflect broad regional incidents, whereas autonomous loops break on localized tail-latency spikes, HTTP 529 capacity shedding, and unhedged tool retries. Pair external status polling with per-hop circuit breakers.

Hardware & Failover Incident Dossier

Architectural failure modes extracted from primary OpenAI, Cloudflare, Anthropic, and GitHub post-mortems, paired with our four reliability engineering references.

Inference Compute Saturation

HTTP 529 / 429

Separate overloaded gateway codes (529) from org rate limits (429); trip cross-provider fallback within a 4s TTFT deadline.

Control-Plane vs Data-Plane Coupling

DNS & KV STATE

Never block per-turn agent orchestration on synchronous control-plane KV writes; buffer state in local durable queues.

Post-Recovery Duplicate Side Effects

WEBHOOK REPLAY

Attach SHA-256 deterministic idempotency keys (runId + step + canonical args) so delayed webhook replays never double-commit.

MOD-01 // POST-MORTEMS

Root-cause timelines of verified OpenAI, Anthropic, Cloudflare, and GitHub incidents, detailing how multi-step tool-calling agents stall under HTTP 429, 503, and 529 responses.

MOD-02 // SLA MATH

Model compound availability (R = p^n) across 1 to 15 sequential LLM, vector DB, and MCP tool hops, and quantify how secondary-provider circuit breakers cut monthly downtime.

MOD-03 // FAILOVER RPC

Reference TypeScript and infrastructure patterns for 4-second Time-to-First-Token budgets, cross-provider model fallback, and deterministic tool-call idempotency keys.

MOD-04 // CONTAINMENT

SRE outage-containment patterns: prompt-taint separation, short-lived OAuth On-Behalf-Of (OBO) credentials, and Firecracker / gVisor / Wasmtime workload isolation.

Reviewed by Nadia Lindqvist, Lead Reliability & Agent Systems Editor

Reviews multi-provider LLM routing architectures, Statuspage telemetry pipelines, and workload isolation patterns.

Last reviewed:

Reviewed every 3 months

AI-assistance & editorial check: Research outlining and formatting are assisted by AI tools in an offline draft workflow. Nothing on this site publishes automatically without verification. A named human editor opens and verifies every primary source link, command snippet, and factual statement prior to publication. See our Editorial Policy and Corrections Policy.

Verified Primary Sources

Receive Sourced AI Outage Post-Mortems & Resilience Notes

Agent Uptime & Failover Post-Mortems

Store your email for deep-dive engineering post-mortems on verified model, vector, or orchestration outages once dispatches begin. No emails are sent yet.

Protected by Cloudflare Turnstile · Isolated per-site D1 (agentoutages-leads).