Network
Where the bytes come from
Every facility we light up is listed here, with its capacity, its transit mix and the exchanges it peers at. No 'up to' numbers.
Points of presence
Green means the site is taking traffic right now.
40 points of presenceprivate backbone, 61 sites
| Location | Region | Capacity | p50 RTT | Status |
|---|---|---|---|---|
| Ashburn US | us-east | 3200 Gbps | 4.9 ms | degraded |
| Bangkok TH | ap-southeast | 200 Gbps | 17.1 ms | healthy |
| Bucharest RO | eu-east | 800 Gbps | 30.6 ms | healthy |
| Buenos Aires AR | sa-south | 400 Gbps | 13.8 ms | degraded |
| Cairo EG | af-north | 3200 Gbps | 3.1 ms | healthy |
| Chennai IN | ap-south | 1600 Gbps | 13.7 ms | healthy |
| Chicago US | us-central | 400 Gbps | 12.2 ms | healthy |
| Dallas US | us-central | 3200 Gbps | 26.6 ms | degraded |
| Delhi IN | ap-north | 1600 Gbps | 6.0 ms | degraded |
| Denver US | us-central | 400 Gbps | 30.1 ms | healthy |
| Dubai AE | me-south | 3200 Gbps | 21.8 ms | healthy |
| Dublin IE | eu-west | 3200 Gbps | 22.6 ms | degraded |
| Frankfurt DE | eu-central | 400 Gbps | 13.2 ms | healthy |
| Helsinki FI | eu-north | 400 Gbps | 32.7 ms | degraded |
214Tbps
installed capacity
480
IXP sessions
6
transit providers
38.6%
traffic over IPv6
Topology
Three tiers, one address
Clients always hit the anycast address. What happens behind it is the interesting part.
- Edge tier holds the hot set on NVMe, roughly 340 TB per large site
- Shield tier keeps a full regional copy on spinning disk
- Origin sees one fetch per region per object, not one per client
Peering policy
We peer openly. If you run a network and we are at the same exchange, send a request and we will bring the session up.
| Exchange | Location | Peering since | Port | Policy |
|---|---|---|---|---|
| DE-CIX | Frankfurt | 2018 | 3.2 Tbps | open |
| AMS-IX | Amsterdam | 2018 | 2.4 Tbps | open |
| LINX | London | 2019 | 1.6 Tbps | open |
| Equinix IX | Ashburn | 2020 | 2.0 Tbps | open |
| SIX | Seattle | 2021 | 800 Gbps | open |
| JPIX | Tokyo | 2022 | 1.2 Tbps | open |
| SGIX | Singapore | 2022 | 1.6 Tbps | open |
| IX.br | São Paulo | 2023 | 900 Gbps | selective |
Network questions
Our IRR objects are in RIPE, every prefix we originate carries an RPKI ROA, and the peering contacts are in PeeringDB.
Yes — strict prefix filtering built from IRR plus RPKI, rebuilt every four hours. Invalid announcements are dropped, not de-preferenced.
Volumetric attacks are absorbed at the edge because the edge is the capacity. Anything the scrubbing rules cannot classify gets rate-limited per source AS rather than blackholed.