Filtering close to the source, blackhole control in your hands, and an escalation path that does not involve explaining your business twice.
Volumetric floods are dropped at the edge, upstream of your interface. Your link and your CPU never see the storm.
A BGP community lets you withdraw a prefix or destination instantly and restore it when the wave passes — without opening a ticket and waiting.
Your abuse and NOC contacts are on file before anything happens, so the first call is about the attack, not about who you are.
| Attack shape | Response |
|---|---|
| Volumetric flood | Edge filtering, capacity absorbed upstream |
| Protocol / reflection | Stateless rules matched to the vector |
| Application flood | Rate limits plus behavioural challenge |
| Sustained targeted attack | On-demand blackhole until it subsides |
Mitigation profiles are quoted with the service. Every transit port and bare-metal server can be protected.
The standard layers are: detection, bogon filtering and edge capacity run continuously and are part of the network rather than an opt-in extra.
Legitimate traffic keeps its path. Volumetric attacks are absorbed before your port, so your interface sees the clean remainder.
If your service uses our communities, yes — withdraw and restore on your own schedule. We will document the exact values.
Partially. Filtering works best for prefixes you announce through us. If your space is announced elsewhere, we will be honest about what we can and cannot do.
Ports and commits, address space, racks, or a routing question you want a second opinion on. You get an answer from an engineer, with numbers attached.
