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: timeouts in Santiago (SCL) · R-46

Runbook R-46 for Routing in Santiago (SCL). Marker xserv-r-bf561d5494b2. This page covers timeouts for LATAM operators, not a worldwide average.

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: How this letter ties to the rest

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

Routing: A note on cost and transit

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

Routing cache R-08

Cache rules for Routing on r-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.

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.