Is transit the default path?

No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.

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.

Virtual IP: capacity in Miami (MIA) · V-28

Runbook V-28 for Virtual IP in Miami (MIA). Marker xserv-v-57e6b0e1f67e. This page covers capacity for LATAM operators, not a worldwide average.

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

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.