Peering: timeouts in Santiago (SCL) · P-10

Runbook P-10 for Peering in Santiago (SCL). Marker xserv-p-e12adc15720d. This page covers timeouts for LATAM operators, not a worldwide average.

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: How this letter ties to the rest

Handoff from letter P Peering into the rest of the platform uses the same request IDs as the gateway. Runbook p-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

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 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.