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.

How fast is rollback for c-03?

The runbook is a command plus a named owner. There is no wait for a weekly change freeze.

Is transit the default path?

No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.

A CDN that respects Spanish and Portuguese caches

Edge caches store language-correct assets near the reader so origin servers in one country are not hit for every image.

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: Failure modes we actually see

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

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 design C-01

CDN probe C-02

CDN policy C-03

CDN capacity C-04

CDN handoff C-05

CDN rollback C-06

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.

CDN regions C-11

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

CDN docs C-12

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