Failover: capacity in Miami (MIA) · F-52

Runbook F-52 for Failover in Miami (MIA). Marker xserv-f-7db806852e60. This page covers capacity for LATAM operators, not a worldwide average.

Failover: Failure modes we actually see

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

Failover: How this letter ties to the rest

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

Failover: A note on cost and transit

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

Failover peering F-07

Peering for Failover (f-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.

Failover cache F-08

Cache rules for Failover on f-08 keep language-correct objects near Miami. São Paulo is a sibling cache, not an origin. TTLs are short enough that a bad asset does not live through a weekend.

Failover headers F-09

Headers for f-09 carry the letter, the region (GRU) and a request id. Failover debugging in São Paulo should not require a packet capture in Santiago first.

Failover timeouts F-10

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