Global CDN

275+ edge nodes.
Every corner of the earth.

When a user requests an image, it's served from the node closest to them. Processed variants are cached. Subsequent requests hit the edge, not your origin.

275+
Edge nodes
<50ms
Global median
99.99%
Uptime SLA
6
Regions
Coverage

Regional breakdown

North America

68 nodes

Median latency: 12ms

New YorkLos AngelesChicagoTorontoSeattle

Europe

82 nodes

Median latency: 9ms

FrankfurtLondonParisAmsterdamWarsaw

Asia Pacific

61 nodes

Median latency: 18ms

SingaporeTokyoSydneyMumbaiSeoul

Africa

24 nodes

Median latency: 24ms

LagosNairobiCape TownCairoAccra

South America

28 nodes

Median latency: 22ms

São PauloBuenos AiresBogotáLima

Middle East

12 nodes

Median latency: 20ms

DubaiRiyadhTel Aviv
Cache behaviour

How caching works

01

First request

Image is fetched from origin storage, processed, then served to the user. The processed variant is written to the edge cache.

02

Cache hit

Every subsequent request for the same URL + params is a cache hit. Sub-millisecond response from the edge node.

03

Purge on demand

Purge by URL, folder prefix, or tag via the API. Stale content is evicted globally within seconds.