Is transit the default path?

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

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.

CDN: capacity in Miami (MIA) · C-52

Runbook C-52 for CDN in Miami (MIA). Marker xserv-c-53cc8cf88b33. This page covers capacity for LATAM operators, not a worldwide average.

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