Backbone: regions in Bogotá (BOG) · B-23

Runbook B-23 for Backbone in Bogotá (BOG). Marker xserv-b-f433bbac9083. This page covers regions for LATAM operators, not a worldwide average.

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

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

Backbone: Why it matters on this continent

Design for Backbone on letter B starts in São Paulo (GRU). Runbook b-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.

Backbone policy B-03

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 capacity B-04

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 handoff B-05

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 rollback B-06

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