Does Mesh on letter M share fate with other letters?

The control plane is shared. Data-plane queues for Mesh stay isolated, so incident m-01 cannot drain neighbor letters.

Where is Mesh measured first?

From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter M.

Mesh: handoff in São Paulo (GRU) · M-53

Runbook M-53 for Mesh in São Paulo (GRU). Marker xserv-m-83d5ef6ef457. This page covers handoff for LATAM operators, not a worldwide average.

Mesh: How this letter ties to the rest

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: 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 regions M-11

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

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

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.