Routing: regions in Bogotá (BOG) · R-23

Runbook R-23 for Routing in Bogotá (BOG). Marker xserv-r-7abdd5101dce. This page covers regions for LATAM operators, not a worldwide average.

Routing: How this letter ties to the rest

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

Routing: A note on cost and transit

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

Routing: Why it matters on this continent

Design for Routing on letter R starts in São Paulo (GRU). Runbook r-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.

Routing capacity R-04

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

Routing handoff R-05

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

Routing rollback R-06

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

Routing peering R-07

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