Peeryx Flow Collector: let your network call for protection
A free collector that connects sFlow, NetStream and IPFIX measurements to Peeryx on-demand DDoS protection. Choose the thresholds and prefixes that fit your network.
Traffic measurement and network operations.
Useful operations start with a timestamp, a scope and a reproducible observation. These guides connect traffic measurements, capacity decisions and incident handling so that each change has a reason and a way back.
Distinguish a telemetry signal from an inline filtering action, and a physical capacity estimate from a measured software limit. Sampling, aggregation intervals and counter conventions affect what a graph can establish.
Suggested reading order
Get observations from the right place
Collect service health and interface or flow telemetry with aligned timestamps. Check exporter reachability and freshness before using missing samples as evidence that traffic has stopped.
Compare rates and paths consistently
Use the same packet-size convention and measurement window when comparing PPS and Gbps. Compare latency on the actual delivery and return paths, including tunnel and filtering changes.
Prepare the change and the rollback
Record the expected effect, the owner, the failure threshold and the rollback action. Test capacity with a node unavailable and keep incident contact information accessible before a cutover.
Guides in this section
16 guides16 / 16 guides
DDoS PPS vs Gbps: compare packet pressure without misleading benchmarks
Convert bandwidth and packet rate with explicit Ethernet assumptions, locate the bottleneck and distinguish wire-rate arithmetic from measured filtering capacity.
DDoS protection costs: compare the complete service
Build a comparable DDoS budget across protected transit, filtering software, hardware and game delivery, with clear commit, percentile and overage assumptions.
How to stop a DDoS attack: emergency response, mitigation and clean traffic delivery
A practical guide to stopping a DDoS attack without improvising: identify saturation, protect legitimate users, activate mitigation, choose between blackhole, FlowSpec, protected IP transit, tunnels or reverse proxy delivery, then restore clean traffic safely.
Why low latency still matters under DDoS mitigation
Under attack, staying online is not enough. Useful Anti-DDoS protection must also preserve stable latency, controlled jitter and clean delivery for legitimate traffic.
What to do when your hoster’s Anti-DDoS is no longer enough
When your hoster’s Anti-DDoS is no longer enough, the worst decision is often to migrate in a hurry. This guide explains how to identify the real limit, keep the existing server when possible, then add specialised protection with tunnels, reverse proxy, router VM or protected IP transit.
How to migrate from a hoster Anti-DDoS to specialised protection without changing server
You can upgrade DDoS protection without moving machines, reinstalling services or leaving your current hoster. The goal is to place a specialised network layer in front of the existing infrastructure, filter attacks there, then deliver clean traffic back to the same server.
How to choose an Anti-DDoS provider without getting trapped
Choosing an Anti-DDoS provider should not be reduced to a Tbps number or a promise of unlimited protection. What matters is how traffic enters the mitigation layer, how it is filtered, how clean traffic is delivered back, what visibility you get during an attack and which limits actually exist.
Low-latency DDoS protection in Europe: why Marseille is strategic
For low-latency DDoS protection in Europe, the location of the scrubbing point matters as much as raw capacity. This guide explains why Marseille is strategic for southern France, Iberia, Italy, the Mediterranean and traffic entering Europe from the south.
Anti-DDoS protection for VoIP, gaming, web and latency-sensitive services
VoIP, gaming, interactive web, APIs and real-time services need Anti-DDoS protection built around latency, jitter, false positives and clean traffic delivery. This guide explains how to protect sensitive services without degrading their normal quality.
How to protect a multi-site infrastructure against DDoS attacks
Protecting a multi-site infrastructure against DDoS attacks requires a full architecture: routing, protected IP transit, clean handoff, role segmentation between sites and credible failover paths. This guide helps design multi-site protection that stays usable in real operations.
Buying DDoS protection: an operator’s checklist
Compare the actual traffic path, packet workload, delivery limits and acceptance evidence before committing to a DDoS service or filtering platform.
PPS and Gbit/s: build a network test plan
Define packet sizes, legitimate traffic and measurement points before comparing filtering configurations.
Latency, asymmetric routing and clean traffic: what really matters in anti-DDoS
Capacity alone is not enough. You also need to understand latency, asymmetric routing, clean traffic delivery, Gbps and Mpps to choose a credible and buyable architecture.
DDoS impact on a network: links, routers, queues and customer services
A DDoS attack does not only affect the targeted server: it can saturate links, routers, queues and neighbouring services.
Anti-DDoS latency explained: how mitigation affects real service quality
DDoS mitigation can add latency when routing, filtering or clean traffic delivery are poorly designed. Learn what really matters before choosing a protection model.
No guide matches this search. Try a protocol name or a shorter phrase.
Use measurements to prepare the next decision.
Flow Collector provides out-of-path observation and can trigger authorized protection workflows. The calculators provide explicit link and server-capacity arithmetic; they do not replace an isolated qualification test.