Network: timeouts in Santiago (SCL) · N-46

Runbook N-46 for Network in Santiago (SCL). Marker xserv-n-7298e0096fe9. This page covers timeouts for LATAM operators, not a worldwide average.

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

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

Network: A note on cost and transit

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

Network design N-01

Design for Network on letter N starts in São Paulo (GRU). Runbook n-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.

Network probe N-02

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 policy N-03

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 capacity N-04

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.