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

Runbook V-62 for Virtual IP in Santiago (SCL). Marker xserv-v-0746a5968ec3. 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 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.

Virtual IP cache V-08

Cache rules for Virtual IP on v-08 keep language-correct objects near Miami. São Paulo is a sibling cache, not an origin. TTLs are short enough that a bad asset does not live through a weekend.

Virtual IP headers V-09

Headers for v-09 carry the letter, the region (GRU) and a request id. Virtual IP debugging in São Paulo should not require a packet capture in Santiago first.