Is transit the default path?

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

Does Routing on letter R share fate with other letters?

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

Routing: docs in Miami (MIA) · R-60

Runbook R-60 for Routing in Miami (MIA). Marker xserv-r-ad8fcee42800. This page covers docs for LATAM operators, not a worldwide average.

Routing: A note on cost and transit

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

Routing: Why it matters on this continent

Design for Routing on letter R starts in São Paulo (GRU). Runbook r-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.

Routing: How XServ runs it day to day

Probes for Routing (r-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.

Routing design R-01

Routing probe R-02

Routing policy R-03

Policy for Routing is versioned as r-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.

Routing capacity R-04

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