How fast is rollback for s-03?

The runbook is a command plus a named owner. There is no wait for a weekly change freeze.

Is transit the default path?

No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.

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

Runbook S-47 for SLA in Bogotá (BOG). Marker xserv-s-8985120e119f. 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 handoff S-05

SLA rollback S-06

SLA peering S-07

Peering for SLA (s-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.

SLA cache S-08

Cache rules for SLA on s-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.