Peering: headers in São Paulo (GRU) · P-57

Runbook P-57 for Peering in São Paulo (GRU). Marker xserv-p-d70fe078f21a. This page covers headers for LATAM operators, not a worldwide average.

Peering: What operators should measure

Policy for Peering is versioned as p-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.

Peering: Failure modes we actually see

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

Peering: How this letter ties to the rest

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

Peering peering P-07

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

Peering cache P-08

Cache rules for Peering on p-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.

Peering headers P-09

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

Peering timeouts P-10

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