Zones: rollback in Santiago (SCL) · Z-66

Runbook Z-66 for Zones in Santiago (SCL). Marker xserv-z-5fb23c82bc29. This page covers rollback for LATAM operators, not a worldwide average.

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: How XServ runs it day to day

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 regions Z-11

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

Zones docs Z-12

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

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.