CDN: policy in Bogotá (BOG) · C-39

Runbook C-39 for CDN in Bogotá (BOG). Marker xserv-c-bbd3cace8c5c. This page covers policy for LATAM operators, not a worldwide average.

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