Virtual IP: design in São Paulo (GRU) · V-25

Runbook V-25 for Virtual IP in São Paulo (GRU). Marker xserv-v-1727fe0e61dc. This page covers design 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 capacity V-04

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 handoff V-05

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

Virtual IP rollback V-06

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

Virtual IP peering V-07

Peering for Virtual IP (v-07) prefers the IX fabric that already carries last-mile ISPs in Bogotá. Session counts and prefix limits are on the same page as the Miami backup path.