Understanding your resource limits

Every plan has a fixed RAM, CPU and disk allocation shown on the product page and in your service details. Here's what actually happens at each limit.

RAM

If your server process tries to use more memory than allocated, it will typically be stopped by the system rather than allowed to exceed the limit (the exact message depends on the game/software — Minecraft usually shows an out-of-memory crash in the console). This is the single most common cause of an unexpected crash on a server that was previously running fine, usually after adding more plugins, mods, or players than the plan was sized for.

CPU

CPU limits are usually a ceiling rather than a hard stop — your server can briefly use it fully, but sustained high usage will show as lag/tick-rate problems (low TPS on Minecraft, stutter on other games) rather than an immediate crash.

Disk

Running out of disk space can prevent your server from writing logs, saving the world/game state, or even starting at all. Check usage from the File Manager (or df -h on a VPS) if your server fails to start or save — "disk full" is a common, easy-to-miss cause.

Checking current usage

The Console/status area of your panel shows live RAM and CPU usage while the server is running. If you're consistently near the limit, that's a sign to either optimize (fewer plugins/mods, lower view-distance, etc.) or upgrade the plan rather than waiting for it to fail under load.

Upgrading

If you're consistently hitting a limit, see Upgrade or change your plan — resizing before you're forced to (mid-crash, with players online) is always the better time to do it.