Mesh: cache in Miami (MIA) · M-08

Runbook M-08 for Mesh in Miami (MIA). Marker xserv-m-fbb97934c178. This page covers cache for LATAM operators, not a worldwide average.

Mesh: How XServ runs it day to day

Probes for Mesh (m-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.

Mesh: What operators should measure

Policy for Mesh is versioned as m-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.

Mesh: Failure modes we actually see

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

Mesh rollback M-06

Rollback for m-06 is a documented command, not a hope. Transit is billed as backup while Mesh prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.

Mesh peering M-07

Peering for Mesh (m-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.

Mesh cache M-08

Cache rules for Mesh on m-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.

Mesh headers M-09

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