Every CoreNetHub server sits behind always-on network scrubbing at no extra cost, with optional layer 7 filtering for application-targeted attacks. No traffic cap, no null-routing as a first response. From $119/mo.
The goal of mitigation is not to survive an attack with the server switched off. It is to keep real visitors reaching it while the attack is dropped upstream.
SYN floods, UDP amplification and reflection attacks are filtered at our transit edge, across multi-terabit capacity. The traffic never reaches the port your server is plugged into, so a 1 Gbps uplink cannot be saturated by them.
Attacks that look like real HTTP requests — slow POSTs, cache-busting query strings, credential stuffing — need request inspection rather than packet filtering. Available as an add-on on any plan.
Many hosts respond to an attack by blackholing your IP, which achieves the attacker's goal for them. We divert through scrubbing instead, so the service stays reachable for legitimate traffic.
Being attacked is not a billable event. There is no traffic cap on mitigation and no surprise invoice after an incident — the protection is part of the plan, not a meter.
Yes. Always-on network-level scrubbing is on every server on every plan, with no traffic cap and no per-incident charge. Layer 7 filtering, which inspects application traffic rather than packets, is the paid add-on.
Volumetric attacks are scrubbed upstream at multi-terabit capacity across our transit providers, so an attack is dropped before it reaches the port your server sits on. Attacks that saturate a single 1 Gbps port never reach the server at all.
No. Traffic is diverted through the scrubbing path rather than null-routed, so legitimate visitors keep reaching the server while the attack is filtered. We do not blackhole a customer IP as a first response.
Layer 3/4 attacks try to exhaust bandwidth or connection tables — SYN floods, UDP amplification, reflection. Those are handled by the included scrubbing. Layer 7 attacks look like real requests and target the application: slow POSTs, cache-busting query strings, credential stuffing. Those need request inspection, which is the add-on.
Under normal conditions traffic follows its usual path and mitigation adds no measurable latency. During an active attack, traffic is routed through a scrubbing centre, which typically adds 2 to 8 ms depending on the datacenter.