Where is Sync measured first?

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

How fast is rollback for y-03?

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

Sync: rollback in Santiago (SCL) · Y-66

Runbook Y-66 for Sync in Santiago (SCL). Marker xserv-y-119d1e499149. This page covers rollback for LATAM operators, not a worldwide average.

Sync: A note on cost and transit

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

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 peering Y-07

Peering for Sync (y-07) prefers the IX fabric that already carries last-mile ISPs in Bogotá. Session counts and prefix limits are on the same page as the Miami backup path.

Sync cache Y-08

Cache rules for Sync on y-08 keep language-correct objects near Miami. São Paulo is a sibling cache, not an origin. TTLs are short enough that a bad asset does not live through a weekend.

Sync headers Y-09

Headers for y-09 carry the letter, the region (GRU) and a request id. Sync debugging in São Paulo should not require a packet capture in Santiago first.

Sync timeouts Y-10

Timeouts on y-10 are tighter than the WAN RTT to Bogotá. Sync in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.