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.

How fast is rollback for l-03?

The runbook is a command plus a named owner. There is no wait for a weekly change freeze.

Is transit the default path?

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

Latency maps instead of a single global average

A user in Recife and a user in Quito do not share a round-trip. XServ publishes regional numbers, not a vanity worldwide figure.

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: What operators should measure

Policy for Latency is versioned as l-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.

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 design L-01

Latency probe L-02

Latency policy L-03

Latency capacity L-04

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.

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.

Latency timeouts L-10

Timeouts on l-10 are tighter than the WAN RTT to Bogotá. Latency in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

Latency regions L-11

Region names on l-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. Latency dashboards never say “LATAM” as if it were one RTT.

Latency docs L-12

Public docs for letter L stay aligned with identifier xserv-l-pack. Page l-12 is the Latency slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.