Cross-connect
A physical datacenter interconnection delivering protected transit directly to your equipment. Prior approval is required.
Protected IP transit & Anti-DDoS
Protected IP transit
Protect your IP prefixes and retain your routing. Receive traffic through a tunnel or a direct connection to your infrastructure.
Technology
Stop attacks upstream. Keep business moving.
Traffic passes through Peeryx protection before reaching your services. Connect in the way that suits your network: BGP, GRE, IPIP, VXLAN or cross-connect.
Architecture overview
Incoming trafficInternet
Your infrastructureClean traffic
Connectivity
Clean-traffic handoff models
GRE tunnel
Fast deployment model for secure protected transit over established GRE encapsulation.
IPIP tunnel
Simple routed delivery option when IPIP better matches your infrastructure constraints.
VXLAN tunnel
Flexible protected delivery for environments built around overlay network designs.
Lan2Lan
A 10G or 100G carrier link connecting your network to Peeryx. Technical review and commercial approval are required before activation.
Router VM
Prefer to keep tunnel control on your side? Peeryx can provide a router VM for iBGP or eBGP return paths.
BGP · Anti-DDoS
Everything included in the default offer
Protect your IP prefixes and retain your routing. Receive traffic through a tunnel or a direct connection to your infrastructure.
- BGP announcement included
- No prefix announcement limit
- Under-ASN support included
- AS-SET available from 500 Mbps commit.
- Anti-DDoS firewall included
- Behavioural mitigation included
- 5 included firewall rules
- Additional rules available at low extra cost
PEERYX / Current commit rates
Estimate your protected transit budget
Choose a commit and compare its monthly cost with your expected 95th-percentile traffic. All amounts are in euros, excluding tax.
Game/Application Anti-DDoS and 5 firewall rules per prefix included with a subscribed commit of 500 Mbps or more.
Compare commitments
Same delivery and options, different commitments. Excess uses your estimated P95; without a P95, only the subscription is compared.
| Commit | Transit | Excess | Total with options | Use this commit |
|---|
Current commit rates
The selected tier prices every Mbit/s of the commit. These are volume tiers, not a progressive calculation that adds the previous tiers.
100–500 Mbit/s€1.50 / Mbit/s / month
501–1,000 Mbit/s€1.20 / Mbit/s / month
1,001–5,000 Mbit/s€1.00 / Mbit/s / month
5,001–100,000 Mbit/s€0.60 / Mbit/s / month
P95 excess: €2.00 per Mbit/s per month, excl. tax.
How the P95 estimate works
For each traffic direction, samples are ranked and the highest 5% are excluded. The larger remaining ingress or egress value is used for billing.
Estimated excess = whole Mbit/s above the commit × €2.00 per Mbit/s. A P95 below the commit does not reduce the subscription price.
One brief peak does not establish your P95. The measurement period, sampling coverage and your contractual metering scope matter.
Before moving from trial to subscription
The trial lasts 7 days. When validated trial P95 exceeds the trial commit, the ordering system requires that measured rate plus at least 20% headroom, rounded up to an available commit. This calculator does not replace that account-specific check.
Included in this calculation
Protected transit, the selected Game/IPv6 options and, without BGP, the selected IPv4 block. Server rental, extra tunnels, firewall packs and physical connection fees are outside this estimate.
The displayed rates apply to a new standard subscription. Existing and negotiated contracts keep their own terms. Taxes, other services and any physical delivery quote are additional.
Connectivity
Deployment windows
Tunnel delivery
IP transit tunnel plans are delivered automatically and immediately when you subscribe through the client area.
Cross-connect delivery
Up to 72 hours
Need a custom setup?
For a physical connection or a custom architecture, our team can help.
Resale and BGP announcements
For your own services or your customers: protected transit that fits your business.
7-day free trial
Test on your own network with one ASN. AS-SET and resale then require an eligible subscription.
Understanding commit and BGP conditions
The threshold applies to the contracted commit of each protected IP transit service, not to port speed or burst traffic.
Below 500 Mbps commit
For your own network only. Reselling Anti-DDoS protection or protected IP transit is not permitted. One ASN only; AS-SET is not supported.
Paid subscription: 500 Mbps commit and above
Reselling protected IP transit and Anti-DDoS protection is permitted. AS-SET is supported with unlimited ASNs and announced prefixes, with no commercial quota.
AS-SET is unavailable during the 7-day trial. Resale is prohibited during the trial; only one ASN is allowed. To enable AS-SET and resale, switch to a subscription with at least 500 Mbps commit.
During the trial and with a subscription, your valid BGP prefixes are announced automatically, with no limit on their number. Without an AS-SET, they must belong to your single verified ASN.
IRR/RPKI validation, route ownership checks and routing security controls still apply.
Technical guides
Plan your deployment.
Routing, tunnels and diagnostics: practical explanations to support your technical decisions.
When should I choose Protected IP Transit instead of a simple protected IP or proxy?
Protected IP Transit makes sense when you want real network control, keep your prefixes or integrate mitigation into an architecture already structured around BGP and clean handoff.
Can I keep my prefixes, ASN and routing policies?
Yes. Peeryx is built for customers that want to preserve network logic, with BGP included, under-ASN support and delivery models compatible with several designs.
Which clean-traffic handoff models are available?
Clean traffic can be returned through cross-connect, GRE, IPIP, VXLAN or a router VM depending on topology, operations and latency targets.
Can Peeryx be used as pre-filtering before my own program or internal edge?
Yes. In some scenarios, Peeryx can protect upstream and hand clean traffic back so your own filtering logic or internal network edge can do the rest.
PEERYX NETWORK
Let’s review your transit architecture
Share your network context, latency targets, preferred handoff model and the services you need to protect. We’ll tell you whether protected transit is the right fit and how to integrate it cleanly.