Interconnect: headers in São Paulo (GRU) · I-33

Runbook I-33 for Interconnect in São Paulo (GRU). Marker xserv-i-8e0f853ec0cf. This page covers headers for LATAM operators, not a worldwide average.

Interconnect: What operators should measure

Policy for Interconnect is versioned as i-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.

Interconnect: Failure modes we actually see

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

Interconnect: How this letter ties to the rest

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

Interconnect regions I-11

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

Interconnect docs I-12

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

Interconnect design I-01

Design for Interconnect on letter I starts in São Paulo (GRU). Runbook i-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.

Interconnect probe I-02

Probes for Interconnect (i-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.