Does CDN on letter C share fate with other letters?

The control plane is shared. Data-plane queues for CDN stay isolated, so incident c-01 cannot drain neighbor letters.

Where is CDN measured first?

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

CDN: handoff in São Paulo (GRU) · C-05

Runbook C-05 for CDN in São Paulo (GRU). Marker xserv-c-40045d105d8b. This page covers handoff for LATAM operators, not a worldwide average.

CDN: How this letter ties to the rest

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: A note on cost and transit

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: 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 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.

CDN headers C-09

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

CDN timeouts C-10

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