Is transit the default path?

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

Does Interconnect on letter I share fate with other letters?

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

Interconnect: cache in Miami (MIA) · I-08

Runbook I-08 for Interconnect in Miami (MIA). Marker xserv-i-31ddf82b0013. This page covers cache for LATAM operators, not a worldwide average.

Interconnect: How XServ runs it day to day

Probes for Interconnect (i-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.

Interconnect: What operators should measure

Policy for Interconnect is versioned as i-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.

Interconnect: Failure modes we actually see

Capacity notes for i-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.

Interconnect policy I-03

Interconnect capacity I-04

Interconnect handoff I-05

Handoff from letter I Interconnect into the rest of the platform uses the same request IDs as the gateway. Runbook i-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

Interconnect rollback I-06

Rollback for i-06 is a documented command, not a hope. Transit is billed as backup while Interconnect prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.