DDoS Protection for Networks

Imperva DDoS Protection for Networks is a cloud-based DDoS scrubbing and mitigation service that protects network-layer assets (entire IP ranges/subnets) from volumetric and protocol attacks while offering always-on and on-demand routing plus multiple connectivity options (BGP, GRE, cross-connect).

19 Ref Customers

Website

Published Oct 14, 2026

01Common complaints

- Company sizes or stages where this product is over-provisioned or inappropriate - Early-stage startups and small businesses with basic web presence may be better served by lower-cost, self-serve offerings that provide edge-level protection without subnet-level routing changes. - Industries or use cases where competitors may be more appropriate - If an organization is fully hosted on a single hyperscaler and requires tightly integrated, cloud-native DDoS protection with consolidated billing, a hyperscaler-native service may be operationally preferable. - Technical requirements that this product cannot meet - If an organization cannot reroute or advertise prefixes (BGP constraints, ISP limitations), network-layer scrubbing will be difficult to implement. - Budget constraints that make alternatives more appropriate - When budget is constrained and primary requirements are edge-level web protection, lower-cost or free tiers from other vendors may be more suitable. - Specific workflows or integrations where the product may fall short - If an organization requires specific on-prem management integrations (as suggested by at least one review), compatibility should be validated during evaluation. - Red flags in the buying process - DDoS for Networks implementations often require enterprise provisioning; procurement teams should clarify trial scope, contract length, and SLA details during evaluation. - Current limitations acknowledged by the vendor - Public marketing and datasheets emphasize capabilities; explicit product limitations are not prominently documented in the sources reviewed. - Features on the roadmap (not yet available) - Not identified in the publicly accessible sources reviewed. - Scale limitations (at what volume/size does it become ineffective?) - Vendor materials emphasize multi-terabit capacity; no independent boundary conditions or public stress-test results were identified in the materials reviewed. - Security or compliance gaps - Product-specific compliance and certification details were not publicly documented in the reviewed sources; buyers should request formal documentation during procurement. - Technical debt or architectural limitations mentioned in reviews - Reviewer-cited caution about default configurations that may require tuning prior to production deployment. - API limitations or integration constraints - At least one reviewer reported integration uncertainty with a local management system; integrations should be validated during a proof-of-concept.

02Why they buy

- Competitive advantages supported by customer feedback (not just vendor claims) - Review excerpts and product materials indicate: - Reported operational stability during attacks (customer review excerpts). - Reported responsive support in at least one review excerpt. - Unique features and capabilities relative to peers - No clearly unique technical capability was identified that is exclusive to Imperva; many major DDoS vendors provide scrubbing, always-on/on-demand options, and enterprise connectivity. Imperva’s differentiation appears to be in packaging, SLA terms, and integration with its broader security portfolio. - Differentiation from competitors based on reviews - Buyers typically differentiate vendors by ease of onboarding, operational experience during live attacks, SLA enforceability, and SOC/NOC support quality. - Value propositions with evidence from case studies - Vendor-published materials provide high-scale mitigation examples, but independent verification was not found in the reviewed sources. - Areas where competitors have advantages - Cloudflare: public plan tiers and lower-friction onboarding for web use cases. - Akamai: consolidated CDN + DDoS offerings for large enterprises. - Hyperscalers: native integration for cloud-hosted workloads.

03Field reports

- Direct quotes from Gartner Peer Insights, Reddit, TrustRadius, G2, HackerNews - Gartner Peer Insights (accessible summary content) - Reviewer excerpt: "I had a great overall experience with Imperva DDoS Protection, it is dependable, quick and successfully maintains services online even in the face of frequent attacks." (excerpt from a Gartner reviewer shown on the product page) - Another reviewer excerpt: "Imperva DDos protection automatically detects and mitigates… without human intervention… always on security…" (excerpt shown on the Gartner product page) - Caveat: some content on the Gartner page indicates placeholder text in certain sections; readers should validate by reading full reviews directly. - G2 Reviews (Imperva DDoS Protection) - Reviewer excerpt (very positive): "Great performance, superb support. Local presence helps us." (G2 review excerpt) - Reviewer excerpt (positive): "It’s input sanitization mechanism is quite effective." (G2 excerpt; this mixes WAF-like language with DDoS, indicating some reviewers may conflate Imperva’s broader app security stack with DDoS features) - Reviewer excerpt (mixed/critical): "Default values are set such that it allows anyone to bypass the protection unless the customer reviews the settings before deploying it into production." (G2 excerpt) - Reviewer excerpt (integration concern): "Integration with local manager is not possible or I don't know it" (G2 excerpt) - TrustRadius (Imperva DDoS Protection) - TrustRadius lists a moderate product score with a small number of reviews and ratings captured in the session, but full review narratives were not visible in the excerpts captured here. - Reddit (community sentiment about DDoS vendors and buying decisions) - Example comment from a sysadmin discussion: "just tunnel it through Cloudflare and enjoy their FREE and much superior ddos protection.." — anecdotal and unverified; reflects some community sentiment around perceived cost and perceived effectiveness of alternatives. - Community discussions commonly describe DDoS scrubbing providers and the operational models (BGP announcements, more-specific routes) that match on-demand diversion models. - HackerNews - No clearly relevant product-specific HackerNews thread was retrieved in this research session; broader discussions about the company and DDoS topics do exist. - Common criticisms and complaints (support issues, bugs, missing features) - Configuration risk / defaults: - At least one reviewer on G2 warned that default values may allow bypass unless reviewed before production deployment. - Integration clarity: - A G2 reviewer indicated inability to integrate with a "local manager," suggesting an integration or documentation gap for that environment. - Fit / cost concerns: - Some reviewers noted the product may be inappropriate for smaller organizations due to implementation complexity and cost. - Why customers chose this product over alternatives - Themes from reviews and product positioning: - Short time to mitigation (as a buyer perception). - Global scrubbing capacity as presented by the vendor. - Reported perception of effective support/local presence in at least one review. - Why some customers left for competitors (churn reasons) - Direct, vendor-specific churn reasons for DDoS Protection for Networks were not found in the accessible sources. - Community and public discussions suggest cost sensitivity and availability of lower-cost or free alternatives for certain web-only use cases can drive smaller buyers away. - Specific outcomes customers achieved (with metrics when available) - Example qualitative outcome from a G2 review: "Deploying Imperva solved the problem almost entirely" for continuous DDoS attacks (reviewer excerpt). - Note: vendor-published performance claims are present in marketing materials and case studies but were not independently validated in this research session. - Customer pain points and frustrations mentioned in reviews - Need to tune and configure product settings rather than relying on defaults. - Uncertainty about specific integrations with local management systems. - Perception that the solution may be more appropriate for larger organizations. - Deal-breakers and reasons customers didn't purchase - Not explicitly stated in the accessible review excerpts; expected deal-breakers include: - Higher cost for always-on enterprise scrubbing relative to simpler web-proxy-based solutions. - Architectural constraints that prevent rerouting or prefix announcements. - Compliance constraints on traffic inspection or routing. - Detailed customer success stories with metrics - Vendor-published attack write-up describes mitigation of a reported multi-vector attack the vendor reported as being in the terabit range. - Vendor datasheets and blogs list capacity-related figures such as very large scrubbing capacity and multiple scrubbing centers; these are vendor-published figures and were not independently validated in this research session. - Specific results and quantified business impact - Most of the quantified metrics located during this research session are vendor-published capacity or time-to-mitigate claims rather than third-party validated outcomes. - Implementation details and time to value - Vendor materials describe protecting individual IPv4 subnets, routing methods (BGP announcements), connectivity options (GRE tunnel, cross-connect, Equinix Cloud Exchange), and flow-based monitoring for on-demand detection and automatic/manual switchover. - Challenges faced during adoption and how they were resolved - Public case studies reviewed emphasize capabilities and outcomes but do not provide detailed accounts of adoption challenges and resolution steps. - CRITICAL: Note when metrics are vendor-published without independent verification - The following items are vendor claims and were not independently validated in this research session: - Claimed mitigation time SLAs (e.g., very short, seconds-level mitigation SLAs) and statements about typical mitigation times. - Claimed scrubbing capacities (e.g., statements in datasheets mentioning terabit-range capacity), and packet-processing capacity figures. - Note methodology gaps - Vendor capacity and time-to-mitigate statements do not disclose full measurement methodology in the excerpts reviewed (e.g., how scrubbing capacity is computed, test conditions, definitions for mitigation start, SLA exclusions). - Include mixed results - Mixed outcomes were visible primarily in review snippets rather than in case studies: - Positive outcomes: reviewers stating the solution addressed persistent DDoS problems. - Cautionary outcomes: reviewers noting configuration and integration caveats.

04Best fit

- Company sizes: employee counts and revenue ranges (inferred) - Typical fit: mid-market to large enterprise organizations operating routable IP space and/or on-premises or hybrid data centers. - Industries and verticals where adoption is strongest (inferred) - Likely strong in financial services, e-commerce, SaaS, government, education, and other organizations with stringent availability obligations. - Direct named customer examples for this specific product were not found in the publicly accessible sources retrieved. - Roles and personas: decision makers AND end users - Decision makers: - CISO / VP Security - Head of Network Engineering / Infrastructure - IT Director (availability / business continuity) - End users: - SOC analysts (alerting, incident response) - Network engineers (BGP/GRE/connectivity) - SRE/operations teams (availability) - Pain points and challenges the product addresses - Maintaining reachability of network services under volumetric attacks. - Reducing manual mitigation steps through automated mitigation and operational support. - Qualification criteria: what makes a good fit - The organization can route traffic through a scrubbing provider (BGP/GRE/cross-connect) and has the operational maturity to test failover. - There is a requirement to protect non-HTTP assets and/or entire network blocks. - The organization has explicit uptime/availability requirements (contractual or regulatory). - Deal disqualifiers: what makes a poor fit - The organization only requires basic website protection and cannot justify enterprise networking changes. - The organization cannot announce or route the required IP space (BGP constraints) or lacks an appropriately sized routable IP block where applicable. - The organization requires fully transparent self-serve pricing and does not want a sales-led procurement process. - Real customer examples with company names when available - No specific named customers for this product were identified in the publicly accessible sources captured in this session.

05The pitch

What the product does (core value proposition in objective terms)

- Imperva’s DDoS Protection for Networks is a cloud-based DDoS scrubbing and mitigation service designed to protect network-layer assets (entire IP ranges / subnets, not just web applications) from volumetric and protocol attacks. - Deployment models described by Imperva include always-on routing through the vendor and on-demand diversion (typically via BGP), plus connectivity methods such as GRE tunnels and cross-connect options (including third-party data center connectivity). - The network product is positioned as part of a broader DDoS portfolio (websites, networks, individual IPs, DNS, contingency).

Target market and market positioning

Target buyers include mid-market and enterprise organizations with Internet-facing network infrastructure that requires Layer 3/4 protection (and often Layer 7 / multi-vector protection as part of a broader security portfolio).
Language about protecting an entire C-Class range (a typical routable subnet) indicates a common fit for organizations that need to protect a routable subnet and require scrubbing capacity and operational support.

Get a comprehensive analysis of DDoS Protection for Networks including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →