Radware Cloud DDoS Protection BYOIP Integration Overview
Worth Knowing
A /23 is required only for the more-specific diversion method. Other methods discuss /24. No single origin ASN is stored.
Searching for the best IP providers? Radware Cloud DDoS Protection diverts customer prefixes with BGP and returns clean traffic over GRE. The service documents IPv4 and IPv6 network prefixes, a letter of authorization for route advertisements, and tunnel setup. Cloud protection can sit beside on-premises mitigation in a hybrid design.
Provider Details
| Field | Information |
|---|---|
| Provider Name | Radware |
| Website | Cloud DDoS Protection |
| ASN(s) | Not stored as one origin. Radware operates more than one network. Confirm the origin for the topology you choose. |
| Tech Article & Date | Cloud DDoS Protection - checked 7 October 2026 |
| BYOIP Scope | Cloud DDoS network protection using BGP diversion, including hybrid designs with on-premises mitigation. |
| Supported Versions | IPv4: /24. IPv6: /48. |
Caveats and Gotchas
- A /23 aggregate applies only to the more-specific diversion method. Other methods in the same guide discuss /24. Do not treat /23 as the minimum for every Radware deployment.
- An LOA is documented for cloud route authorization. A ROA requirement was not established in the reviewed sources.
- Older technical articles describe the mechanics. They do not guarantee that every current contract uses the same terms. The product page shows the offer is still active.
- Onboarding uses a portal plus authorization and network setup. Complex deployments involve the SOC. That is assisted setup, not automatic onboarding.
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | IPv4 /24, except the more-specific diversion method, which asks for at least a /23 aggregate. IPv6 /48. |
| LOA | Accepted. Documented for cloud route authorization. |
| Return path | GRE in the documented BGP diversion workflow. |
| Modes | Always-on, on-demand, and hybrid. |
Step-by-Step BYOIP Process
Step 1
Start in the onboarding portal and provide the authorization and network details Radware asks for.
Step 2
Choose the diversion method before you size the prefix.
Only the more-specific method uses the /23 aggregate.
Step 3
Pricing is a quote.
Site eligibility is confirmed during onboarding.
Related Resources
Published 7 October 2026