CDNs

A CDN is a named pool of edge nodes. Anywhere a URL or ASN replacement takes a destination, you can pick a CDN instead of a single node. Each redirect the gateway rewrites is then sent to one node in the pool, chosen by weight, so viewers are spread across its nodes. Nodes that are offline are skipped automatically.

Create a CDN

1. Open CDNs in the server's config section and click Edit.
2. Add CDN, give it a name, then Add node for each edge node that should be in the pool. Nodes come from this server's Edge Nodes list; both managed and external nodes work.
3. Set a weight on each node if you want an uneven split. Every node starts at 1, which is an equal share; a node with weight 3 next to one with weight 1 gets three redirects out of four.
4. Save. The share bar under each CDN shows how traffic is split.

A CDN needs at least one node. Nodes at capacity are shown but can't be added.

Using IP addresses directly

Turn on Use IP addresses directly on a CDN to type in any IPs or hostnames instead of picking edge nodes, for servers the panel doesn't manage. Such a CDN is a plain equal split: every address gets the same share, there are no weights, and nothing checks whether the hosts are up. Switching a CDN to this mode drops any weights it had.

Health

Nodes installed through the panel report in every 15 seconds. The gateway asks the dashboard for that status and leaves out any node that is offline or was never installed; its share goes to the remaining nodes. The CDN page marks such nodes as skipped and draws their slice of the bar hollow.

External nodes (your own proxy, added by IP) don't report in, so they are always used. The same goes for every address in a CDN that uses IP addresses directly.

If the dashboard can't be reached for 90 seconds, the gateway stops trusting the last status and uses every node again, so a dashboard outage never shrinks a CDN. If every node in a CDN is offline, the rule that points at it is skipped and the next priority applies.

Use it in a replacement

In URL Replacements or ASN Replacements, open the destination picker and choose the CDN from the CDNs group. The rule stores a cdn:<id> token in place of the IP, and the gateway resolves it on every redirect.

Priority is unchanged: ASN, then country, then default. If a rule's CDN has been deleted or has no nodes, that level is skipped and the next one applies, so a broken pool never produces a broken redirect.

Removing a CDN

A CDN that is still used by a rule can't be removed. Point those rules at another destination first. The gateway also rejects a config that references a CDN it doesn't know.

Notes

• The split is per redirect, not per viewer, so a viewer's next request may land on a different node.
• Requires a gateway build with CDN support. On an older build the CDNs page shows an update notice instead of the editor.