Does Routing on letter R share fate with other letters?

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

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.

Is transit the default path?

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

Routing policy you can explain on a whiteboard

Communities, local-pref and as-path prepends are named after the outcome they produce, not after a ticket number.

Routing: Why it matters on this continent

Design for Routing on letter R starts in São Paulo (GRU). Runbook r-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.

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: 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 design R-01

Routing probe R-02

Routing policy R-03

Routing capacity R-04

Routing handoff R-05

Routing rollback R-06

Routing peering R-07

Peering for Routing (r-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.

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.

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.