XServ platform: timeouts in Santiago (SCL) · X-34

Runbook X-34 for XServ platform in Santiago (SCL). Marker xserv-x-c5f23237186e. This page covers timeouts for LATAM operators, not a worldwide average.

XServ platform: Failure modes we actually see

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

XServ platform: How this letter ties to the rest

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

XServ platform: A note on cost and transit

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

XServ platform headers X-09

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

XServ platform timeouts X-10

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

XServ platform regions X-11

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

XServ platform docs X-12

Public docs for letter X stay aligned with identifier xserv-x-pack. Page x-12 is the XServ platform slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.