Technical Guide

The biggest problem in a DDoS attack is trying to stop attack traffic after it has already reached your link. Once the link is full, the firewall on your server no longer helps. Remote DDoS protection moves filtering in front of your link: traffic passes through a filtering network first, and only the clean part returns to you. Your servers stay where they are.
What is remote DDoS protection?
Remote DDoS protection is a protection model that redirects your traffic to a remote filtering network so attacks are stopped before they reach your own network. You do not have to change your infrastructure, move servers or buy new hardware.
The flow has three steps:
- Routing: You announce the prefixes to protect to the WireShield network with BGP. Traffic from the Internet reaches us first.
- Filtering: Attack traffic is analyzed and blocked. Legitimate traffic passes.
- Delivery: Clean traffic returns to your infrastructure over the connection method you chose.
This model fits hosting and cloud providers, internet service providers, and enterprise networks that need uninterrupted access for data center and cloud environments. See the remote DDoS protection page for details.
How is traffic routed with BGP?
BGP is the protocol networks use to tell each other which IP blocks can be reached where. With remote protection a BGP session is built between your own ASN and prefixes and WireShield. When you announce the prefixes, traffic to those addresses arrives at the filtering network.
You can use protection in two ways:
- Always-on: Traffic always passes through the filtering network.
- On-demand: Routing is switched on only when you need it.
A letter of authorization (LOA) and RPKI records are needed for the announcement; we complete these steps together during setup. Before taking BGP sessions live, have a look at the BGP go-live checklist.
How does clean traffic come back to you?
Filtered traffic is delivered to your infrastructure with one of three methods:
| Method | How it works | When it fits |
|---|---|---|
| GRE tunnel | Delivery over a tunnel across the Internet | Quick setup, compatible with most environments |
| VXLAN | Flexible transport over Layer 2 | Data center and cloud environments |
| Cross-connect | Physical connection in the data center | High capacity and low latency |
The BGP routing plan follows the method you choose. If you have no router, we can discuss a Router VM. If you use GRE, tunnel MTU is the most common source of trouble; see our guide on MTU in GRE tunnels.
What do you need for remote DDoS protection?
You do not need every answer up front, but technical assessment is much faster when these are ready:
- The ASN and prefixes you want to protect (IPv4 and/or IPv6)
- Whether you need a BGP-capable router or a Router VM
- Your preferred delivery method (GRE, VXLAN or cross-connect)
- Expected clean traffic, including peaks and growth
- Always-on or on-demand preference
- Support and SLA expectations
For the complete list, use the pre-installation checklist in the documentation.
Which attacks does it stop?
Filtering covers volumetric and protocol attacks at the network and transport layers: UDP flood, SYN flood, DNS and NTP amplification, ICMP flood and fragment attacks. HTTP/L7 and service-specific needs are scoped separately in a technical assessment. For UDP-based attacks, we explained which data to watch in the UDP flood guide.
What do you see in the portal?
While protection is active you follow everything in the Customer Portal: live traffic, attack history and downloadable PDF reports. You manage your own rules, rate limits and allow-list, and receive attack notifications by e-mail and webhook. The API reference is ready for integration with your own systems. For the whole portal, see the Platform page.
How is the cost determined?
The price depends on the clean-traffic capacity you need (from 50 Mbps to 10 Gbps). Billing follows the 95th percentile, yearly billing includes a 15% discount and the number of protected prefixes is unlimited. You can see an indicative price in the price calculator; the final offer is set by the technical scope. For capacities above 10 Gbps or multi-location projects you can request a custom quote.
7-day free trial
If you want to try remote protection first, fill in the trial form. You apply with your own ASN and prefix details; our team reviews the request and contacts you, and scope and dates are agreed before the trial starts.
Common mistakes
- Taking a GRE tunnel live without verifying MTU.
- Not planning return routing.
- Redirecting all prefixes at once. Test with a single prefix first.
- Sizing capacity on average traffic only and ignoring peaks and growth.
Frequently asked questions
Do I need hardware for remote DDoS protection?
No. Protection happens on the WireShield filtering network. You only need a router that speaks BGP; if you have none, we can discuss a Router VM.
Do I have to move my servers?
No. Your servers stay in your current data center; only the traffic passes through the filtering network first.
What is the difference between remote protection and WireShield Edge?
With remote protection traffic is filtered on WireShield infrastructure and clean traffic returns to you. WireShield Edge filters traffic inside your own network, inline. For selection criteria see the inline vs. remote comparison.
Next step
Share your topology and traffic needs and we will choose the right connection method together. You can talk to the technical team or calculate the price as your next step.