Anycast: cache in Miami (MIA) · A-08

Runbook A-08 for Anycast in Miami (MIA). Marker xserv-a-22169a1a7441. This page covers cache for LATAM operators, not a worldwide average.

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: What operators should measure

Policy for Anycast is versioned as a-03. Operators measure error rate, p95 from Bogotá, and time-to-rollback — not a worldwide average. Changes land in Bogotá first, then Miami, with a hold if either region regresses.

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

Anycast policy A-03

Policy for Anycast is versioned as a-03. Operators measure error rate, p95 from Bogotá, and time-to-rollback — not a worldwide average. Changes land in Bogotá first, then Miami, with a hold if either region regresses.

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.