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.

Where is TLS measured first?

From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter T.

TLS: headers in São Paulo (GRU) · T-09

Runbook T-09 for TLS in São Paulo (GRU). Marker xserv-t-5647a195474d. This page covers headers for LATAM operators, not a worldwide average.

TLS: What operators should measure

Policy for TLS is versioned as t-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.

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

TLS headers T-09

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

TLS timeouts T-10

Timeouts on t-10 are tighter than the WAN RTT to Bogotá. TLS in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

TLS regions T-11

Region names on t-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. TLS dashboards never say “LATAM” as if it were one RTT.