Is transit the default path?

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

Does TLS on letter T share fate with other letters?

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

TLS: capacity in Miami (MIA) · T-64

Runbook T-64 for TLS in Miami (MIA). Marker xserv-t-e6257f45c465. This page covers capacity for LATAM operators, not a worldwide average.

TLS: Failure modes we actually see

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

TLS: How this letter ties to the rest

Handoff from letter T TLS into the rest of the platform uses the same request IDs as the gateway. Runbook t-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

TLS: A note on cost and transit

Rollback for t-06 is a documented command, not a hope. Transit is billed as backup while TLS prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.

TLS handoff T-05

TLS rollback T-06

TLS peering T-07

Peering for TLS (t-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.

TLS cache T-08

Cache rules for TLS on t-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.