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.

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

Runbook C-75 for CDN in Bogotá (BOG). Marker xserv-c-720d89216d0e. 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 capacity C-04

CDN handoff C-05

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.