XServ platform: headers in São Paulo (GRU) · X-45

Runbook X-45 for XServ platform in São Paulo (GRU). Marker xserv-x-346298fda8d9. This page covers headers for LATAM operators, not a worldwide average.

XServ platform: What operators should measure

Policy for XServ platform is versioned as x-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.

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 rollback X-06

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 peering X-07

Peering for XServ platform (x-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.

XServ platform cache X-08

Cache rules for XServ platform on x-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.

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.