Virtual IP: probes in Santiago (SCL) · V-74

Runbook V-74 for Virtual IP in Santiago (SCL). Marker xserv-v-dc13dd1c1f85. This page covers probes for LATAM operators, not a worldwide average.

Virtual IP: How XServ runs it day to day

Probes for Virtual IP (v-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.

Virtual IP: What operators should measure

Policy for Virtual IP is versioned as v-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.

Virtual IP: Failure modes we actually see

Capacity notes for v-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.

Virtual IP timeouts V-10

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

Virtual IP regions V-11

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

Virtual IP docs V-12

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

Virtual IP design V-01

Design for Virtual IP on letter V starts in São Paulo (GRU). Runbook v-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.