Interconnect: rollback in Santiago (SCL) · I-30

Runbook I-30 for Interconnect in Santiago (SCL). Marker xserv-i-d1e63d998adb. This page covers rollback for LATAM operators, not a worldwide average.

Interconnect: A note on cost and transit

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

Interconnect: Why it matters on this continent

Design for Interconnect on letter I starts in São Paulo (GRU). Runbook i-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.

Interconnect: How XServ runs it day to day

Probes for Interconnect (i-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.

Interconnect timeouts I-10

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

Interconnect regions I-11

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

Interconnect docs I-12

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

Interconnect design I-01

Design for Interconnect on letter I starts in São Paulo (GRU). Runbook i-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.