DDoS Protection: Attacks stop at the edge.
Layer 3 to Layer 7, always on.
Mitigation is not a mode you switch on when something breaks — it runs on every request from the moment your traffic points at us. Floods are absorbed where they enter the network, and application-layer attacks are filtered request by request, so almost none of that traffic ever reaches your origin.
- L3 – L7 at our edge
- Coverage
- Always-on
- Mitigation
- None
- Attack surcharge
- Automatic
- Reaction
01What you get
Built to stay up
Protection that is already in place before anything happens — not a mode you switch on once something breaks.
Volumetric floods
Floods aimed at your site are absorbed at our edge, before they reach your uplink or your origin. Keep your origin's address private and it stays out of the line of fire.
Application-layer attacks
HTTP floods, bots and abuse are filtered request by request, so your origin spends its capacity on the people who came to use it.
Adapts on its own
Protection tightens when it has to and relaxes when it can. There is nothing to tune in the middle of an incident.
Real users first
Precision comes before force. Interrupting a real visitor is the last resort, not the default response to a busy day.
Always on
Mitigation runs on every request from the moment your traffic points at us. There is no activation delay and no switch to flip.
Live visibility
Blocks and challenges appear in your event log within seconds, and your analytics show what was served, cached and stopped.
02DDoS Protection
Priced flat, on purpose.
An attack is when you need your provider most, and when most pricing models turn against you. Ours does not move: mitigation is included on every plan, including the free one, and traffic during an attack is not billed differently from any other traffic.
- 01No per-GB or per-request attack fees
- 02Unmetered mitigation on every plan
- 03No emergency upgrade to a higher tier
- 04The bill after an attack looks like the one before it
03DDoS Protection
Built around your visitors.
Blocking a real customer is a worse outcome than letting a bot through, so the platform is built to avoid it. Attacks are taken apart at the edge with precise measures first, and a real person is only asked to verify when nothing more precise will do.
- 01Precise blocks come before any visitor check
- 02Checks are short and usually automatic
- 03API traffic is held to rate limits, not browser checks
- 04Stricter responses only when it is genuinely needed
05Further reading
The concepts behind this.
What is a DDoS attack?
A DDoS attack floods a target from many machines at once until it stops serving real users. Attack types, warning signs, real-world scale and defences.
Types of DDoS attacks: volumetric, protocol and application layer
A map of every DDoS attack type by layer: what each exhausts, its traffic signature and the defence that works. Plus multi-vector and carpet-bombing.
How to stop a DDoS attack
What to do while an attack is happening, what to do afterwards, and which common reactions make it worse. A practical sequence rather than a product pitch.
What is DDoS mitigation?
DDoS mitigation filters attack traffic while real users keep getting through. Detection, techniques compared, always-on vs on-demand, pricing and set-up.
Get started
Point your nameservers. We take the flood.
A few minutes of setup and no code changes. Protection starts as soon as your traffic points at us.
