https://upcloud.com/docs/products/cdn/Recent content in Content Delivery Network (CDN) on DocumentationHugo -- gohugo.ioenhello@upcloud.com (UpCloud)hello@upcloud.com (UpCloud)© 2024 UpCloudWed, 07 Oct 2026 07:39:48 +0000https://upcloud.com/docs/products/cdn/availability/Wed, 07 Oct 2026 07:39:48 +0000hello@upcloud.com (UpCloud)https://upcloud.com/docs/products/cdn/availability/ UpCloud CDN is not tied to a single UpCloud zone. Content is served from a global edge network of more than 120 points of presence (PoPs), and every CDN you create is available in all of them by default. Edge regions The edge network is divided into five regions. Each region is also a pricing zone, so enabling or disabling a region changes both where your content is served from and what you pay. Region Europe North America Asia & Oceania South America Middle East & Africa All regions are enabled when a CDN is created. You can disable a region at any time from the Pricing zones section of the CDN's Overview tab. Visitors in a disabled region are routed to the nearest enabled region instead, which lowers cost for that traffic at the expense of latency. Origins The origin can be in any UpCloud zone or outside UpCloud entirely. See Origins and caching for the supported origin types. Tiers The Standard tier serves from all 120+ PoPs. The High Volume tier is enabled by sales for large file and video workloads. See Configurations.https://upcloud.com/docs/products/cdn/configurations/Wed, 07 Oct 2026 07:39:48 +0000hello@upcloud.com (UpCloud)https://upcloud.com/docs/products/cdn/configurations/ Standard tier The Standard tier is available to all customers and is selected by default when you create a CDN. It serves content from all 120+ edge locations and is optimized for low latency, which suits websites, ads, and small files. Standard tier CDNs are capped at 100 TB of delivered bandwidth per month. High Volume tier The High Volume tier is optimized for large files and high-bandwidth video delivery, where throughput matters more than per-request latency. It is not self-service. Contact sales to enable it. Monthly bandwidth limit Every CDN has a monthly bandwidth limit, set from the Monthly bandwidth limit section of the Overview tab. When the limit is reached, the CDN stops serving until the next billing cycle begins. Use it to put a hard ceiling on cost. On the Standard tier the limit can be set anywhere up to the 100 TB cap. Contact sales if you need more. Tier Availability Best for Monthly cap Standard Self-service Websites, ads, small files 100 TB High Volume Via sales Large files, video Contact saleshttps://upcloud.com/docs/products/cdn/billing/Wed, 07 Oct 2026 07:39:48 +0000hello@upcloud.com (UpCloud)https://upcloud.com/docs/products/cdn/billing/ UpCloud CDN is billed on the bandwidth it delivers to visitors. There is no fixed monthly fee for a CDN, and you only pay for the gigabytes served from the edge. How it works Billing is per gigabyte of bandwidth delivered from the CDN edge to visitors. The rate depends on the region the content is served from. Each of the five edge regions is a separate pricing zone with its own rate. Requests that are fetched from your origin are not billed separately. Standard UpCloud zero-cost egress applies to traffic leaving your UpCloud origin. CDN is billed in USD. The EUR amounts shown in the Control Panel are estimates based on the current exchange rate. Please refer to our pricing page for current rates in your currency. Pricing zones The pricing zones are Europe, North America, Asia & Oceania, South America, and Middle East & Africa. All are enabled by default. Disabling a zone routes visitors in that region to the nearest enabled zone, so you can trade latency for a lower rate on traffic from more expensive regions. See Availability. Monthly bandwidth limit Each CDN has a monthly bandwidth limit that disables the CDN for the rest of the billing cycle once it is reached. This is the simplest way to guarantee an upper bound on CDN cost. See Configurations. Usage reporting The Usage tab of each CDN shows month-to-date bandwidth, request count, and the estimated bandwidth price. These figures come from the billing system, are refreshed every 10 minutes, and match what appears on your end-of-month invoice. Detailed traffic statistics are collected with a delay of about an hour and are kept for 365 days. If you have any questions about pricing, please contact our Support team.https://upcloud.com/docs/products/cdn/origins-and-caching/Wed, 07 Oct 2026 07:39:48 +0000hello@upcloud.com (UpCloud)https://upcloud.com/docs/products/cdn/origins-and-caching/ The origin is the source of your content. When a visitor requests a file, the CDN fetches it from the origin, caches it at the edge, and serves the cached copy to later requests. Origin types Origin URL. Use when your content is on a server outside UpCloud, or to point at a specific URL. Configured with any public URL, including http:// or https://. Object Storage. Use when your content is in one or more UpCloud Managed Object Storage buckets. The instance is picked from a list and the origin URL is set to the instance endpoint. See Object Storage origins below. Load Balancer. Use when your content is behind an UpCloud Managed Load Balancer. The load balancer is picked from a list and the origin URL is set to its hostname. Server. Use when your content is served directly by an UpCloud Cloud Server. The server is picked from a list and the origin URL is set to its public IPv4 address over http://. The origin type and URL can be changed after creation from the Origin type section of the Overview tab. Changing the origin does not clear content already cached at the edge, so purge the cache afterwards. Object Storage origins With the Object Storage origin type, the origin is the instance endpoint rather than a bucket. The CDN passes the request path straight through, so the bucket name is the first segment of every CDN URL: CDN request Fetched from origin /my-bucket/image.jpg objects.example.com/my-bucket/image.jpg /image.jpg (no bucket) No such bucket, returns 404 All public buckets on the instance are reachable this way through one CDN hostname. Objects must be publicly readable, through the bucket's anonymous HTTPS access setting or a bucket policy. Requests for private objects return the origin's 403 to the visitor. Bucket listings are not served. To serve a single bucket at the root of the CDN hostname, use the Origin URL type with the bucket's virtual-host address, for example https://my-bucket.objects.example.com. The CDN then maps /image.jpg directly to that bucket. Origin settings Setting Default What it does Host header Empty The Host header sent to the origin. When empty, the hostname from the origin URL is used. Set it when the origin serves several sites by hostname, for example when the origin URL is an IP address. Origin connect timeout 10s How long the edge waits to open a connection to the origin. Origin response timeout 60s How long the edge waits for the origin to respond once connected. Increase it for slow origins or very large files. Follow redirects Off When on, the edge follows redirects returned by the origin and caches the final response. When off, the redirect is passed to the visitor. Forward Host header Off When on, the edge forwards the hostname the visitor requested, such as cdn.example.com, instead of the origin's own hostname. Retry failed requests Off When on, the edge retries the origin once if the first attempt fails. Caching Setting Default What it does Smart Cache On Caches static files such as images, video, stylesheets, and scripts. Dynamic responses, including HTML, are never cached. Cache-Control headers from the origin are respected. Query string ordering On Sorts query parameters into a fixed order before caching, so ?a=1&b=2 and ?b=2&a=1 share one cache entry. Cache lifetimes can be overridden per path with edge rules. Purging the cache Purge cache removes every cached object for a CDN from all edge locations. The next request for each file is fetched from the origin again. Purging is global, cannot be undone, and causes a short increase in origin load while the cache refills. Cached copies are served until they expire or are purged, regardless of changes at the origin. Purge after revoking public access to content or switching the origin, or the old copies keep being served.https://upcloud.com/docs/products/cdn/hostnames-and-ssl/Wed, 07 Oct 2026 07:39:48 +0000hello@upcloud.com (UpCloud)https://upcloud.com/docs/products/cdn/hostnames-and-ssl/ Default hostname Every CDN gets a hostname of the form prefix.b-cdn.net, where the prefix is chosen at creation. It is marked Main in the hostname list, has SSL enabled from the start, and cannot be removed. Custom hostnames You can add any number of custom hostnames, such as cdn.example.com, so that visitors see your own domain. Each custom hostname needs a CNAME record at your DNS provider pointing at the default b-cdn.net hostname. The hostname shows as CNAME missing until the record is found, and becomes Active once it is verified. For the step-by-step flow, see How to get started with UpCloud CDN. Root domains are not supported Root domains such as example.com are not supported as custom hostnames, including with CNAME flattening at your DNS provider. Use a subdomain such as cdn.example.com or www.example.com, and redirect the root domain to it. DNS proxies If your DNS provider proxies traffic, such as Cloudflare's proxy mode, disable it for the CDN record. A proxied record does not resolve to the CNAME target, so verification fails. SSL certificates Once a custom hostname is verified, you can enable SSL for it in one of two ways. Option What it does Free SSL A Let's Encrypt certificate is issued for the hostname and renewed automatically. The hostname shows Provisioning for a short while, then Enabled. Manual certificate Upload or paste your own PEM-encoded certificate and private key. Renewal is your responsibility. Force SSL Each hostname has a Force SSL toggle. When on, HTTP requests to that hostname are redirected to HTTPS. It is off by default, including on the main hostname. The same redirect can be applied to specific paths only with an edge rule.https://upcloud.com/docs/products/cdn/edge-rules/Wed, 07 Oct 2026 07:39:48 +0000hello@upcloud.com (UpCloud)https://upcloud.com/docs/products/cdn/edge-rules/ Edge rules change how the CDN handles requests that match a condition, before they reach the cache or the origin. Each rule has a trigger, one or more patterns, and an action. Rules are managed from the Edge rules tab of a CDN. Rule structure Part What it does Enable Rule On by default. Turn it off to save the rule as a draft without activating it. Trigger type What the rule inspects. See the trigger list below. Pattern matching Match any: the rule fires if any pattern matches. Match all: every pattern must match. Match none: the rule fires only when no pattern matches. Patterns One or more values to compare against. * is a wildcard. Action What happens when the trigger matches. See the action list below. Description Optional note for your own reference. Trigger types Trigger Matches against Example pattern URL The full request URL. */images/* URL extension The file extension of the requested path. jpg Request header A header sent by the visitor. Header name and value pattern. Country code The two-letter country code of the visitor's IP address. DE Remote IP The visitor's IP address. 203.0.113.0/24 Actions Action What it does Redirect Sends the visitor to another URL with a status code of 301, 302, 307, or 308. The redirect URL can include variables. Override edge cache time Sets how long the edge keeps the matching content, overriding the origin's Cache-Control. The browser cache time is set to the same value unless an Override browser cache time rule also matches. Applies to content fetched after the rule is created. Override browser cache time Sets the Cache-Control max-age sent to the visitor's browser. Force SSL Redirects matching HTTP requests to HTTPS. Block request Denies the request. Set response header Adds or overrides a header on the response sent to the visitor. Set request header Adds or overrides a header on the request sent to the origin. Ignore query string Treats URLs with different query strings as the same cached object. Variables Redirect URLs and header values can include variables that are replaced per request. Variable Value %{Request.Method} HTTP method %{Request.Path} Full request path including query string %{Request.QueryString} Query string only %{Url.Hostname} Host portion of the URL %{Url.Directory} Directory portion of the path %{Url.FileName} Filename without extension %{Url.Extension} File extension %{Path.0}, %{Path.0-2}, %{Path.3-}, %{Path.-1} Path segments by index, range, or from the end %{Query.name} Value of the name query parameter %{RequestHeaders.Name} Value of a request header, for example %{RequestHeaders.User-Agent} %{User.IP} Visitor IP address %{User.CountryCode} Visitor country code %{Server.ZoneCode} Edge zone serving the request %{Server.ID} Edge server identifier For worked examples, see How to get started with UpCloud CDN.https://upcloud.com/docs/products/cdn/security/Wed, 07 Oct 2026 07:39:48 +0000hello@upcloud.com (UpCloud)https://upcloud.com/docs/products/cdn/security/ Security settings are managed from the Security tab of a CDN. Request blocking by country or IP address is available through edge rules. CORS headers When enabled, the CDN adds Access-Control-Allow-Origin: * to responses, which lets pages on other domains load your CDN assets. This is required for web fonts and for scripts that fetch data across origins. An Allowed file extensions list limits which files receive the header. The default list covers fonts (eot, ttf, woff, woff2), css, js, images (jpg, jpeg, png, webp, gif, svg), and media (mp3, mp4, mpeg, webm). An empty list applies the header to every response. Hotlink protection Hotlink protection controls which websites can embed your content, based on the Referer header the browser sends. Setting What it does Allowed referrers Hostnames that may embed your content. When the list is empty, all referrers are allowed. Blocked referrers Hostnames that are always denied, even if they would otherwise be allowed. Block requests with no referrer When on, requests without a Referer header are denied. Direct links, some privacy-focused browsers, and many API clients send no referrer, so enable this with care.https://upcloud.com/docs/products/cdn/limitations/Wed, 07 Oct 2026 07:39:48 +0000hello@upcloud.com (UpCloud)https://upcloud.com/docs/products/cdn/limitations/ Beta service UpCloud CDN is in beta. It is fully functional, but standard UpCloud SLAs do not apply during the beta period, and features, limits, and pricing may change before general availability. Control Panel only CDN can be managed only through the UpCloud Control Panel. There is no UpCloud API, upctl, or Terraform support yet. Root domains as custom hostnames Root domains such as example.com are not supported as custom hostnames. Use a subdomain and redirect the root domain to it. See Hostnames and SSL. HTML is never cached Smart Cache caches static assets only. Dynamic responses, including HTML pages, are always fetched from the origin. Cache lifetimes for specific paths can be overridden with edge rules. Bandwidth cap Standard tier CDNs are capped at 100 TB of delivered bandwidth per month. Contact sales for higher volumes. See Configurations. Origin requirements Object Storage origins point at the instance, so the bucket name is part of every CDN path and objects must be publicly readable. See Origins and caching. Server origins are configured over plain HTTP to the server's public IPv4 address. A server that serves HTTPS only, or several sites by hostname, should be configured as an Origin URL with a host header instead.