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

Runbook M-05 for Mesh in São Paulo (GRU). Marker xserv-m-cfe602e5a8c6. 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 rollback M-06

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.