A prefix list is a named, reusable group of IP networks — single IPs or CIDR ranges like 192.168.1.0/24. Once created, you attach it to a protection profile and use it to blacklist or whitelist that traffic. Open DDoS Mitigation → Prefix Lists in my.cubepath.com.
The reason to use a list rather than individual rules is maintenance: one list applied to five protected IPs means adding an attacker's network in one place, not five.
List overview
The table shows every prefix list with its Name, Description, the number of Entries it holds, and its Type:
- Custom — lists you create and fully manage.
- Global — built-in, shared lists. They're read-only: you can view their entries but not edit or delete them.
Use the search box to filter by name or description.
Create a prefix list
- 1Start a new listClick Create Prefix List.
- 2Name itEnter a Name (e.g.
Blocked Datacenters) and an optional Description. - 3CreateClick Create. The list starts empty.
TipName lists after their purpose, not their contents —
Office allow,Scraper networks,Blocked datacenters. You'll be reading these names months later when deciding whether a list still applies.
Manage entries
Click Entries on any list to view its networks.
- On Custom lists, type an IP or CIDR and click Add. Remove one with the X beside it.
- On Global lists, entries are read-only.
NoteA single IP works too — a
/32(IPv4) or/128(IPv6) suffix is normalized automatically.
How it's applied
ImportantA prefix list does nothing on its own. It only takes effect once a protection profile references it.
In a protection profile, set Prefix List Mode to:
| Mode | Effect |
|---|---|
| Blacklist | Drop traffic from the assigned prefixes |
| Whitelist | Allow only traffic from the assigned prefixes |
| Off | Ignore prefix lists for that profile |
Then select which lists apply.
WarningWhitelist mode drops everything not on the list. It's the right choice for an internal or staging address, and a fast way to take a public service offline if you apply it to the wrong IP. Double-check which address the profile belongs to before switching.
Where the entries come from
The efficient loop is to build lists from real traffic rather than from guesswork: in Traffic Capture, source IPs in the packet log can be added straight to a prefix list. During an incident that turns "this network is flooding us" into a block in a couple of clicks.
Delete a prefix list
Click the trash icon on a Custom list and confirm. This removes all its entries and unassigns it from any protection profiles. Global lists can't be deleted, and the action can't be undone.