Peering: design in São Paulo (GRU) · P-61

Runbook P-61 for Peering in São Paulo (GRU). Marker xserv-p-881b7d4bdb14. This page covers design for LATAM operators, not a worldwide average.

Peering: Why it matters on this continent

Design for Peering on letter P starts in São Paulo (GRU). Runbook p-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.

Peering: How XServ runs it day to day

Probes for Peering (p-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.

Peering: What operators should measure

Policy for Peering is versioned as p-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.

Peering regions P-11

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

Peering docs P-12

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

Peering design P-01

Design for Peering on letter P starts in São Paulo (GRU). Runbook p-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.

Peering probe P-02

Probes for Peering (p-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.