Keys: timeouts in Santiago (SCL) · K-46

Runbook K-46 for Keys in Santiago (SCL). Marker xserv-k-b4fb70537b67. This page covers timeouts for LATAM operators, not a worldwide average.

Keys: Failure modes we actually see

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

Keys: How this letter ties to the rest

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

Keys: A note on cost and transit

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

Keys cache K-08

Cache rules for Keys on k-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.

Keys headers K-09

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

Keys timeouts K-10

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

Keys regions K-11

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