13+ Tbps
In-house stateful filtering
Ours, on our own hardware. This is the number that decides whether a protocol-aware attack gets inspected rather than merely absorbed — and it is the harder one to buy.
The network
One anycast address. 29 ways in.
Attack traffic is absorbed at whichever edge it arrives on, scrubbed there, and the clean remainder is handed to you over the tunnel you already have. Your customers keep talking to the same address throughout.
Ingress, validate, deliver
- IngressMixed traffic
Players and floods arrive together at the nearest edge.
- ValidateStateful filtering
Every packet checked against what the protocol legitimately expects.
- DeliveryClean to your edge
Over GRE, BGP or a direct cross-connect.
Scrubbing locations
29 live · 5 regions · 1 coming soon
North America
10- AshburnUnited StatesIAD
- DallasUnited StatesDFW
- ChicagoUnited StatesORD
- North Kansas CityUnited StatesMCI
- New YorkUnited StatesJFK
- Los AngelesUnited StatesLAX
- SeattleUnited StatesSEA
- MiamiUnited StatesMIA
- MontrealCanadaYUL
- VancouverCanadaYVR
Latin America
1- São PauloBrazilGRU
Europe
11- LondonUnited KingdomLHR
- AmsterdamNetherlandsAMS
- ParisFranceCDG
- FrankfurtGermanyFRA
- ZurichSwitzerlandZRH
- MilanItalyMXP
- PragueCzechiaPRG
- WarsawPolandWAW
- BucharestRomaniaOTP
- SofiaBulgariaSOF
- AthensGreeceATH
Middle East
2- IstanbulTurkeyIST
- DubaiUnited Arab EmiratesDXB
Asia Pacific
6- SingaporeSingaporeSIN
- Kuala LumpursoonMalaysiaKUL
- SeoulSouth KoreaICN
- TokyoJapanNRT
- SydneyAustraliaSYD
- AucklandNew ZealandAKL
Two numbers that do different jobs
500+ Tbps
Volumetric, via transit partners
Edge capacity for floods whose only ambition is to fill a pipe. Large, blunt attacks never reach the filtering tier at all.
Want routing options for your prefixes?
Tell us which prefixes you announce and where you terminate, and we will map them to ingress PoPs.