DDoS mitigation, inline in the traffic path

Your users connect to an address we announce, not to your server. Every packet passes our filters on the way in. Attacks are dropped and clean traffic goes on to you.

  1. 1

    Internet to our edge

    Users connect to an address we announce. Your server's real address stays hidden.

  2. 2

    Inline filtering

    Attack traffic is filtered as it arrives, all the time. You never have to switch anything on.

  3. 3

    Clean handoff

    Clean traffic goes on to your server. That is the traffic we bill you for.

Inline filtering, zero added latency

We filter in the traffic path itself. Nothing is sent on a detour to a scrubbing center and back, so mitigation adds no latency. It is full DDoS mitigation, and it is always on.

UDP attacks

UDP floods and amplification traffic are dropped at the edge, before they can fill your uplink.

TCP attacks

SYN floods, ACK floods and other TCP floods are filtered before they reach your server's connection table.

Always on

Mitigation runs from the day your service goes live. No phone call when an attack starts.

GRE or Cross-Connect

Filtering is the same either way. Pick the handoff that suits your server. Read more about DDoS protection over GRE.

GRE tunnel

A tunnel from our edge to a public IP you control. Quick to set up and works with most hosts.

The catch: a little GRE overhead, and clean traffic still uses your uplink.

Cross-Connect

A dedicated physical link to us in Equinix FR5, Frankfurt. For London or Amsterdam, ask us. No GRE overhead and the shortest path to your server.

The catch: it takes longer to order.

The customer panel

Watch attacks as they happen, set firewall and rate limit rules, and request ports. Click a screenshot to enlarge it.

Overview of your service and mitigation. Click to enlarge.

Ready to connect? Tell us your use case, peak clean traffic and which handoff you want.

Request a quote