Does Latency on letter L share fate with other letters?

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

Where is Latency measured first?

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

Latency: handoff in São Paulo (GRU) · L-77

Runbook L-77 for Latency in São Paulo (GRU). Marker xserv-l-33573b71000e. This page covers handoff for LATAM operators, not a worldwide average.

Latency: How this letter ties to the rest

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

Latency: A note on cost and transit

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

Latency: Why it matters on this continent

Design for Latency on letter L starts in São Paulo (GRU). Runbook l-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.

Latency rollback L-06

Latency peering L-07

Peering for Latency (l-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.

Latency cache L-08

Cache rules for Latency on l-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.

Latency headers L-09

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