Abuse reports

Last updated: October 2026

Where to send a report about a Kvantis server, how we handle it, and what to do if your own server was reported. This page complements our Acceptable Use Policy.

How to report

Email abuse@kvantis.org. To let us act quickly, include:

• the IP address of the server;
• the date and time with time zone (UTC preferred);
• the evidence — log lines, email headers, URLs or screenshots.

An IP and a timestamp are enough to identify the exact server, even if its address has changed since. Reports without them usually need a follow-up question and take longer.

Reports may also reach us forwarded by our infrastructure provider (currently Vultr) — spam complaints, scan detections, copyright notices, attack reports. However a report arrives, it is matched to a server the same way.

What we do with a report

Every report is reviewed and its severity assessed. Critical abuse — active attacks, phishing, malware distribution or command-and-control, botnets — can lead to the server being suspended immediately and without notice: every minute it stays online harms others and the reputation of the shared IP space.

Everything else — a copyright notice, a single spam complaint, an open service flagged by a scanner — starts with a notice, not a shutdown. Depending on the case we may:

• ask you to fix the issue or explain it;
• throttle or suspend the server;
• terminate the server or account and remove content;
• preserve or disclose information where the law or provider policy requires it.

Non-critical reports: 24 hours

For non-critical reports we contact you in the support chat in your dashboard and, where we have it, by email, with the details of the complaint. You have 24 hours to remove the reported content or fix the configuration, or to reply with your side of the story. If it is fixed in time, the case is closed. If the deadline passes with no reply and no action, the server may be suspended or terminated.

No refunds are issued for terminations caused by policy violations (see Refunds & Billing).

Automatic security checks

Many complaints against honest customers come from services left open by mistake. We periodically check our servers for commonly abused services exposed to the internet — databases, caches, Docker API, SMB and similar. If we find one, we message you in the support chat with the port and how to close it. It is a warning, not a penalty; if you need the port open on purpose, just tell us.

If your server was reported

Reply in the support chat or write to support@kvantis.org with logs, context or anything showing the report is wrong. False positives happen — scanners flag legitimate VPN endpoints, Tor relays and game servers — and we review what you send.

What leads to termination

Spam infrastructure, phishing, malware distribution or control, botnets, DDoS attacks and child sexual abuse material lead to termination, not a warning. CSAM is reported to the authorities immediately. We are privacy-friendly, not abuse-friendly: this line keeps the IP space clean for everyone else.

Sanctions

The Service may not be used from, or on behalf of, sanctioned or restricted territories or by sanctioned persons — see Sanctions and restricted territories in our Terms. Accounts found in breach are suspended and their servers stopped.

How to avoid reports

• Bind databases and caches to 127.0.0.1 or a private network, or allow them only from your own IPs. If they run in Docker, publish them as 127.0.0.1:PORT:PORT — Docker bypasses ufw.
• Do not run open DNS resolvers, open SMTP relays or unauthenticated proxies.
• Keep software updated and rate-limit anything public.
• Outbound SMTP (ports 25/587) may be restricted by default to protect IP reputation — see the Acceptable Use Policy.