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: capacity in Miami (MIA) · M-52

Runbook M-52 for Mesh in Miami (MIA). Marker xserv-m-e4a796960e20. This page covers capacity for LATAM operators, not a worldwide average.

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

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.