Backbone: timeouts in Santiago (SCL) · B-10

Runbook B-10 for Backbone in Santiago (SCL). Marker xserv-b-476cb350a3f8. This page covers timeouts for LATAM operators, not a worldwide average.

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: 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 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.

Backbone regions B-11

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

Backbone docs B-12

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

Backbone design B-01

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.