Sync: timeouts in Santiago (SCL) · Y-10

Runbook Y-10 for Sync in Santiago (SCL). Marker xserv-y-40ba3c1c4965. This page covers timeouts for LATAM operators, not a worldwide average.

Sync: Failure modes we actually see

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

Sync: How this letter ties to the rest

Handoff from letter Y Sync into the rest of the platform uses the same request IDs as the gateway. Runbook y-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

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 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.

Sync regions Y-11

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

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.