Keys: regions in Bogotá (BOG) · K-11

Runbook K-11 for Keys in Bogotá (BOG). Marker xserv-k-b9fdf212ad7a. This page covers regions for LATAM operators, not a worldwide average.

Keys: How this letter ties to the rest

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: A note on cost and transit

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: 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 regions K-11

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

Keys docs K-12

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

Keys design K-01

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 probe K-02

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.