Is transit the default path?

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

Does XServ platform on letter X share fate with other letters?

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

XServ platform: docs in Miami (MIA) · X-12

Runbook X-12 for XServ platform in Miami (MIA). Marker xserv-x-65eeff9db439. This page covers docs for LATAM operators, not a worldwide average.

XServ platform: A note on cost and transit

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

XServ platform: Why it matters on this continent

Design for XServ platform on letter X starts in São Paulo (GRU). Runbook x-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.

XServ platform: How XServ runs it day to day

Probes for XServ platform (x-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.

XServ platform rollback X-06

XServ platform peering X-07

Peering for XServ platform (x-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.

XServ platform cache X-08

Cache rules for XServ platform on x-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.

XServ platform headers X-09

Headers for x-09 carry the letter, the region (GRU) and a request id. XServ platform debugging in São Paulo should not require a packet capture in Santiago first.