Virtual IP: peering in Bogotá (BOG) · V-43

Runbook V-43 for Virtual IP in Bogotá (BOG). Marker xserv-v-b336ac9c0f9c. This page covers peering for LATAM operators, not a worldwide average.

Virtual IP: Why it matters on this continent

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.

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 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.

Virtual IP probe V-02

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.