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.

Is transit the default path?

No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.

Sync: policy in Bogotá (BOG) · Y-03

Runbook Y-03 for Sync in Bogotá (BOG). Marker xserv-y-87c233a7ff78. This page covers policy for LATAM operators, not a worldwide average.

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

Sync rollback Y-06

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