Anycast: docs in Miami (MIA) · A-24

Runbook A-24 for Anycast in Miami (MIA). Marker xserv-a-d7902d8e45e7. This page covers docs for LATAM operators, not a worldwide average.

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

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: How XServ runs it day to day

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.

Anycast capacity A-04

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 handoff A-05

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 rollback A-06

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 peering A-07

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