Latency: docs in Miami (MIA) · L-48

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

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: How XServ runs it day to day

Probes for Latency (l-02) leave Santiago every 15s toward Bogotá. XServ pages the named owner if loss or RTT crosses the letter budget. A probe never shares a queue with bulk transfers, so a saturated WAN does not hide a dead PoP.

Latency rollback L-06

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