Backbone: probes in Santiago (SCL) · B-62

Runbook B-62 for Backbone in Santiago (SCL). Marker xserv-b-e31f22fe20c7. This page covers probes for LATAM operators, not a worldwide average.

Backbone: How XServ runs it day to day

Probes for Backbone (b-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.

Backbone: What operators should measure

Policy for Backbone is versioned as b-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.

Backbone: Failure modes we actually see

Capacity notes for b-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.

Backbone regions B-11

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

Backbone docs B-12

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

Backbone design B-01

Design for Backbone on letter B starts in São Paulo (GRU). Runbook b-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.

Backbone probe B-02

Probes for Backbone (b-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.