---
title: "Setting up a Multi-Region CDN"
description: "Edge CDN is global by default — 2,200+ locations. Learn how to configure deployments, cache rules, image optimisation, and monitoring for worldwide audiences."
url: https://edge.network/academy/multi-region-cdn/
---

# Setting up a Multi-Region CDN

[Back to Academy](https://edge.network/academy)
Featured Guide
10 min read

# Setting up a Multi-Region CDN

Edge CDN is global by default — 2,200+ locations. Unlike AWS, you don't configure regions; the network routes requests to the nearest node automatically.

## Multi-region is built in

On AWS, "multi-region" means manually provisioning CloudFront distributions, configuring origins
per region, and managing replication. [Edge CDN](https://edge.network/cdn) is global by default. A single deployment serves
from 2,200+ locations worldwide. Every user gets routed to the nearest edge node — no region
selection required.

This guide walks through creating a deployment, configuring cache rules, and monitoring
geo-distribution.

## Creating a deployment

In the Edge control panel, create a new CDN deployment. Set your origin — a VM, storage bucket,
or external URL. Add your domains; Edge provisions SSL automatically. The deployment is live
across all edge locations immediately.

**Multiple domains:** Add as many domains as you need. Each can point to the same
deployment. Useful for subdomains (e.g. `cdn.example.com`,
`assets.example.com`) or
multiple apex domains.

## How Edge routes requests

When a user requests content, Edge uses DNS and Anycast to route them to the nearest node.
That node checks its cache; on a hit, it serves the response. On a miss, it fetches from origin
and caches the response for subsequent requests.

You don't configure geography — the network handles it. Users in Tokyo, London, and São Paulo
each hit the closest node automatically.

## Cache rules for different content types

Set path-based cache rules to optimise behaviour:

- **Static assets** — `/assets/*`, `*.js`, `*.css` — long TTL (7–30 days)
- **Images** — `/images/*` — long TTL; enable image optimisation for format detection (WebP/AVIF where supported)
- **Dynamic content** — `/api/*` — short TTL or cache bypass
- **HTML pages** — short TTL (0–5 min) or bypass for personalised pages

See [Caching Strategies](https://edge.network/academy/caching-strategies)
for detailed guidance.

## Monitoring per-region performance

The control panel includes a **geo distribution** page for each CDN deployment. It
shows traffic and cache hit rates by region or country. Use it to verify that requests are
distributed globally and to identify regions where hit rates are low — a sign you may need to
adjust cache rules or TTLs for that traffic pattern.

## Image optimisation for global audiences

Edge's image optimisation automatically detects browser support for WebP and AVIF. Serve the
best format for each user — smaller files, faster loads. Particularly valuable for global
audiences on mixed devices and connections.

Enable image optimisation in the deployment settings. Use query params (e.g.
`?w=800`) for resizing;
format conversion happens automatically based on `Accept` headers.

## Dynamic content and Edge Storage as origin

For dynamic content, use short TTLs or cache bypass. Path-based rules let you exempt
`/api/*` or user-specific
paths from caching.

**Edge Storage as CDN origin:** For static sites (HTML, CSS, JS, images), use
[Edge Storage](https://edge.network/storage) as the origin. You get a truly serverless setup — no VMs, no origin management. Upload
files to storage; CDN serves them globally. Ideal for documentation sites, marketing pages, and
SPAs with static builds.

## Next steps

[Caching Strategies](https://edge.network/academy/caching-strategies) [CDN Documentation](https://edge.network/docs/cdn)