BGP Mitigation Engine | Automated FlowSpec, RTBH & Blackhole Routing | Flowtriq
Detection, Mitigation & Response

Detect and mitigate DDoS attacks in under 1 second, respond automatically, and keep your users informed.

All features →
Learn
Documentation Quick Start API Reference Agent Setup DDoS Protection Landscape State of DDoS 2026 REPORT Free Certifications NEW
Research & Guides
Mirai Botnet Kill Switch Research memcached Amplification Dynamic Baselines PCAP Forensics PagerDuty Setup
Company
About Us Partners Whitelabel / Reseller Affiliate Program Pay with Crypto System Status
Legal & Support
Contact Us Terms Privacy SLA
Who Uses Flowtriq

From indie hosts to ISPs, see how teams like yours use Flowtriq to detect and stop DDoS attacks.

Talk to Us →
Infrastructure
Hosting Providers ISPs MSPs/MSSPs Small Operators Routers Edge Node Defense
Gaming
Game Server Hosting Game Studios
Business
SaaS Platforms E-Commerce Financial Services Compliance NEW

BGP Mitigation Engine

Network-level mitigation.
Deployed in seconds.

Flowtriq detects DDoS attacks and automatically deploys BGP FlowSpec rules, RTBH blackhole routes, and rate-limiting announcements to your BGP speakers. IPv4 and IPv6 FlowSpec with VRF redirect, RPKI-validated announcements, BGP Large Communities (RFC 8092), selective per-peer blackholing, dynamic baseline thresholds, per-host overrides, automated rollback with collateral damage detection, and 8 adapter integrations including ExaBGP, GoBGP, BIRD 2, FRRouting, Cloudflare Magic Transit, Radware DefenseFlow, and F5.

< 2s
Detection to Announcement
8
Adapter Types
4
Escalation Levels
200
Max Concurrent Rules

How It Works

Attack detected. Rule deployed. Traffic mitigated. Automatically.

When Flowtriq detects a DDoS attack, the mitigation engine classifies the threat, selects the optimal response intent (rate-limit, drop specific protocol/port, or blackhole), and deploys the corresponding BGP rule to your configured adapter -- all within seconds.

Events are queued and aggregated: if multiple nodes report the same attack simultaneously, they're collapsed into a single rule. A sliding-window rate limiter prevents rule storms. When the attack subsides, rules are automatically withdrawn after their TTL expires.

The engine supports automatic escalation: a moderate flood starts with FlowSpec rate-limiting, but if traffic exceeds higher thresholds, it escalates to RTBH blackholing or upstream cloud scrubbing without manual intervention.

DispatchQueue-based with aggregation window
AdaptersExaBGP, GoBGP, BIRD 2, FRRouting, Cloudflare, Radware, F5, Webhook
ProtocolsIPv4 + IPv6 FlowSpec (RFC 5575), RTBH, VRF redirect
IntentsRate-limit, drop protocol/port, blackhole, VRF redirect, geo lockdown
CommunitiesStandard, Large (RFC 8092), per-peer selective blackholing
RPKIPre-announce validation with Cloudflare RPKI API or custom Routinator
BaselinesStatic thresholds or dynamic (weekly traffic pattern learning)
DeduplicationSame target+intent = skip (with distributed locks)
Rate limitingConfigurable max rules/minute per tenant
Rule TTLConfigurable (default 5 min), auto-expire
RollbackAuto-detect collateral damage and deploy more targeted replacement
HealthBGP session monitoring with auto-failover to backup adapter
Max rules200 concurrent per tenant, per-host threshold overrides
RetryExponential backoff for failed announcements
NotificationsEmail, Slack, Telegram on deploy/withdraw/fail/rollback
ExportPrometheus metrics, Kafka event streaming, flow mirroring
flowtriq · bgp mitigation
09:44:19 PPS=847,000 BPS=3.2 Gbps
Attack classified: UDP Amplification (NTP)
Target: 203.0.113.5 port 123

09:44:19 Evaluating escalation...
3.2 Gbps > RTBH threshold (2 Gbps)
Intent: blackhole

09:44:20 Announcing to ExaBGP...
announce route 203.0.113.5/32
  next-hop self community [65535:666]
OK rule announced (0.4s)

09:49:20 TTL expired (5 min)
Withdrawing blackhole...
OK route withdrawn
_

Escalation Policy

Four escalation levels. Zero manual intervention.

The engine automatically selects the right mitigation level based on attack volume. As attacks intensify, mitigation escalates. As they subside, less aggressive rules take over.

Local Rate-Limit

FlowSpec rate-limiting rules that throttle attack traffic without dropping legitimate packets. Applied via BGP FlowSpec to your border routers.

Default: > 100 Mbps

FlowSpec Drop

Targeted FlowSpec rules that drop specific protocols, ports, or source IPs. Surgical mitigation that preserves legitimate traffic to the target.

Default: > 500 Mbps

RTBH Blackhole

Remote Triggered Blackhole routing. Announces the target IP with community 65535:666, causing upstream routers to null-route all traffic to that IP.

Default: > 2 Gbps

Cloud Scrubbing

Diverts traffic to upstream scrubbing providers like Cloudflare Magic Transit. For volumetric attacks that exceed your local capacity.

Default: > 5 Gbps

BGP Adapters

Eight adapter types for any network architecture

Connect Flowtriq to your existing BGP infrastructure. Each adapter handles the protocol-specific details of announcing and withdrawing mitigation rules. All adapters support IPv4 and IPv6, BGP Large Communities (RFC 8092), RPKI validation, and selective per-peer blackholing.

ExaBGP

The most popular open-source BGP route injector. Flowtriq sends JSON commands over HTTP to ExaBGP's API, which announces FlowSpec and unicast routes to your routers.

  • FlowSpec rate-limiting with configurable rate values
  • Protocol-specific and port-specific drop rules
  • RTBH blackhole with community 65535:666
  • JSON API over HTTP -- no BGP session management needed
  • Full payload logged for audit trail

GoBGP

High-performance BGP implementation written in Go. Flowtriq uses GoBGP's gRPC/REST API to inject FlowSpec and unicast routes programmatically.

  • Same FlowSpec capabilities as ExaBGP
  • gRPC API for low-latency announcements
  • Built for high-throughput environments
  • Ideal for large-scale deployments with many peers
  • Supports all 4 intent types

Cloudflare

Direct integration with Cloudflare's Magic Transit API. Flowtriq announces and withdraws your /24 prefix to divert traffic through Cloudflare's global scrubbing network.

  • BGP prefix advertisement via Cloudflare API
  • On-demand scrubbing -- $0 during peacetime
  • Global anycast scrubbing network
  • Auto-withdraw on incident resolution
  • Works with Magic Transit On Demand

Webhook

Generic webhook adapter for custom integrations. Flowtriq sends structured JSON payloads to your endpoint for each announce/withdraw event, letting you integrate with any system.

  • Custom HTTP endpoint with auth token
  • Configurable headers and timeout
  • Full attack context in JSON payload
  • Build custom integrations with any network gear
  • Ideal for proprietary SDN controllers or APIs

BIRD 2

The dominant BGP daemon in European ISPs and IXPs. Flowtriq controls BIRD 2 via birdc socket proxy, supporting native flow specification syntax for FlowSpec and static blackhole routes.

  • Native BIRD 2 flow specification syntax
  • IPv4 and IPv6 FlowSpec + unicast blackhole
  • BGP Large Communities via bgp_large_community
  • birdc socket proxy API for real-time control
  • Ideal for European ISPs and IXP members

FRRouting (FRR)

The leading open-source routing suite for whitebox switches and SONiC deployments. Flowtriq pushes vtysh commands via proxy API for static blackhole routes, ACL-based FlowSpec, and route-maps.

  • vtysh command proxy for real-time configuration
  • Static blackhole routes with tag-based community tagging
  • Policy-based routing for FlowSpec-like filtering
  • Standard and Large Communities via route-maps
  • Ideal for whitebox, SONiC, and data center fabrics

Radware DefenseFlow

Enterprise scrubbing appliance integration. Flowtriq creates and removes protection policies on Radware DefenseFlow via REST API for automated traffic diversion and scrubbing.

  • Create/remove protection policies via REST API
  • Divert or drop actions per target IP
  • Automatic policy cleanup on attack resolution
  • Ideal for enterprise networks with Radware appliances

F5 DDoS

Enterprise DDoS appliance integration. Flowtriq manages DoS profiles on F5 BIG-IP via iControl REST API for automated scrubbing and traffic filtering.

  • DoS profile management via iControl REST
  • Protocol and port-specific scrubbing
  • Configurable partitions for multi-tenant F5
  • Automatic profile cleanup on attack resolution

Event Pipeline

Queue-based dispatch with built-in safety guards

Every attack event goes through a multi-stage pipeline before a BGP rule is announced. This prevents rule storms, duplicate announcements, and ensures the right level of mitigation is applied.

1. Event Queue

Attack events from all nodes are queued with priority scores based on severity (critical=90, high=70, medium=50, low=30).

mitigation_event_queue

2. Aggregation

Events targeting the same IP+protocol+port+family within the aggregation window are collapsed into a single record. Multi-node attacks = one rule.

Default: 5-second window

3. Validation & Intent

Target IP is validated (public IPv4 only, no private/reserved ranges). Attack type determines the intent: rate-limit, drop protocol, drop port, or blackhole.

Private IPs rejected · /24 minimum prefix

4. Escalation

Attack bandwidth determines the escalation level. Exceeding higher thresholds automatically upgrades the intent from rate-limiting to blackhole.

4 configurable thresholds

5. Rate Limiting

Sliding-window rate limiter ensures no more than N rules per minute per tenant. Prevents rule storms during distributed attacks.

Default: 30 rules/min

6. Announce

The BGP rule is dispatched to the best available adapter (scored by capability match and test status). Full payload is logged for audit.

Adapter scoring · Auto-retry on failure

Comparison

Manual BGP mitigation vs. Flowtriq

Manual / Script-Based

  • SSH into router, manually type BGP commands
  • Minutes to hours response time at 3 AM
  • No aggregation -- duplicate rules from multiple alerts
  • Forget to withdraw? Blackhole persists for hours
  • No escalation -- same response for 100 Mbps and 10 Gbps
  • No audit trail of what was announced and when
  • No rate limiting -- script storms can overwhelm routers

Flowtriq BGP Mitigation

  • Detect attack, classify, announce rule -- all automatic
  • Sub-2-second response time, 24/7
  • Event aggregation collapses multi-node attacks into one rule
  • TTL-based auto-expiry withdraws rules automatically
  • 4-level escalation from rate-limit to cloud scrubbing
  • Every announce/withdraw logged with full adapter payload
  • Sliding-window rate limiter prevents rule storms

FAQ

Common questions

What BGP speakers do I need?

Flowtriq works with any BGP speaker that exposes an API for route injection. The built-in adapters support ExaBGP (JSON/HTTP API) and GoBGP (gRPC/REST API). For other BGP implementations, use the webhook adapter to receive structured JSON payloads and translate them into your speaker's native format.

Does the engine support IPv6?

The current engine validates and mitigates IPv4 targets only. IPv6 FlowSpec support is on the roadmap. For IPv6 attacks, use firewall rules or cloud scrubbing integrations.

What happens if my adapter goes offline?

Failed announcements are retried with exponential backoff by the lifecycle cron job (runs every minute). The adapter's last test status is tracked, and the engine scores adapters by health -- if you have multiple adapters, it prefers the one that passed its last connectivity test.

Can I create rules manually?

Yes. The Manual Rule tab in the dashboard lets you create BGP rules on demand -- specify the target IP, intent type, protocol, port, rate limit, TTL, and escalation level. Useful for pre-emptive mitigation or testing your adapter setup.

How does this relate to cloud scrubbing?

BGP mitigation and cloud scrubbing are complementary. BGP FlowSpec/RTBH handles mitigation at your network edge (your routers), while cloud scrubbing diverts traffic upstream before it reaches your infrastructure. Flowtriq's escalation policy can automatically escalate from BGP to cloud scrubbing when attack volume exceeds your link capacity.

What safety guards are in place?

Multiple layers: private/reserved IPs are rejected, /24 is the minimum prefix, rate limiting caps rules per minute, cooldown periods prevent flapping, a global cap of 200 active rules prevents runaway scenarios, and all operations use distributed MySQL locks to prevent duplicate announcements even in multi-process deployments.

Deploy network-level mitigation in minutes

Connect your BGP speakers, configure escalation thresholds, and let Flowtriq handle the rest. Free 7-day trial, no credit card required.

Start Free Trial Read the Docs