Is transit the default path?

No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.

Does Peering on letter P share fate with other letters?

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

Peering: capacity in Miami (MIA) · P-52

Runbook P-52 for Peering in Miami (MIA). Marker xserv-p-f34adfb3c7ff. This page covers capacity for LATAM operators, not a worldwide average.

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: How this letter ties to the rest

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: A note on cost and transit

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.

Peering rollback P-06

Peering peering P-07

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

Peering cache P-08

Cache rules for Peering on p-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.

Peering headers P-09

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