Anti-DDoS technology built for production networks

Peeryx Network places filtering servers at the network edge, on points of presence designed to receive traffic before it reaches the protected infrastructure. Traffic crosses the mitigation layer in bridge mode, which enables filtering without imposing heavy application logic or unnecessary complexity on the customer side.

This model protects many use cases: protected IP transit, BGP prefixes, GRE/IPIP/VXLAN tunnels, gaming reverse proxy, dedicated servers and sensitive infrastructure.

Peeryx uses DPDK-based packet processing in its mitigation architecture. Performance depends on the deployed software, enabled rules, packet sizes and traffic distribution.

CPU, NIC, PCIe bandwidth, NUMA placement and receive queues all constrain forwarding. A port speed or a processor core count does not establish a server’s filtering capacity. Validate Gbps and Mpps together with representative packets, legitimate traffic, enabled features and an explicit packet-loss limit. Historical network telemetry is not a reproducible per-server benchmark.

Overly generic Anti-DDoS filtering can block players, break real-time applications or disrupt business protocols. Peeryx uses behavioral analysis: used ports, protocols, usual volumes, packet sizes, destinations and normal service variations.

When an attack starts, mitigation compares incoming traffic with the expected behavior. Rules are adjusted to block enough of the attack while preserving useful traffic, even when the attacker tries to imitate part of the legitimate traffic.

Peeryx combines upstream transit and local filtering. Resilience depends on independent, working paths and on the capacity remaining after a failure; planned points of presence are not additional live capacity.

The announced 15 Tbps+ refers to capacity available through upstream providers. It is shared network capacity, not a dedicated customer reservation or a measure of locally owned filtering. Customer port limits, the clean handoff and upstream mitigation policies still apply.

When an attack is detected, Peeryx can automatically generate BGP FlowSpec rules that target the observed characteristics: protocol, ports, TCP flags, packet lengths or impacted destinations.

A FlowSpec instruction takes effect only if the receiving provider accepts it and the forwarding equipment installs a supported action. Validate the match against legitimate traffic, observe its effect and define withdrawal conditions. An established BGP session alone does not prove that filtering is active.

Marseille is the currently declared operational location. Confirm the delivery point and available connectivity for your service before planning a deployment.

Latency follows the actual forward and return paths, peering and congestion. Measure it from your users and origin, during normal operation and mitigation; geographical proximity alone does not establish a latency guarantee.

The public reverse-proxy offers cover FiveM and Minecraft Java. Supported versions, origin delivery, exposed ports and any administration or web endpoints must be reviewed for the selected service.

Network filtering and protocol-specific modules have different scopes. Other games or applications require a compatibility review; the presence of a module in the filtering catalogue does not mean it is enabled or included in every offer. No generic L7 or universal anti-bot result is implied.

After automatic mitigation, Peeryx can apply a post-filtering firewall layer. It can block unused ports, limit specific flows, protect administration services or adapt rules to the constraints of a precise infrastructure.

This layer strengthens security without replacing mitigation: it acts after traffic has already been cleaned by the Anti-DDoS protection.

The best Anti-DDoS protection is the one end users do not notice. Peeryx aims to preserve low latency, fewer false positives, network stability and service continuity even during attacks.

The technology analyzes, adjusts and protects in real time. It is not just a capacity promise; it is designed to deliver traffic that is actually usable.