Does Anycast on letter A share fate with other letters?

The control plane is shared. Data-plane queues for Anycast stay isolated, so incident a-01 cannot drain neighbor letters.

Where is Anycast measured first?

From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter A.

Anycast: handoff in São Paulo (GRU) · A-77

Runbook A-77 for Anycast in São Paulo (GRU). Marker xserv-a-07e6adeccb40. This page covers handoff 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 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.