Anycast: timeouts in Santiago (SCL) · A-46

Runbook A-46 for Anycast in Santiago (SCL). Marker xserv-a-e04e3a037128. This page covers timeouts for LATAM operators, not a worldwide average.

Anycast: Failure modes we actually see

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

Anycast: How this letter ties to the rest

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

Anycast: A note on cost and transit

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

Anycast regions A-11

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

Anycast docs A-12

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

Anycast design A-01

Design for Anycast on letter A starts in São Paulo (GRU). Runbook a-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.

Anycast probe A-02

Probes for Anycast (a-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.