Customer
Prospective / Internal Review
Hyper-scale botnets such as Aisuru and Kimwolf now operate as residential proxies, blending attack traffic into legitimate user traffic. AI-driven reconnaissance and orchestration tools probe defenses in real time, identify the weakest surface, and launch multi-vector, multi-destination attacks. Stopping this class of attack requires automation paired with human intelligence and proven runbooks, not automation alone.
Prolexic stops DDoS attacks and other unwanted or malicious traffic before they reach applications, data centers, and internet-facing infrastructure, on any port and protocol. It is available on-premises, in the cloud, or as a hybrid combination of both, with a cloud-based network firewall providing an additional, centralized access control layer at the edge of the customer's network.
All Prolexic Routed services are carrier-agnostic and support customers with a routable IP space (IPv4 /24 and/or IPv6 /48). Customers without a routable block, or on cloud-hosting providers, use Prolexic IP Protect instead.
| Service | Model | Notes |
|---|---|---|
| Prolexic Routed, GRE | Cloud | Primary DDoS mitigation service. Logical GRE tunnels return clean traffic asymmetrically to origin; live for 20+ years across enterprise deployments. |
| Prolexic Connect | Cloud | Direct VLAN connections to origin with asymmetric clean traffic return via Equinix Cloud Exchange, GTT, Megaport, or AT&T TAO. |
| Prolexic over Akamai Direct Connect | Cloud | Private interconnect supporting 10G and 100G ports, resilient multi-router metro deployments, and jumbo frame GRE tunnels. |
| Prolexic IP Protect | Cloud | Symmetric service activated via DNS redirection for customers with less than a routable IPv4 /24 and/or IPv6 /48, or fragmented IP space. |
| Prolexic Network Cloud Firewall | Cloud | First line of defense, sitting outside all other firewalls. Customer-managed ACLs and geographic/IP-based rules, integrated via native APIs. |
| Prolexic On-Prem, powered by Corero | On-Prem | Inline, sub-second automated mitigation at the customer edge without traffic backhaul. Suited to latency-sensitive real-time services. |
All traffic is announced to Prolexic via a single BGP route advertisement and passes through one Network Cloud Firewall layer, where ACLs and firewall rules block malicious traffic at the edge before it reaches scrubbing. From there, traffic is split across two regional Prolexic scrubbing centers, each returning clean traffic to its regional origin over a GRE tunnel. Cross-region connectivity gives each origin a redundant path if a regional scrubbing center or origin is degraded.