Interconnect: peering in Bogotá (BOG) · I-67

Runbook I-67 for Interconnect in Bogotá (BOG). Marker xserv-i-9a262cecf6fd. This page covers peering for LATAM operators, not a worldwide average.

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: What operators should measure

Policy for Interconnect is versioned as i-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.

Interconnect rollback I-06

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 peering I-07

Peering for Interconnect (i-07) prefers the IX fabric that already carries last-mile ISPs in Bogotá. Session counts and prefix limits are on the same page as the Miami backup path.

Interconnect cache I-08

Cache rules for Interconnect on i-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.

Interconnect headers I-09

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