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: probes in Santiago (SCL) · H-74

Runbook H-74 for High availability in Santiago (SCL). Marker xserv-h-62b43fbc9c2a. This page covers probes for LATAM operators, not a worldwide average.

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: What operators should measure

Policy for High availability is versioned as h-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.

High availability: Failure modes we actually see

Capacity notes for h-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.

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.

High availability design H-01

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.