Latency: timeouts in Santiago (SCL) · L-22

Runbook L-22 for Latency in Santiago (SCL). Marker xserv-l-59d6758fb51f. This page covers timeouts for LATAM operators, not a worldwide average.

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

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

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

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.