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

Runbook Y-05 for Sync in São Paulo (GRU). Marker xserv-y-5ec7670d178f. 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 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.

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.