Peering: cache in Miami (MIA) · P-80

Runbook P-80 for Peering in Miami (MIA). Marker xserv-p-005d559f2565. This page covers cache for LATAM operators, not a worldwide average.

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: Failure modes we actually see

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.

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.

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.