Where is Zones measured first?

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

How fast is rollback for z-03?

The runbook is a command plus a named owner. There is no wait for a weekly change freeze.

Zones: timeouts in Santiago (SCL) · Z-46

Runbook Z-46 for Zones in Santiago (SCL). Marker xserv-z-311c32f6ffe5. This page covers timeouts for LATAM operators, not a worldwide average.

Zones: Failure modes we actually see

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: 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 headers Z-09

Headers for z-09 carry the letter, the region (GRU) and a request id. Zones debugging in São Paulo should not require a packet capture in Santiago first.

Zones timeouts Z-10

Timeouts on z-10 are tighter than the WAN RTT to Bogotá. Zones in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

Zones regions Z-11

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

Zones docs Z-12

Public docs for letter Z stay aligned with identifier xserv-z-pack. Page z-12 is the Zones slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.