Ingress and public exposure
Prefixes can be announced through BGP or delivered through protected IPs depending on whether you keep your own blocks and routing logic or want a faster initial rollout.
Anti-DDoS protection delivered through cross-connect, GRE, IPIP, VXLAN or router VM, designed to integrate mitigation into infrastructure already running in production.
Peeryx is not just an abstract protection layer. The service sits in the network path to absorb the attack, separate legitimate traffic, then deliver that clean traffic back through the model that best matches your topology and operating constraints.
Prefixes can be announced through BGP or delivered through protected IPs depending on whether you keep your own blocks and routing logic or want a faster initial rollout.
Continuous legitimate traffic analysis, targeted filters and upstream relief only when attack volume requires it, without arbitrarily slowing useful traffic.
Cross-connect, GRE, IPIP, VXLAN or a router VM depending on the integration model and the level of network control your team expects.
Dedicated servers, hosting networks, gaming services, APIs or critical platforms can be protected without forcing a full migration of what is already in production.
Where traffic enters, how it is filtered, how it gets delivered back and what operational constraints that creates in the real environment.
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.
A practical way to start quickly with clean public exposure and lower early complexity.
A standard model for protecting an existing dedicated server without rebuilding the full architecture.
Best suited when your own prefixes and routing policies need to remain in place.
The objective remains to add protection without disrupting the customer’s daily operations.
A clear focus on protected transit for infrastructure, hosting and public-facing services.
Cross-connect, GRE, IPIP, VXLAN and router VM delivery models let you fit Peeryx into your existing network design.
Five included post-filter firewall rules let you ratelimit, accept or drop traffic after mitigation.
Protection spans L3, L4, L5 and L7, including DDoS targeting all L3/L4 protocols.
Protected transit delivered directly in datacenter for low-latency, high-trust interconnection.
Fast deployment model for secure protected transit over established GRE encapsulation.
Simple routed delivery option when IPIP better matches your infrastructure constraints.
Flexible protected delivery for environments built around overlay network designs.
Prefer to keep tunnel control on your side? Peeryx can provide a router VM for iBGP or eBGP return paths.
Choose cross-connect, tunnels or router VM based on your existing topology and operational preferences.
Traffic enters the Peeryx mitigation fabric where volumetric and protocol attacks are filtered in real time.
Firewall rules and behavioral analysis refine the accepted traffic profile after core mitigation.
Filtered traffic is handed back to your infrastructure through the chosen delivery method, with BGP included.
Commit-based pricing keeps the offer transparent while scaling efficiently for larger networks.
Commit pricing
Commit pricing
Commit pricing
Commit pricing
If you prefer to control the tunneling layer yourself, Peeryx can provide a router VM so you can establish tunnels on your side and route traffic back using iBGP or eBGP according to your design.
Add specialized gaming traffic filtering for €190/month when you need deeper rules tailored to game protocols and session patterns.
Up to 24 hours
Up to 72 hours
Under 2 hours with €250 setup
Protect public-facing customer workloads without sacrificing delivery flexibility.
Add premium Anti-DDoS protected transit to exposed backbone segments and edge services.
Secure business-critical applications, APIs and platforms against disruptive traffic spikes.
Protect game-adjacent infrastructure while keeping the transit product as the operational core.
Before buying protected transit, buyers should understand link saturation, 95th percentile billing, blackholing, asymmetric routing and the difference between static profiles and truly adaptive mitigation.
Link saturation, 95th percentile, blackholing, asymmetric routing and clean traffic delivery: the fundamentals before comparing providers.
Read the articleAdaptive mitigation and clean delivery
How to keep an OVH or Hetzner server in production and get legitimate traffic back without rebuilding the whole infrastructure.
Read the articleProtection without full migration
The strengths, limits and deployment cases of the main anti-DDoS delivery models depending on topology and network control.
Read the articleProtection without full migration
The minimum commit is 100 Mbps, billed on a 95th percentile basis.
Yes. Router VM delivery is available when clients want to manage the tunneling layer and return traffic through iBGP or eBGP.
No. It is an optional €190/month add-on for customers who need more specialized gaming rules.
Excess traffic outside the commit is billed at €1.50/month per exceeded Mbps.
Share your architecture with us and we’ll recommend the right protected delivery model.