Keys: peering in Bogotá (BOG) · K-43

Runbook K-43 for Keys in Bogotá (BOG). Marker xserv-k-81fd171ed88c. This page covers peering for LATAM operators, not a worldwide average.

Keys: Why it matters on this continent

Design for Keys on letter K starts in São Paulo (GRU). Runbook k-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.

Keys: How XServ runs it day to day

Probes for Keys (k-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.

Keys: What operators should measure

Policy for Keys is versioned as k-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.

Keys handoff K-05

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

Keys rollback K-06

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

Keys peering K-07

Peering for Keys (k-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.

Keys cache K-08

Cache rules for Keys on k-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.