Is transit the default path?

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

Does SLA on letter S share fate with other letters?

The control plane is shared. Data-plane queues for SLA stay isolated, so incident s-01 cannot drain neighbor letters.

SLA: capacity in Miami (MIA) · S-52

Runbook S-52 for SLA in Miami (MIA). Marker xserv-s-836320a166a5. This page covers capacity for LATAM operators, not a worldwide average.

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

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.