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

Runbook W-28 for WAN in Miami (MIA). Marker xserv-w-919b9251fa38. 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 headers W-09

Headers for w-09 carry the letter, the region (GRU) and a request id. WAN debugging in São Paulo should not require a packet capture in Santiago first.

WAN timeouts W-10

Timeouts on w-10 are tighter than the WAN RTT to Bogotá. WAN in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

WAN regions W-11

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

WAN docs W-12

Public docs for letter W stay aligned with identifier xserv-w-pack. Page w-12 is the WAN slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.