Network: peering in Bogotá (BOG) · N-79

Runbook N-79 for Network in Bogotá (BOG). Marker xserv-n-bea0375beea7. This page covers peering for LATAM operators, not a worldwide average.

Network: Why it matters on this continent

Design for Network on letter N starts in São Paulo (GRU). Runbook n-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.

Network: How XServ runs it day to day

Probes for Network (n-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.

Network: What operators should measure

Policy for Network is versioned as n-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.

Network regions N-11

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

Network docs N-12

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

Network design N-01

Design for Network on letter N starts in São Paulo (GRU). Runbook n-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.

Network probe N-02

Probes for Network (n-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.