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.

Where is WAN measured first?

From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter W.

WAN: handoff in São Paulo (GRU) · W-05

Runbook W-05 for WAN in São Paulo (GRU). Marker xserv-w-c8de7cdfa90d. This page covers handoff for LATAM operators, not a worldwide average.

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: Why it matters on this continent

Design for WAN on letter W starts in São Paulo (GRU). Runbook w-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.

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.

WAN cache W-08

Cache rules for WAN on w-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.

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.