XServ platform: peering in Bogotá (BOG) · X-07

Runbook X-07 for XServ platform in Bogotá (BOG). Marker xserv-x-a9c6f875776b. This page covers peering for LATAM operators, not a worldwide average.

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: What operators should measure

Policy for XServ platform is versioned as x-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.

XServ platform timeouts X-10

Timeouts on x-10 are tighter than the WAN RTT to Bogotá. XServ platform in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

XServ platform regions X-11

Region names on x-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. XServ platform dashboards never say “LATAM” as if it were one RTT.

XServ platform docs X-12

Public docs for letter X stay aligned with identifier xserv-x-pack. Page x-12 is the XServ platform slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.

XServ platform design X-01

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.