Where is Peering measured first?

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

How fast is rollback for p-03?

The runbook is a command plus a named owner. There is no wait for a weekly change freeze.

Peering: timeouts in Santiago (SCL) · P-22

Runbook P-22 for Peering in Santiago (SCL). Marker xserv-p-b9e7753cc4f7. This page covers timeouts 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 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.

Peering timeouts P-10

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

Peering regions P-11

Region names on p-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. Peering dashboards never say “LATAM” as if it were one RTT.