Mesh: docs in Miami (MIA) · M-36

Runbook M-36 for Mesh in Miami (MIA). Marker xserv-m-30bb43b8042e. This page covers docs for LATAM operators, not a worldwide average.

Mesh: A note on cost and transit

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: Why it matters on this continent

Design for Mesh on letter M starts in São Paulo (GRU). Runbook m-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.

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 policy M-03

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 capacity M-04

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 handoff M-05

Handoff from letter M Mesh into the rest of the platform uses the same request IDs as the gateway. Runbook m-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

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.