Backbone: headers in São Paulo (GRU) · B-21

Runbook B-21 for Backbone in São Paulo (GRU). Marker xserv-b-4e58cec33220. This page covers headers for LATAM operators, not a worldwide average.

Backbone: What operators should measure

Policy for Backbone is versioned as b-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.

Backbone: Failure modes we actually see

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

Backbone: How this letter ties to the rest

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

Backbone peering B-07

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

Backbone cache B-08

Cache rules for Backbone on b-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.

Backbone headers B-09

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

Backbone timeouts B-10

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