Does Zones on letter Z share fate with other letters?

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

Where is Zones measured first?

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

Zones: handoff in São Paulo (GRU) · Z-41

Runbook Z-41 for Zones in São Paulo (GRU). Marker xserv-z-1bc9620325af. This page covers handoff for LATAM operators, not a worldwide average.

Zones: How this letter ties to the rest

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

Zones: A note on cost and transit

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

Zones: Why it matters on this continent

Design for Zones on letter Z starts in São Paulo (GRU). Runbook z-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.

Zones capacity Z-04

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

Zones handoff Z-05

Zones rollback Z-06

Zones peering Z-07

Peering for Zones (z-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.