Security & DDoSEvery server here is covered by enterprise-grade anti-DDoS protection, always on. Almost every attack is absorbed without you noticing. This article is about the rare case where it is not, and why your server can go dark for a while even though nothing is broken.
What you're seeing
- The server is unreachable from every network, not just yours.
- The panel shows the container running normally.
- It comes back on its own after a while, without you doing anything.
Why it happens
Every server is covered by enterprise-grade anti-DDoS protection. When a volumetric attack goes past what the protection can absorb and starts threatening the whole node, the targeted IP is null-routed — blackholed — so the attack stops reaching the node at all. Your server keeps running; the route to it is what disappears.
What to do
- Confirm it is the route and not the server
In the panel, check that the container is still running and the console is still producing output. If it is, the process is healthy and the problem is upstream.
- Wait for the null-route to lift
It is temporary and lifts on its own once the attack subsides. Restarting the server does not shorten it, because the server was never the problem.
- Tell us if it repeats
A single event is normal internet weather. A pattern is worth a ticket with the times and dates, so it can be looked at properly.
Preventive null-routing is a security measure that protects everyone on the node, so it is excluded from SLA downtime calculations. It is the one kind of unreachability that does not count toward a compensation claim.
About this guide: An original guide from the EnduranceNodes team, written for the servers we host. If a step no longer matches what you see, tell us and we will update it.