Does Failover on letter F share fate with other letters?

The control plane is shared. Data-plane queues for Failover stay isolated, so incident f-01 cannot drain neighbor letters.

Where is Failover measured first?

From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter F.

Failover: handoff in São Paulo (GRU) · F-17

Runbook F-17 for Failover in São Paulo (GRU). Marker xserv-f-08077e83bc23. This page covers handoff for LATAM operators, not a worldwide average.

Failover: How this letter ties to the rest

Handoff from letter F Failover into the rest of the platform uses the same request IDs as the gateway. Runbook f-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

Failover: A note on cost and transit

Rollback for f-06 is a documented command, not a hope. Transit is billed as backup while Failover prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.

Failover: Why it matters on this continent

Design for Failover on letter F starts in São Paulo (GRU). Runbook f-01 keeps a single owner, a written rollback, and a traffic split that can be reversed without a global freeze. Neighbors in Santiago only take overflow after the local pool fails a health window.

Failover policy F-03

Policy for Failover is versioned as f-03. Operators measure error rate, p95 from Bogotá, and time-to-rollback — not a worldwide average. Changes land in Bogotá first, then Miami, with a hold if either region regresses.

Failover capacity F-04

Capacity notes for f-04 assume rainy-season power in Miami and festival peaks toward São Paulo. The failure we actually see is a single uplink, not a cartoon partition of the whole continent. Spare ports and a second provider sit on the same runbook.