Where is High availability measured first?

From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter H.

How fast is rollback for h-03?

The runbook is a command plus a named owner. There is no wait for a weekly change freeze.

High availability: rollback in Santiago (SCL) · H-06

Runbook H-06 for High availability in Santiago (SCL). Marker xserv-h-e58b4f2f6540. This page covers rollback for LATAM operators, not a worldwide average.

High availability: A note on cost and transit

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

High availability: Why it matters on this continent

Design for High availability on letter H starts in São Paulo (GRU). Runbook h-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.

High availability: How XServ runs it day to day

Probes for High availability (h-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.

High availability regions H-11

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

High availability docs H-12

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