Does Keys on letter K share fate with other letters?

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

Where is Keys measured first?

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

Keys: handoff in São Paulo (GRU) · K-41

Runbook K-41 for Keys in São Paulo (GRU). Marker xserv-k-2f75b5b8bf25. This page covers handoff for LATAM operators, not a worldwide average.

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

Design for Keys on letter K starts in São Paulo (GRU). Runbook k-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.

Keys handoff K-05

Keys rollback K-06

Keys peering K-07

Peering for Keys (k-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.

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.