SLA: headers in São Paulo (GRU) · S-33

Runbook S-33 for SLA in São Paulo (GRU). Marker xserv-s-3df697807f63. This page covers headers for LATAM operators, not a worldwide average.

SLA: What operators should measure

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: Failure modes we actually see

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

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.

SLA headers S-09

Headers for s-09 carry the letter, the region (GRU) and a request id. SLA debugging in São Paulo should not require a packet capture in Santiago first.