TLS: regions in Bogotá (BOG) · T-59

Runbook T-59 for TLS in Bogotá (BOG). Marker xserv-t-11f1995a85ad. This page covers regions for LATAM operators, not a worldwide average.

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: Why it matters on this continent

Design for TLS on letter T starts in São Paulo (GRU). Runbook t-01 keeps a single owner, a written rollback, and a traffic split that can be reversed without a global freeze. Neighbors in Santiago only take overflow after the local pool fails a health window.

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.

TLS docs T-12

Public docs for letter T stay aligned with identifier xserv-t-pack. Page t-12 is the TLS slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.

TLS design T-01

Design for TLS on letter T starts in São Paulo (GRU). Runbook t-01 keeps a single owner, a written rollback, and a traffic split that can be reversed without a global freeze. Neighbors in Santiago only take overflow after the local pool fails a health window.