Keys: headers in São Paulo (GRU) · K-45

Runbook K-45 for Keys in São Paulo (GRU). Marker xserv-k-1af549adafb9. This page covers headers for LATAM operators, not a worldwide average.

Keys: What operators should measure

Policy for Keys is versioned as k-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.

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 capacity K-04

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 handoff K-05

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 rollback K-06

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