Available upstream capacity
Transit capacity available at our upstream carriers to absorb an attack before it reaches our filtering servers. This is not scrubbing capacity we own outright.
Trust center
Everything we claim, you can check
Check our AS number, public routing records, company details and contractual documents. Operator declarations, our telemetry and external records have different scopes; the source and method help you assess each claim.
Public verification
External network records and our own service-status page. PeeringDB entries are maintained by participating networks; listing a source here does not make it an independent audit.
The company
- Legal name
- PEERYX NETWORK
- Legal form
- Société par actions simplifiée (SAS)
- Share capital
- 1 000 EUR
- Trade register
- 104 733 340 R.C.S. Nîmes
- VAT number
- FR57104733340
- Registered office
- 83 rue André Le Nôtre, Bât A3 Parc Act, 30900 Nîmes, France
- President
- Paul Emmanuel Flores
- Managing director
- Manon Josette Bertelli
- Sales contact
- [email protected]
- Phone
- +33 7 66 85 66 73
Capacity, without ambiguity
Capacity figures invite misunderstanding. Here is exactly what each one refers to.
Largest peak handled
Highest packets-per-second peak recorded on a single attack, taken only from records whose packet peak and bitrate peak are mutually consistent: packet size within a valid Ethernet frame, and bitrate below the available upstream capacity. Records failing that check are excluded from the calculation.
Attacks mitigated
Telemetry from our filtering servers over the stated period. Raw figure, not rounded up.
Scope of application-layer (L7) filtering
Application-layer filtering depends on the protocol module, enabled rules, supported version and selected offer. The list below describes catalogue scope, not universal activation or a generic web application firewall. Confirm protocol compatibility and the protection applied to your service before deployment.
- FiveM / RedM
- Garry's Mod & Source
- Minecraft (Java online, offline, Bedrock)
- Rust
- SSH
- VXLAN
- HTTP / TLS
What our servers actually filtered
Telemetry over a rolling period. Raw figures, not rounded up.
27 472Attacks mitigated
3.12 GppsLargest peak handled
93attacks above 100 Mpps
44 sMedian duration
- Period
- 2026-07-15 → 2026-10-17 (94 days)
- Method
- Every attack is recorded by our filtering servers’ telemetry: detection timestamp, packets-per-second peak, bandwidth peak, vector, resolution. Isolated outliers — a single reading far above the 99.9th percentile — are excluded until confirmed.
Points of presence
What runs today, what is being built, what is planned. Never mixed together.
In service
- Marseille FR
Deploying
- Paris FR · 2026
Planned
- Frankfurt DE · 2026
- Amsterdam NL · 2026
- Madrid ES · 2026
- New York US · 2027
Declared facilities
Facilities declared in our public PeeringDB record, retrieved on 2026-08-10. This dated declaration does not establish current port capacity, active scrubbing at every building or an independent site audit. Confirm the delivery location for your service.
- Digital Realty Marseille MRS1/2/3/4 Marseille · FR
- Equinix PA5 — Paris, Victor Hugo Paris · FR
- Digital Realty Paris PAR5 Paris · FR
Operations
- Availability target
- 99 %
- Maintenance notice
- 7 days
- Service status
- Open
- Network operations
- [email protected]
What the SLA does not cover
The availability target expressly excludes DDoS attacks, mitigation, emergency filtering, blackholing and attack-driven saturation, as well as maintenance and third-party supplier incidents. No compensation is automatic. We would rather write it here than let you find it in the contract.
Support
Our filtering servers detect and mitigate continuously: across 27472 handled attacks, not one hour of the day is empty. That said, no human on-call hours or response times are contractually committed today. We will not advertise them until they are written in a document you can read.
Security and reporting
- Abuse reports
- [email protected]
- Security contact
- [email protected]
- security.txt
- /.well-known/security.txt
Contractual documents
- Legal Notice
- Read the document
- Terms and Conditions of Sale
- Read the document
- Terms of Use
- Read the document
- Privacy Policy
- Read the document
- Cookie Policy
- Read the document
- Acceptable Use Policy (AUP)
- Read the document
- Service Level Agreement (SLA)
- Read the document
The service, concretely
- Trial
- 7 days
- Delivery models
- BGP · GRE · IPIP · VXLAN · LAN-TO-LAN · CROSS-CONNECT · ROUTER-VM