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

Runbook L-17 for Latency in São Paulo (GRU). Marker xserv-l-a6312564258b. 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 capacity L-04

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

Latency handoff L-05

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.