Uptime: regions in Bogotá (BOG) · U-71

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

Uptime: How this letter ties to the rest

Handoff from letter U Uptime into the rest of the platform uses the same request IDs as the gateway. Runbook u-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

Uptime: A note on cost and transit

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

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.