Does Sync on letter Y share fate with other letters?

The control plane is shared. Data-plane queues for Sync stay isolated, so incident y-01 cannot drain neighbor letters.

Where is Sync measured first?

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

Sync: handoff in São Paulo (GRU) · Y-41

Runbook Y-41 for Sync in São Paulo (GRU). Marker xserv-y-a18d10b19aec. This page covers handoff for LATAM operators, not a worldwide average.

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: 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 capacity Y-04

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 handoff Y-05

Sync rollback Y-06

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.