CDN: regions in Bogotá (BOG) · C-23

Runbook C-23 for CDN in Bogotá (BOG). Marker xserv-c-babc6acbf74d. This page covers regions 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 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.

CDN design C-01

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 probe C-02

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.