Where is Routing measured first?

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

How fast is rollback for r-03?

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

Routing: probes in Santiago (SCL) · R-26

Runbook R-26 for Routing in Santiago (SCL). Marker xserv-r-3454c147f1d3. This page covers probes for LATAM operators, not a worldwide average.

Routing: How XServ runs it day to day

Probes for Routing (r-02) leave Santiago every 15s toward Bogotá. XServ pages the named owner if loss or RTT crosses the letter budget. A probe never shares a queue with bulk transfers, so a saturated WAN does not hide a dead PoP.

Routing: What operators should measure

Policy for Routing is versioned as r-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.

Routing: Failure modes we actually see

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

Routing headers R-09

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

Routing timeouts R-10

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

Routing regions R-11

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

Routing docs R-12

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