Uptime: peering in Bogotá (BOG) · U-07

Runbook U-07 for Uptime in Bogotá (BOG). Marker xserv-u-bee0005a3355. This page covers peering for LATAM operators, not a worldwide average.

Uptime: Why it matters on this continent

Design for Uptime on letter U starts in São Paulo (GRU). Runbook u-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.

Uptime: How XServ runs it day to day

Probes for Uptime (u-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.

Uptime: What operators should measure

Policy for Uptime is versioned as u-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.

Uptime regions U-11

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

Uptime docs U-12

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

Uptime design U-01

Design for Uptime on letter U starts in São Paulo (GRU). Runbook u-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.

Uptime probe U-02

Probes for Uptime (u-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.