Create a CDN zone from the Deploy CDN page in my.cubepath.com. You only need a plan and a name to launch, then point it at your origin.

What a CDN zone does

A zone sits between your visitors and your origin (your web server or object storage). Requests hit the nearest point of presence (PoP) instead of your server: cached content is answered straight from the edge, and only cache misses travel back to your origin.

Two things follow from that, and they're the whole reason to use one:

  • Latency drops, because the bytes come from a PoP near the visitor rather than from a single server on one continent.
  • Origin load and bandwidth drop, because the edge absorbs the repeat traffic. A well-cached zone can serve the large majority of requests without touching your origin at all.

Deploy

  1. 1
    Select a plan
    Pick a plan based on its max origins and rules per zone; higher plans add Custom SSL. Each plan has a flat monthly price plus regional bandwidth pricing.
  2. 2
    Name your zone
    Enter a name (lowercase letters, numbers and hyphens). Your CDN domain becomes <name>.cubecdn.io.
  3. 3
    Review and deploy
    Check the summary (domain, plan, max origins, monthly price), pick your currency, then click Deploy CDN Zone.

The zone takes a few minutes to deploy across the edge. Analytics only start once it's active.

First steps after it's active

  1. 1
    Add an origin
    Go to the Origins tab and add at least one backend, otherwise the CDN has nothing to serve.
  2. 2
    Test on the zone domain
    Fetch a file through https://<name>.cubecdn.io/... and confirm it comes back correctly before you point any real traffic at it.
  3. 3
    Attach your own domain
    In Settings, set a custom domain and point a CNAME at the zone domain. SSL is issued automatically.
  4. 4
    Cache your static assets
    Add a cache rule in Rules for your images, CSS and JavaScript. This is the single change with the biggest effect on speed and cost.

The zone tabs

TabWhat it's for
OverviewRequests, bandwidth, cache hit rate and error rate for the last hour, plus a summary of origins and rules
OriginsThe backends the CDN pulls from, with health checks and private-bucket authentication
Edge RulesCaching, redirects and headers per path
WAFWho can reach the zone and how much traffic they can send
AnalyticsThe deep dive: charts and top-N tables over a time range
PricingYour plan's base price and per-GB bandwidth by region
SettingsCustom domain, SSL, signed URLs and CORS
ActivityAudit log of every change to the zone

Delete a zone

Deleting is permanent and can't be undone, so the dialog asks you to type the zone's domain to confirm. Move traffic off the domain first — once the zone is gone, requests to it stop resolving.