DDoS protection
Every address is behind BitsNull. By default.
Protection at Auronys is not a product you add. It is how the network is built. Our own mitigation engine sits inline in front of every workload we host.
3D illustration: a wall of red glass carrying the BitsNull lattice, with a row of server racks behind it. Hostile traffic ends on the glass.
How it works
The volume is absorbed. The rest is decided.
Two layers, each doing only the job it is good at. And a third thing most protection leaves out: you can watch it work.
Schematic: traffic arrives from the left. Hostile packets end at the BitsNull line. Clean traffic continues to your server.
01 · Absorb
The flood is taken far from your server.
A global anycast scrubbing network absorbs volumetric attacks upstream. Only generic rules that are safe for any port are applied there.
02 · Decide
The engine inspects every packet.
BitsNull runs inline. Stateful TCP handling, a filter profile per service, and protocol-aware filtering for game traffic.
03 · Deliver
Clean traffic reaches your instance.
Any protocol, on any port. Nothing is forbidden to make filtering easier for us.
The principle
An attack is defined by behaviour, not by bandwidth.
A small flood of fake connections can take a game server offline while the traffic graph stays flat. A threshold in megabits would never see it. BitsNull compares each address against its own baseline instead.
What you see and control
No black box.
You manage protection for your own addresses in the BitsNull panel, and you see what it does.
Profiles
A filter profile per service.
Set by address, port and transport, with parameters you can tune.
Modes
Observe or enforce.
Watch what a profile would do before it drops anything.
Observe marks what the profile would drop. Everything still passes.
Visibility
What arrived. What was dropped. Why.
Traffic and attack views for your own addresses.
Evidence
Attack history and reports.
Evidence for each attack, exportable as a PDF.
Discovery
New services are noticed.
Unconfigured traffic is spotted and a profile is suggested for it.
The fragments above are schematic. They show how the panel is organised, not live data.
Application-layer protection.
An optional layer per service, where traffic terminates on a BitsNull edge proxy before it reaches you: web with TLS and a browser challenge, Minecraft and FiveM.
It is being built now. It is not available yet, and this page will say so until it is.
More about the engine at bitsnull.com
Being attacked right now?
Say so in the first line. Tell us what you run, on which ports, and what the attack looks like from your side.