Virtual IP: regions in Bogotá (BOG) · V-35

Runbook V-35 for Virtual IP in Bogotá (BOG). Marker xserv-v-0cc3626c004a. This page covers regions for LATAM operators, not a worldwide average.

Virtual IP: How this letter ties to the rest

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

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.