TLS: policy in Bogotá (BOG) · T-03

Runbook T-03 for TLS in Bogotá (BOG). Marker xserv-t-9377f13d7266. This page covers policy 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 rollback T-06

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

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.