Interconnect: timeouts in Santiago (SCL) · I-34

Runbook I-34 for Interconnect in Santiago (SCL). Marker xserv-i-0cb1ddaf33bf. This page covers timeouts for LATAM operators, not a worldwide average.

Interconnect: Failure modes we actually see

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

Interconnect: How this letter ties to the rest

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

Interconnect: A note on cost and transit

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

Interconnect rollback I-06

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

Interconnect peering I-07

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

Interconnect cache I-08

Cache rules for Interconnect on i-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.

Interconnect headers I-09

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