Is transit the default path?

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

Does WAN on letter W share fate with other letters?

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

WAN: capacity in Miami (MIA) · W-40

Runbook W-40 for WAN in Miami (MIA). Marker xserv-w-d3c6c10661e2. This page covers capacity for LATAM operators, not a worldwide average.

WAN: Failure modes we actually see

Capacity notes for w-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.

WAN: How this letter ties to the rest

Handoff from letter W WAN into the rest of the platform uses the same request IDs as the gateway. Runbook w-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

WAN: A note on cost and transit

Rollback for w-06 is a documented command, not a hope. Transit is billed as backup while WAN prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.

WAN capacity W-04

WAN handoff W-05

WAN rollback W-06

WAN peering W-07

Peering for WAN (w-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.