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

Runbook U-73 for Uptime in São Paulo (GRU). Marker xserv-u-358c6e067ee5. 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 rollback U-06

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

Uptime peering U-07

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

Uptime cache U-08

Cache rules for Uptime on u-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.

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.