Edge network
Regions
Fourteen regions render and cache images. A request goes to the nearest healthy one; the region that answered is named in the x-px-lane response header.
Europe 5 regions
eu-1Amsterdameu-2Frankfurteu-3Warsaweu-4Stockholmeu-5Madrid
North America 4 regions
na-1Ashburnna-2Dallasna-3San Josena-4Toronto
Asia 3 regions
asia-1Singaporeasia-2Tokyoasia-3Mumbai
South America & Oceania 2 regions
sa-1São Paulooc-1Sydney
How a request finds its lane
1. Nearest region
DNS answers with the region closest to the resolver. Regions that fail two consecutive health checks are withdrawn within 20 seconds.
2. Local cache
Each region keeps its own cache of rendered variants on NVMe. A hit never leaves the building: median time to first byte is 11 ms.
3. Render on miss
On a miss the region fetches your original (once, then keeps it for 24 hours), renders the variant, stores it, and answers.
Pinning and data residency
By default originals are cached in whichever regions receive traffic for them. If your originals must stay in one jurisdiction, ask us to pin your host to a group: eu, na or apac. Requests from elsewhere are still served, from the pinned group, a little slower.
Region codes are stable. We add regions; we have never renumbered one.