CDN: design in São Paulo (GRU) · C-13

Runbook C-13 for CDN in São Paulo (GRU). Marker xserv-c-b3045ee9b379. This page covers design for LATAM operators, not a worldwide average.

CDN: Why it matters on this continent

Design for CDN on letter C starts in São Paulo (GRU). Runbook c-01 keeps a single owner, a written rollback, and a traffic split that can be reversed without a global freeze. Neighbors in Santiago only take overflow after the local pool fails a health window.

CDN: How XServ runs it day to day

Probes for CDN (c-02) leave Santiago every 15s toward Bogotá. XServ pages the named owner if loss or RTT crosses the letter budget. A probe never shares a queue with bulk transfers, so a saturated WAN does not hide a dead PoP.

CDN: What operators should measure

Policy for CDN is versioned as c-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.

CDN handoff C-05

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

CDN rollback C-06

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

CDN peering C-07

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

CDN cache C-08

Cache rules for CDN on c-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.