Cut your attack surface by an entire continent.
Block the countries the flood comes from, or allow only the ones your players are in. PAKKT pushes up-to-date CIDR ranges into nftables sets, in both IPv4 and IPv6, with an anti-self-block guard that always protects your access.
Block a list, or allow only a list.
Everything passes, except these countries
You list the countries to block. Good for cutting off recurring attack origins while staying open to the rest of the world. Verdict saddr @set drop.
Nothing passes, except these countries
You list the only allowed countries. Perfect for a regional service (European game, etc.): the attack surface shrinks to your actual zone. Verdict saddr != @set drop.
nftables sets, delivered up to date.
PAKKT does not perform a GeoIP lookup on the agent: the Core API resolves the CIDR ranges and delivers them already computed. The agent installs them atomically into named sets, updated in a single nftables transaction.
- ▸Source: ipdeny.com aggregated zones, refreshed every week.
- ▸Deduplication: ranges are repushed only when they actually change.
- ▸v4 + v6: country_v4 / country_v6 sets, on input and forward.
- ▸safe_ips guard: localhost and Core API stay allowed, at the top of the chain.
Explore the platform
Frequently asked questions
Straight answers, no marketing fog.
How does country blocking work at PAKKT?
Where do the per-country IP ranges come from, and are they up to date?
Does country blocking support IPv6?
Is there a risk of blocking yourself when enabling a country policy?
When is country blocking useful?
Cut off what has no business reaching you.
From 3 € / server / month. Use a preset (EU, North America, top DDoS threats) or build your own list. Free 7-day trial.