Overview
What this area covers, and what each part needs before it works.
Two related things on the same addresses: attack history, which reads what our network absorbed for your IP space, and firewall, which reads and manages the rules and filters on it. They share a definition of which addresses are yours.
| Page | What it covers |
|---|---|
| Attack history | Query attacks by address, prefix, ASN or window; alert on ongoing ones |
| Firewall | Create and delete rules and stateful filters, and read state back |
| Ownership | Which addresses both endpoints treat as yours |
| API Reference | Every endpoint, with a playground |
Both areas are gated
Neither is on by default. Attack history needs the Attack History API flag on
your organisation and the attacks.read ability; firewall needs the Firewall
API flag plus firewall.read to read and firewall.manage to write. See
Activation.
Writes are the slow half
Reads are immediate. Firewall writes are accepted synchronously but take 3-5 minutes to propagate globally, are not atomic across ports, and skip silently on delete — all of which is on the Firewall page and is the part most worth reading before you script against it.