Peeryx Flow Collector：让您的网络发出防护信号
将 sFlow、NetStream 和 IPFIX 测量数据接入 Peeryx 按需 DDoS 防护的免费采集软件。由您决定阈值与需要保护的前缀。
流量测量与网络运维。
有效观察需要时间戳、明确范围和可复现方法。这些指南连接流量测量、容量决策和事件处理，让每次变更都有依据和回退方式。
区分遥测信号与在线过滤动作，以及物理容量估算与软件实测上限。采样、聚合间隔和计数口径会影响图表能够支持的结论。
建议阅读顺序
在正确位置收集数据
按对齐的时间戳采集服务状态、接口或流遥测。将缺失样本视为流量停止的证据前，检查导出器可达性和数据新鲜度。
一致地比较速率与路径
比较 PPS 和 Gbps 时使用相同的包长口径和测量窗口。沿实际交付与回程路径比较延迟，并计入隧道和过滤变化。
准备变更与回滚
记录预期效果、负责人、失败阈值和回滚动作。在节点不可用的情况下测试容量，并在切换前准备好事件联系人。
本专题指南
16 篇指南部分指南仅提供英文版。打开前即可看到语言标识。
16 / 16 篇指南
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.
没有匹配的指南。请尝试协议名称或更短的关键词。
用测量结果支持下一步决策。
Flow Collector 在数据路径之外观察流量，并可触发获授权的防护流程。计算器明确展示链路与服务器容量计算，但不能替代隔离环境中的资格验证测试。