Controlled network exposure
BGP announcements for your prefixes or exposure through protected IPs depending on the level of control you want, rollout speed and the way your network already operates.
Protected IP transit & European Anti-DDoS infrastructure
Protected IP transit Anti-DDoS for operators, hosters and critical services
Peeryx protects prefixes, exposed services and latency-sensitive environments with a readable model: volumetric mitigation, BGP, protected IP transit and clean traffic delivery back to production.
Protected IP transit, volumetric mitigation and clean handoff
Protected IP transit with BGP included, under-ASN and AS-SET support
Clean-traffic delivery through cross-connect, GRE, IPIP, VXLAN or a router VM
Protection for infrastructure already in production without forced migration
24h trial to validate the integration design before a larger rollout
Protected IP transit & European Anti-DDoS infrastructure
Peeryx protected IP transit
Starting from €1/Mbps
- 100 Mbps minimum commit at 95th percentile
- BGP included
- Tunnel, cross-connect or router VM
- Advanced Anti-DDoS filtering included
Announced mitigation capacity
30+ Tbps
Protected IP transit, clean traffic delivery and readable network integration for environments that are already live.
European footprint
European points of presence
Marseille is the initial scrubbing center. Paris is part of the launch design for handoff and network integration. Frankfurt, Amsterdam and Madrid follow in the next expansion phases.
Live / included at launch
Coming soon
Paris
Included point of presence
Marseille
Primary scrubbing center
Frankfurt
Coming soon
Amsterdam
Coming soon
Madrid
Coming soon
Protected IP transit Anti-DDoS
BGP included
Protected IPs or customer prefixes
GRE / IPIP / VXLAN
Cross-connect / router VM
Pre-filtering before XDP / DPDK
L3 to L7 by service
24h trial depending on scenario
How Peeryx works
Peeryx intercepts the attack, filters precisely and hands back only useful traffic
Peeryx sits between the Internet and your production as a specialized network layer. Depending on the scenario, your prefixes are announced toward the platform or your services are exposed through protected IPs, then legitimate traffic is returned through the delivery model that best fits your environment.
Protected transit or protected IPs depending on the need
BGP included with under-ASN and AS-SET support
GRE / IPIP / VXLAN / cross-connect / router VM
Compatible with symmetric or asymmetric routing
Mitigation built around real traffic
Filtering is designed to preserve legitimate traffic, with continuous observation, targeted signatures and upstream relief only when attack volume truly requires it.
Delivery matched to your topology
Cross-connect, GRE, IPIP, VXLAN or a router VM: Peeryx does not force a single model. The right handoff depends on your edge, hoster, target latency and operating style.
Existing infrastructure preserved
Dedicated servers, clusters, gaming platforms, APIs and critical services can stay where they are. The goal is to protect what already runs before considering wider changes.
How Peeryx receives traffic, how mitigation is applied, how clean traffic comes back and how much network control the customer keeps.
Delivery models
Choose the right integration model
Depending on your topology, clean traffic can be delivered through protected IPs, GRE, IPIP, VXLAN, cross-connect or a router VM. The right choice depends mainly on the infrastructure already in place and the level of network control you need.
Protected IPs
A practical way to start quickly with clean public exposure and lower early complexity.
GRE tunnel
A standard model for protecting an existing dedicated server without rebuilding the full architecture.
BGP
Best suited when your own prefixes and routing policies need to remain in place.
Production-first approach
The objective remains to add protection without disrupting the customer’s daily operations.
Core offers
Each offer fits a concrete need: protecting live prefixes, keeping your own filtering logic or adding a specialised layer for selected public gaming services.
Protected IP Transit
From €1/MbpsBGP, clean traffic, readable handoff and network integration for exposed prefixes or IPs.
Anti-DDoS Router VM
From €99/mo*Keep your own XDP, eBPF or routing logic behind a first volumetric protection layer.
Anti-DDoS Dedicated Server
From €149/mo*Build your own filtering stack behind upstream protection.
Gaming Reverse Proxy
From €29/mo*For selected public gaming services that need a specialised layer.
A network offer built to protect without breaking operations
Peeryx is designed for teams that want a service they can defend technically: keep your prefixes, use protected IP transit, add upstream filtering, deploy a router VM, a dedicated Anti-DDoS server or a gaming reverse proxy depending on the real scenario.
Prefixes, ASN and BGP policies can remain in place depending on the scenario
Clean traffic can be handed back to an existing dedicated server, cluster, proxy or backbone
Upstream pre-filtering is possible before your own XDP, DPDK or custom proxy logic
Integration is designed for real production environments, not just a lab diagram
Peeryx protected IP transit
Starting from €1/Mbps
- 100 Mbps minimum commit at 95th percentile
- BGP included
- Tunnel, cross-connect or router VM
- Advanced Anti-DDoS filtering included
- Post-filter firewall included
- 5 included firewall rules
- 24h free trial
Transit pricing
Readable pricing for teams comparing a real protected transit service with handoff models adapted to customer network constraints.
100 Mbps → 500 Mbps
€1/Mbps
Commit pricing
500 Mbps → 1 Gbps
€0.60/Mbps
Commit pricing
1 Gbps → 5 Gbps
€0.44/Mbps
Commit pricing
5 Gbps → 10 Gbps
€0.29/Mbps
Commit pricing
Minimum commit: 100 Mbps at 95th percentile
Excess outside commit: €1.50/month per exceeded Mbps
What Peeryx lets you preserve and improve in production
A production-ready offer without making your architecture heavier than it needs to be
Peeryx is not only about absorbing attacks. The offer is built to simplify BGP announcements, preserve network flexibility and keep filtering options that remain genuinely useful once clean traffic is delivered back.
BGP announcement included and free
No prefix announcement limit
Additional rules available at low extra cost
BGP and routing control
Everything needed to announce your prefixes cleanly and integrate the service without friction on the routing side.
- BGP announcement included and free
- No prefix announcement limit
- Under-ASN support included
- AS-SET parameter supported
Filtering already included
A serious mitigation baseline available from day one, without needing to assemble multiple separate layers first.
- Anti-DDoS firewall included
- Behavioral AI-based protection included
Operational flexibility
Rules and extensions that can grow with the environment without redesigning the whole delivery model.
- 5 post-filter firewall rules included
- Additional rules available at low extra cost
+190€/mois
Optional game filtering
Add a specialized filtering layer for services like Minecraft Java or FiveM while keeping the same network foundation and clean-traffic delivery model.
Deployment windows
Tunnel delivery
Up to 24 hours
Cross-connect delivery
Up to 72 hours
Urgent option
+€250 setupActivation in under 2 hours
Specialized protection for Minecraft Java, FiveM and exposed gaming services
Gaming reverse proxy offers extend the Peeryx core when an application needs more specific logic. The principle stays the same: serious network protection, controlled latency and clean traffic delivered back to the customer environment.
Blog
Technical guides, network comparisons and architecture notes
Content written for network teams, hosters, operators and exposed services: protected IP transit, tunnels, BGP, latency, clean handoff, multi-site designs and architecture choices before buying.
How do you mitigate a DDoS attack above 100Gbps?
Link, PPS, CPU, upstream relief and clean handoff: the real framework behind credible 100Gbps mitigation.
Read the article
BGP Flowspec for DDoS: useful or dangerous?
What Flowspec does well, what it should never do alone and how to fit it into a safe multi-layer strategy.
Read the article
Anti-DDoS clean traffic delivery: why the handoff matters as much as mitigation
In Anti-DDoS architecture, mitigation alone is not enough: legitimate traffic still has to be delivered back correctly. This guide explains why clean traffic handoff matters as much as scrubbing, how to choose the right delivery model and which mistakes break daily operations. It also helps compare clean traffic delivery, clean handoff, GRE, IPIP, VXLAN and cross-connect with an operator-grade architecture, operations and buying logic.
Read the article
Gaming Anti-DDoS: why generic filtering is not always enough
Gaming needs Anti-DDoS protection built around sessions, latency, false positives and real protocol behaviour. This guide explains why generic filtering is not always enough and how to design a more serious gaming protection model. It also helps compare gaming Anti-DDoS, false positives, session stability and game-specific filtering with an operator-grade architecture, operations and buying logic.
Read the article
Peeryx FAQ
Is Peeryx only focused on gaming?
No. The core Peeryx offer is Protected IP Transit Anti-DDoS for operators, hosters, SaaS, APIs, critical services and exposed infrastructure. Gaming offers are specialized add-ons.
Do I need to migrate my whole infrastructure to use Peeryx?
No. Peeryx can protect infrastructure already in production and return clean traffic through BGP, GRE, IPIP, VXLAN, cross-connect or a router VM depending on your design.
Can I keep my prefixes, ASN and BGP logic?
Yes. BGP announcement is included, under-ASN support is available and AS-SET can be supported when the integration scenario requires it.
Can Peeryx be used as pre-filtering before internal or custom filtering?
Yes. Depending on the architecture, Peeryx can absorb, clean and hand traffic back to your infrastructure so that you keep part of the control or additional filtering internally.
Let’s talk about your prefixes, links and clean-delivery model
Share your prefixes, ports, current hoster, routing model and the way you want clean traffic delivered back. We will come back with a realistic design that is readable for both operations and buying teams.