Sync: design in São Paulo (GRU) · Y-01

Runbook Y-01 for Sync in São Paulo (GRU). Marker xserv-y-98aa06704e02. This page covers design for LATAM operators, not a worldwide average.

Sync: Why it matters on this continent

Design for Sync on letter Y starts in São Paulo (GRU). Runbook y-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.

Sync: How XServ runs it day to day

Probes for Sync (y-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.

Sync: What operators should measure

Policy for Sync is versioned as y-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.

Sync docs Y-12

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

Sync design Y-01

Design for Sync on letter Y starts in São Paulo (GRU). Runbook y-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.

Sync probe Y-02

Probes for Sync (y-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.

Sync policy Y-03

Policy for Sync is versioned as y-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.