Virtual IP: docs in Miami (MIA) · V-72

Runbook V-72 for Virtual IP in Miami (MIA). Marker xserv-v-8702a394f63a. This page covers docs for LATAM operators, not a worldwide average.

Virtual IP: A note on cost and transit

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

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.