How fast is rollback for w-03?

The runbook is a command plus a named owner. There is no wait for a weekly change freeze.

Is transit the default path?

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

WAN: regions in Bogotá (BOG) · W-59

Runbook W-59 for WAN in Bogotá (BOG). Marker xserv-w-b28b01c29967. This page covers regions 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 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.

WAN design W-01

WAN probe W-02

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