Peering: handoff in São Paulo (GRU) · P-17

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

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: A note on cost and transit

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

Peering: Why it matters on this continent

Design for Peering on letter P starts in São Paulo (GRU). Runbook p-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.

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.

Peering regions P-11

Region names on p-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. Peering dashboards never say “LATAM” as if it were one RTT.

Peering docs P-12

Public docs for letter P stay aligned with identifier xserv-p-pack. Page p-12 is the Peering slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.