Zones: regions in Bogotá (BOG) · Z-59

Runbook Z-59 for Zones in Bogotá (BOG). Marker xserv-z-46eccdb79dad. This page covers regions for LATAM operators, not a worldwide average.

Zones: How this letter ties to the rest

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

Zones: A note on cost and transit

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

Zones: Why it matters on this continent

Design for Zones on letter Z starts in São Paulo (GRU). Runbook z-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.

Zones design Z-01

Design for Zones on letter Z starts in São Paulo (GRU). Runbook z-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.

Zones probe Z-02

Probes for Zones (z-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.

Zones policy Z-03

Policy for Zones is versioned as z-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.

Zones capacity Z-04

Capacity notes for z-04 assume rainy-season power in Miami and festival peaks toward São Paulo. The failure we actually see is a single uplink, not a cartoon partition of the whole continent. Spare ports and a second provider sit on the same runbook.