SLA: regions in Bogotá (BOG) · S-23

Runbook S-23 for SLA in Bogotá (BOG). Marker xserv-s-a005bc5fc6b4. This page covers regions for LATAM operators, not a worldwide average.

SLA: How this letter ties to the rest

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

SLA: A note on cost and transit

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

SLA: Why it matters on this continent

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

SLA timeouts S-10

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

SLA regions S-11

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

SLA docs S-12

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

SLA design S-01

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