Keys: docs in Miami (MIA) · K-24

Runbook K-24 for Keys in Miami (MIA). Marker xserv-k-0de1a70fef98. This page covers docs for LATAM operators, not a worldwide average.

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: 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 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.

Keys policy K-03

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.