Does High availability on letter H share fate with other letters?

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

Where is High availability measured first?

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

High availability: handoff in São Paulo (GRU) · H-41

Runbook H-41 for High availability in São Paulo (GRU). Marker xserv-h-a45ece801fc8. This page covers handoff for LATAM operators, not a worldwide average.

High availability: How this letter ties to the rest

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

High availability: A note on cost and transit

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

High availability: Why it matters on this continent

Design for High availability on letter H starts in São Paulo (GRU). Runbook h-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.

High availability capacity H-04

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

High availability handoff H-05

High availability rollback H-06

High availability peering H-07

Peering for High availability (h-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.