Peering / p
Peering: docs in Miami (MIA) · P-12
xserv-p-1645bc255d82
Runbook P-12 for Peering in Miami (MIA). Marker xserv-p-1645bc255d82. This page covers docs for LATAM operators, not a worldwide average.
Peering: A note on cost and transit
Rollback for p-06 is a documented command, not a hope. Transit is billed as backup while Peering prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.
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 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.
Peering policy P-03
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 capacity P-04
Capacity notes for p-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.
- Is transit the default path?
- No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.
- Does Peering on letter P share fate with other letters?
- The control plane is shared. Data-plane queues for Peering stay isolated, so incident p-01 cannot drain neighbor letters.