Delivery
Block traffic
Blocking happens at the edge of the proxy, before a request is forwarded to your origin, so a blocked IP never puts load on your infrastructure.
How it works
- Block an address from Security operations — the Redis-backed list answers403 before your origin sees the request
- A fixed per-IP window (default 120 requests per 60 seconds) answers 429 — and only counts requests that matter
- The proxy evaluates sensitive paths, content-block rules, WAF regexes, the IP list, CIDR and country policies, then the rate cap — first match wins
Good to know
- Blocklist and rate-limit checks are intentionally lightweight so they don't add meaningful latency to legitimate traffic