Latency: probes in Santiago (SCL) · L-74

Runbook L-74 for Latency in Santiago (SCL). Marker xserv-l-6ed5f5af362c. This page covers probes for LATAM operators, not a worldwide average.

Latency: How XServ runs it day to day

Probes for Latency (l-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.

Latency: What operators should measure

Policy for Latency is versioned as l-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.

Latency: Failure modes we actually see

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

Latency docs L-12

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

Latency design L-01

Design for Latency on letter L starts in São Paulo (GRU). Runbook l-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.

Latency probe L-02

Probes for Latency (l-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.

Latency policy L-03

Policy for Latency is versioned as l-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.