Your whole network, behind one gate.

Network Protection moves traffic for your IP prefixes through SentiGate with BGP. Floods get scrubbed at layers 3 to 5, and clean traffic comes back to your routers over GRE or a direct link. This protects every service on those addresses, from game servers to VPN gateways.

L3L4L5BGPGRE/24 and up
Attack report · AS64500Example
0255014:0014:1014:2014:30Gbps 48.2 Gbps peak Arriving at SentiGate Delivered to you
Peak48.2 Gbps
Packet rate6.1 Mpps
VectorsUDP, DNS amp
Absorbed at4 gates
Example attack report for prefix 203.0.113.0/24.
How it works

What happens when your prefix is attacked.

Scroll down to follow a typical attack on an example network, AS64500 with the prefix 203.0.113.0/24, from start to finish.

AS64500 · 203.0.113.0/24Example
Internet Users Botnet SentiGate 11 gates Your ISP AS64500 203.0.113.0/24 All good Link full Rerouting Clean only Announce /24 GRE Return Routes withdrawn
01 Normal day. Traffic flows through your ISP.
  1. 01 · Quiet

    A normal morning

    In on-demand mode your prefix is announced by your own upstreams, and SentiGate stays on standby. In always-on mode, traffic already flows through our gates every day, so the flood in step 2 never reaches your uplink and nothing needs to reroute.

  2. 02 · Attack

    The flood shows up

    An attacker sends 48 Gbps of UDP at a game server on 203.0.113.14. Your 10 Gbps uplink fills up in seconds, and every service on the prefix suffers, including the ones nobody was targeting.

  3. 03 · Reroute

    Your prefix moves to SentiGate

    The switch starts automatically based on your flow data, or after one message to our NOC. Your routers stop announcing 203.0.113.0/24 to your upstreams and we announce it from all 11 gates, so the internet starts sending that traffic to us.

  4. 04 · Scrub

    The flood hits the gates

    Anycast splits the attack across sites close to its sources. Spoofed packets, amplification traffic, malformed packets and SYN floods get dropped at layers 3 to 5, while real traffic keeps going.

  5. 05 · Deliver

    Clean traffic comes home

    What’s left reaches your border router through a GRE tunnel or a direct cross-connect. Replies leave through your own ISP as usual, so your outbound path doesn’t change.

  6. 06 · Quiet again

    And back to normal

    When the attack is over and you’re happy with how things look, the announcement is withdrawn and traffic goes back to your upstreams. You get a report of everything that happened.

Modes

Always-on or on-demand.

Both modes use the same gates and the same filters. The difference is whether your traffic passes through us every day or only when it needs to.

Always-on

No switchover

Your prefixes are announced from SentiGate all the time. Every packet passes through the gates, so an attack meets filters that are already running and there’s nothing to reroute.

Best for networks that get hit often: game hosting, VPN providers, hosting companies and other frequent targets.

On-demand

Switch when needed

Traffic uses your own upstreams on a normal day. When an attack starts, the prefix moves to SentiGate automatically based on your flow data, or when you ask, and goes back once it’s over.

Best for networks that rarely see attacks and want their everyday traffic to take the most direct path.

Delivery

Two ways to get clean traffic back.

Pick whichever fits your network. Some customers use both, with a cross-connect where we share a building and GRE everywhere else.

GRE tunnels

This works over the internet with almost any router. We set up tunnels from several gates to your border, so clean traffic has more than one way home. We’ll help you get MTU and MSS right, since tunnels add a few bytes to every packet.

Direct cross-connect

If your equipment sits in a facility where we have a gate, we can run a physical link between our routers and yours. There’s no tunnel overhead, and the path for clean traffic is very short.

Layer 3

Network

ICMP floods, IP fragmentation attacks, spoofed and bogon sources, GRE and other protocol floods, carpet bombing across a whole prefix.

Layer 4

Transport

SYN, ACK, RST and FIN floods, UDP floods, reflection and amplification from DNS, NTP, memcached, SSDP, CLDAP and similar protocols, TCP state exhaustion.

Layer 5

Session

TLS handshake floods, connection and session exhaustion, slow connection attacks that try to keep every socket on your servers busy.

The full list is in the attack coverage section.

Before you start

What you’ll need.

None of this is unusual. If you run your own prefixes, you probably have most of it already, and we’ll help with the rest.

  • An IPv4 prefix of /24 or larger. That’s the smallest block most networks accept on the global routing table.
  • Permission to announce it. A Letter of Authorization for us, route objects in the IRR, and an RPKI ROA that lets our ASN originate your prefix. We’ll help with all three.
  • A way to receive clean traffic. A router that can terminate GRE tunnels, or space in a facility where we can cross-connect.
  • Flow export for on-demand mode. NetFlow, sFlow or IPFIX from your edge, so an attack can trigger the switch automatically.
  • An hour with our engineers. We’ll go through your setup, test the tunnels and agree on what happens when an attack starts.
FAQ

The questions network people ask.

If you have a more unusual question, send it to us. Our engineers like those.

What’s the smallest prefix you can protect?

A /24 for IPv4. Most networks on the internet filter out anything smaller, so a /25 announced through us wouldn’t propagate and traffic would keep taking its normal path.

Will latency go up?

Usually by very little. Traffic enters the nearest of our 11 gates and then travels to you over a tunnel or cross-connect. With on-demand mode, your everyday traffic doesn’t pass through us at all.

Do you protect just one server or IP?

Network Protection works on whole prefixes. If you need to protect a website or an API on a single address, Web App & API Protection is the better fit.

Can I set different rules for different hosts?

Yes. Policies can be set per prefix and per host, so a game server, a mail server and a VPN gateway in the same /24 each get filters that fit their traffic.

How do I see what happened during an attack?

Every attack gets a report: when it started and ended, peak bandwidth and packet rate, attack vectors, which gates absorbed it and how much clean traffic reached you.

Let’s look at your network.

Tell us about your network and how often it gets hit, and we’ll suggest a mode and send a quote.

Under attack

Let’s get you behind the gate.

This is what happens next.

  1. Write to our NOC. Put “URGENT” in the subject and tell us what’s being hit: a domain, an IP or a whole prefix, and roughly when it started.
  2. An engineer replies with a plan. For a website this is a DNS change and usually a new origin IP that the attackers don’t know yet. For a network it’s a Letter of Authorization, route objects and a GRE tunnel, so we can announce your prefix from our edge.
  3. The flood hits our gates instead of you. Once traffic flows through SentiGate, we tune the filters with you while the attack is still going.
noc@sentigate.cloud
Write to the NOC

Quick tip: if you run your own DNS, check the TTL on the record you’ll be changing. The shorter it is, the faster the switch to SentiGate takes effect.