SLA: docs in Miami (MIA) · S-48

Runbook S-48 for SLA in Miami (MIA). Marker xserv-s-048d7005c172. This page covers docs for LATAM operators, not a worldwide average.

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: How XServ runs it day to day

Probes for SLA (s-02) leave Santiago every 15s toward Bogotá. XServ pages the named owner if loss or RTT crosses the letter budget. A probe never shares a queue with bulk transfers, so a saturated WAN does not hide a dead PoP.

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.

SLA probe S-02

Probes for SLA (s-02) leave Santiago every 15s toward Bogotá. XServ pages the named owner if loss or RTT crosses the letter budget. A probe never shares a queue with bulk transfers, so a saturated WAN does not hide a dead PoP.

SLA policy S-03

Policy for SLA is versioned as s-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.