Security
DDoS protection
How Kyrbit talks about attack resilience during beta.
Honest version: we are in closed beta with a single US East location, and our DDoS protection today relies on network-level mitigations from our hosting and transit providers plus internal operational response. We do not publish capacity numbers we cannot independently verify.
What this means in practice
- Large traffic floods: may be mitigated by network providers, but beta capacity claims are intentionally conservative.
- Application or game-specific abuse: handled through operational response, customer communication, and future measured improvements.
If your server is under a sustained or sophisticated attack during beta, expect degraded service. We will tell you the truth about what we can and cannot absorb. We'd rather lose a sale than oversell.
Roadmap
We are evaluating additional protections for game traffic. When improvements are deployed and measured, we will publish customer-safe summaries of what changed and what claims are supported by evidence. Not before.
What you can do
- Don't share your server address publicly more than necessary.
- Use Minecraft's built-in whitelist for small private communities (see Whitelisting players).
- If you get extorted by an attacker, do not pay. Open a support ticket so we can review the incident and help with next steps.
For the current public posture, read the DDoS protection page.
Didn't find what you needed? Open a support ticket. During the closed beta you'll get a real human reply, usually within a few hours.