Zipzy CDN
Status Get started
Support center

Getting started with Zipzy CDN

Point a hostname at us, set cache headers on your origin, done. This page covers setup, caching behaviour, response headers, rate limits and the origin API. Questions we haven't answered here go in the FAQ or straight to contact.

Getting started

Create a CNAME record pointing your subdomain at your assigned edge hostname:

static.example.com.  CNAME  edge.zipzy-cdn.net.

Once DNS propagates (usually within minutes), requests to static.example.com are served from the nearest edge node and pulled from your origin on a cache miss. There's no activation step on our side — the first request provisions the cache.

Caching rules

We respect standard HTTP caching headers from your origin — nothing exotic:

Cache-Control: max-age

Honoured as-is. Edge nodes will not serve stale content past the given TTL, even under origin outage.

Cache-Control: no-store

Bypasses the edge cache entirely — every request is proxied straight to origin.

ETag / Last-Modified

Used for conditional revalidation on cache expiry, before falling back to a full re-fetch.

Vary

Supported for a small allow-list of headers (Accept-Encoding, Accept).

Every response we serve also carries a couple of headers of our own:

X-Zipzy-Cache: HIT
X-Zipzy-Node: fra-edge-01
X-Zipzy-Age: 412

Origin API reference

A minimal API for cache management. All requests require an API key issued from your account.

Purge a path

POST /v1/purge
Authorization: Bearer <api_key>
Content-Type: application/json

{
  "paths": ["/downloads/build-142.zip"]
}

Purge everything under a prefix

POST /v1/purge
Authorization: Bearer <api_key>
Content-Type: application/json

{
  "prefix": "/downloads/"
}

Node health

GET /v1/health

200 OK
{
  "status": "operational",
  "nodes": 6,
  "region": "eu-central"
}
Rate limit: 60 requests/minute per API key on /v1/purge, 600 requests/minute on /v1/health.

Changelog

2026-07-20

Vary header support

Added support for a small allow-list of Vary headers.

2026-06-04

HTTP/3 by default

Enabled on all edge nodes without any configuration required on the customer side.

2026-04-11

Prefix-based purge

The origin API can now purge everything under a path prefix, not just individual files.

2026-02-02

Helsinki node added

Brought hel-edge-01 into rotation to reduce latency for Nordic traffic.

Still stuck?

Check the FAQ or reach a human directly.

Contact us