Clean traffic delivery before attacks reach your network.
A DDoS scrubbing center is filtering infrastructure that receives traffic, removes malicious flows and forwards legitimate packets to the protected service.
Traffic is steered through scrubbing capacity using BGP, DNS or a proxy path. Filtering systems inspect packets and flows, drop attack traffic and pass clean traffic toward the origin through direct transit, GRE tunnels or private interconnects.
Always-on scrubbing keeps traffic protected at all times and avoids emergency route changes. On-demand scrubbing can work for lower-risk networks, but activation and traffic convergence must be planned before an incident.
Good scrubbing reports show attack volume, protocol mix, top sources, mitigated vectors, clean throughput, latency and dropped traffic. These metrics help tune filters without blocking legitimate users.
Confirm protected prefixes, origin handoff and routing policy
Test GRE, direct cross-connect or transit delivery before an attack
Define contacts and escalation paths for emergency changes
Review filter profiles for TCP, UDP, DNS and web services
Monitor clean traffic, dropped traffic and latency
Document when blackholing is acceptable as a last-resort action
Usually no. Scrubbing happens in the network path and forwards clean traffic to the same service, though routing and origin handoff must be configured.
Clean traffic is legitimate traffic that remains after malicious packets, floods or abusive flows have been removed by the filtering layer.
Always-on is preferred for public services where downtime, route convergence or emergency activation delays are unacceptable.
TMW Shield provides network DDoS mitigation with protected routing, filtering profiles and engineer-led incident response.