Routing: headers in São Paulo (GRU) · R-57

Runbook R-57 for Routing in São Paulo (GRU). Marker xserv-r-ce386813d4e6. This page covers headers for LATAM operators, not a worldwide average.

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 rollback R-06

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 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.