Does Virtual IP on letter V share fate with other letters?

The control plane is shared. Data-plane queues for Virtual IP stay isolated, so incident v-01 cannot drain neighbor letters.

Where is Virtual IP measured first?

From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter V.

Virtual IP: handoff in São Paulo (GRU) · V-53

Runbook V-53 for Virtual IP in São Paulo (GRU). Marker xserv-v-38fda4b9e687. This page covers handoff 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 rollback V-06

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.