Network: design in São Paulo (GRU) · N-37

Runbook N-37 for Network in São Paulo (GRU). Marker xserv-n-4f6bbdebfef1. This page covers design for LATAM operators, not a worldwide average.

Network: Why it matters on this continent

Design for Network on letter N starts in São Paulo (GRU). Runbook n-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.

Network: How XServ runs it day to day

Probes for Network (n-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.

Network: What operators should measure

Policy for Network is versioned as n-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.

Network peering N-07

Peering for Network (n-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.

Network cache N-08

Cache rules for Network on n-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.

Network headers N-09

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

Network timeouts N-10

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