Latency: rollback in Santiago (SCL) · L-54

Runbook L-54 for Latency in Santiago (SCL). Marker xserv-l-d706c83fcd02. This page covers rollback for LATAM operators, not a worldwide average.

Latency: A note on cost and transit

Rollback for l-06 is a documented command, not a hope. Transit is billed as backup while Latency prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.

Latency: Why it matters on this continent

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: 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 timeouts L-10

Timeouts on l-10 are tighter than the WAN RTT to Bogotá. Latency in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

Latency regions L-11

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

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.