Failover: timeouts in Santiago (SCL) · F-70

Runbook F-70 for Failover in Santiago (SCL). Marker xserv-f-8de4b967d9ad. This page covers timeouts for LATAM operators, not a worldwide average.

Failover: Failure modes we actually see

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.

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 probe F-02

Probes for Failover (f-02) leave Santiago every 15s toward Bogotá. XServ pages the named owner if loss or RTT crosses the letter budget. A probe never shares a queue with bulk transfers, so a saturated WAN does not hide a dead PoP.

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.

Failover handoff F-05

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.