Uptime: design in São Paulo (GRU) · U-01

Runbook U-01 for Uptime in São Paulo (GRU). Marker xserv-u-626c528addf2. This page covers design 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 headers U-09

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

Uptime timeouts U-10

Timeouts on u-10 are tighter than the WAN RTT to Bogotá. Uptime in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

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.