How it works

From an attack to clean traffic.

Protect on demand: a BGP session kept ready, your announcement during an attack, our filtering, your withdrawal.

Example addresses on this page use documentation ranges (RFC 5737, RFC 5398).

Before

Getting ready

  1. We set up the link and the BGP session, and check your route objects and ROAs.

  2. You're ready. During the next attack, you announce; we filter.

During

The attack stays on top of the sieve.

  1. 01

    During an attack, you announce the affected prefixes to us.

  2. 02

    Traffic for those prefixes arrives at our edge, and attack traffic stops there.

  3. 03

    We filter the attack and deliver the clean traffic back over your link.

  4. 04

    When it's over, you withdraw.

Fig. 1 · Traffic pathAS208355
Traffic path: the internet, our edge, filtering, then your network over a cross-connect.
You need

Requirements

  • Your own ASN.
  • Prefixes of /24 or larger, with valid ROAs and route objects.