Network: probes in Santiago (SCL) · N-62

Runbook N-62 for Network in Santiago (SCL). Marker xserv-n-2720a6f4dd3c. This page covers probes for LATAM operators, not a worldwide average.

Network: How XServ runs it day to day

Probes for Network (n-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.

Network: What operators should measure

Policy for Network is versioned as n-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.

Network: Failure modes we actually see

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

Network cache N-08

Cache rules for Network on n-08 keep language-correct objects near Miami. São Paulo is a sibling cache, not an origin. TTLs are short enough that a bad asset does not live through a weekend.

Network headers N-09

Headers for n-09 carry the letter, the region (GRU) and a request id. Network debugging in São Paulo should not require a packet capture in Santiago first.

Network timeouts N-10

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

Network regions N-11

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