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

Runbook F-58 for Failover in Santiago (SCL). Marker xserv-f-d9a265b0908c. 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 timeouts F-10

Timeouts on f-10 are tighter than the WAN RTT to Bogotá. Failover in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

Failover regions F-11

Region names on f-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. Failover dashboards never say “LATAM” as if it were one RTT.

Failover docs F-12

Public docs for letter F stay aligned with identifier xserv-f-pack. Page f-12 is the Failover slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.

Failover design F-01

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.