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

Runbook M-72 for Mesh in Miami (MIA). Marker xserv-m-032a58cda271. 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 docs M-12

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

Mesh design M-01

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 probe M-02

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.