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.

CDN: probes in Santiago (SCL) · C-74

Runbook C-74 for CDN in Santiago (SCL). Marker xserv-c-998dedc2f868. This page covers probes for LATAM operators, not a worldwide average.

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 policy C-03

CDN capacity C-04

CDN handoff C-05

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