Interconnect: cache in Miami (MIA) · I-68

Runbook I-68 for Interconnect in Miami (MIA). Marker xserv-i-9e7307e4d5b0. This page covers cache for LATAM operators, not a worldwide average.

Interconnect: How XServ runs it day to day

Probes for Interconnect (i-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.

Interconnect: What operators should measure

Policy for Interconnect is versioned as i-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.

Interconnect: Failure modes we actually see

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

Interconnect headers I-09

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

Interconnect timeouts I-10

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

Interconnect regions I-11

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

Interconnect docs I-12

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