Is transit the default path?

No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.

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.

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

Runbook M-68 for Mesh in Miami (MIA). Marker xserv-m-4439a3224475. 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 capacity M-04

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.

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.