Network
34 delivery regions, three storage regions. The list below is what we commit to in contracts; we add capacity inside a region without announcing it.
Delivery regions
| Area | Regions | Median first byte | Sustained per client |
|---|---|---|---|
| Western Europe | 6 | 18 ms | 220 Mbps |
| Central & Eastern Europe | 4 | 26 ms | 180 Mbps |
| North America (east) | 4 | 21 ms | 240 Mbps |
| North America (west) | 3 | 24 ms | 230 Mbps |
| South America | 3 | 38 ms | 120 Mbps |
| East Asia | 5 | 22 ms | 210 Mbps |
| South & Southeast Asia | 5 | 34 ms | 140 Mbps |
| Middle East | 2 | 41 ms | 110 Mbps |
| Africa | 1 | 58 ms | 80 Mbps |
| Oceania | 1 | 32 ms | 150 Mbps |
Figures are the trailing-90-day medians from client-reported telemetry, not synthetic probes. Sustained throughput is per connection on a well-provisioned last mile; your users' ISPs remain the dominant factor and we make no promises there.
Storage regions
| Region | Role | Replication lag (p99) |
|---|---|---|
| Amsterdam | Primary, control plane | — |
| Ashburn | Primary | 2.1 s |
| Singapore | Primary | 3.4 s |
An upload is acknowledged once it is durable in two regions. The third follows asynchronously; channel pointers wait for all three before they resolve, which is why a promotion takes tens of seconds rather than milliseconds.
Routing
Each delivery region has its own hostname, and that hostname resolves to the one edge
currently serving the region. When an edge leaves rotation the hostname is re-pointed
within 30 seconds — which is why clients must resolve per request and never cache
an address. Failover across regions is the client's job, and our libraries do it with a
Range header so a large download resumes rather than restarts.
Transit and peering
Multiple transit carriers in every region, and we peer selectively where it measurably helps a customer's users rather than for the sake of the port count. If you run a network with a lot of our downloads on it, write to [email protected] and we will look at a session.