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

Runbook S-24 for SLA in Miami (MIA). Marker xserv-s-cfb3ddb00e6c. 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 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.

SLA capacity S-04

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

SLA handoff S-05

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 rollback S-06

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.