Peering: cache in Miami (MIA) · P-56

Runbook P-56 for Peering in Miami (MIA). Marker xserv-p-3fdab96c11a7. This page covers cache for LATAM operators, not a worldwide average.

Peering: How XServ runs it day to day

Probes for Peering (p-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.

Peering: What operators should measure

Policy for Peering is versioned as p-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.

Peering: Failure modes we actually see

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

Peering policy P-03

Policy for Peering is versioned as p-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.

Peering capacity P-04

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

Peering handoff P-05

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

Peering rollback P-06

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