Is transit the default path?

No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.

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.

Latency: capacity in Miami (MIA) · L-04

Runbook L-04 for Latency in Miami (MIA). Marker xserv-l-eec5fbb93d76. This page covers capacity for LATAM operators, not a worldwide average.

Latency: Failure modes we actually see

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

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.