Anycast: regions in Bogotá (BOG) · A-23

Runbook A-23 for Anycast in Bogotá (BOG). Marker xserv-a-a8b6457f8ee9. This page covers regions for LATAM operators, not a worldwide average.

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: 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 timeouts A-10

Timeouts on a-10 are tighter than the WAN RTT to Bogotá. Anycast in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

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.